cendawanita
Anyway, what does then tend to shake out is that the bigger instances need to decide if it's open for all or not, and the social consequences of that, and more small to midsized instances émerge.
@CynAq you don't have to defed entire instances, if the instance themselves are willing to keep to their own principles. If that's not kept or they've changed their position, it is actually Fedi culture to date, to defed (this is on instance to instance basis). Federation isn't being connected to everyone, it's practicing the right to associate. That's why if you don't agree with your instance, unlike closed systems, you have the right/freedom to move.
(The problem is the moving so far only carries your social graph not post history. So yes there is a penalty - but this also incentivize users to also push their admins to act more representatively. Assuming that's what the majority wants)
@macallik
Absolutely. If this is true then for the other small to mid-size instances it's not just an existential threat philosophically but technically. They're expecting Threads onboarding might just knock out instances because of the traffic. Might as well limit or block just for your own performance metrics.
@macallik and if you scroll down the comments, Byron from Universeodon, who did take the earlier meeting, did provide some vague points from the meeting. Relating to your point about big instances, it seems likely that FB wants to throw money at them so that they won't become overwhelmed by the ensuing traffic (unlike the rest of us, I guess...) so they can demonstrate that the Instagram bridge (it's an IG product) works.
@furrowsofar very much this point. There's an additional issue related to (kbin) infra as well, it does fetch content and present it as tho that person posted on the microblog here and short of contacting an admin, no user-level way to delete it (since they can't actually login)
@asjmcguire the user-level block means you the user can't see the post. It's still being fetched at instance level. So in terms of avoiding hate speech (political problem), good and quick step to do. In terms of overwhelming an instance with traffic (the technical problem), not so much.
@asjmcguire i was talking about kbin. The AP programming language (eta: yes it's called protocol or standard as well iirc) is definitely old :)
The fact that kbin does fetch posts from originating instances without instances having the setting to allow or disallow is a problem once something with the computing power of meta and its userbase comes on board. Because mastodon for example doesn't have whitelists, only blocklists.
@chemical_cutthroat
The first conceptual mistake in this analogy is assuming the LLM entity is "writing". A person or a sentient being writing is still showing signs of intellectual work, which is how the example book report and movie review will not be accused of plagiarism, which is very very basically stealing someone's output but one that is not made legally ownership of (which then brings it to copyright infringement territory).
LLMs are producing text based on statistical probability meaning it is quite literally aping/replicating the aesthetic form of a known genre of textual output, which in these cases are given the legal status of intellectual property. So yes, an LLM-generated textual output that is in the form of a book report or movie review looks the way it does by copying with no creative intent previous works of the genre. It's the same way YouTube video essays get taken down if it's just a collection of movie clips that might sound like a full dialogue. Of course in that example yt clip, if you can argue it's a creative output where an artist is forming a new piece out of a collage of previous media, the rights owner to those movie clips might lose their claim to the said video. You can't make that defence with OpenAI.
@stopthatgirl7