Erin Kissane posted a long and well researched article about Threads federation risks and trust and safety issues around Meta. If you're taking part in the debate and discussions about Threads federation - or if you're instance admin on the fence - you should really read this.
I can't find anything on the specifics of how federation actually works. The op thread gets copied to any federated server? What happens if the thread is deleted on the op server? Does it still exist on all other federated servers? How do comments and votes work? That kind of thing.
There are mobile apps in development and the API is coming along.
Kbin is still just a prototype though, but it's moving along nicely.
My other feeling is that kbin is setting up to be like iCloud whereas lemmy is more akin to sftp.
I've no idea what that analogy even is, but I think the differences are mostly technical (PHP vs Rust) and UX.
Both implement AP a bit differently, but at the end of the day, they're still AP aggregators.
And that's ignoring the political issues around lemmy's codebase ofc.
The biggest thing that bugs me about Mastodon is the lack of the simple ability to just "like" or agree with a post. I like a voting system. Give the idea that what you posted is some sort of uncouth or an unspoken unique idea. I don't want it a part of my profile via "boosting". I just want to say "hey bro, yeah, that's neat" and move on.
That's exactly what the "Favorite" (star) function does on Mastodon.
A lot of us are pretty new to the fediverse and we've arrived just in time to grapple with what is easily the biggest federation/defederation controversy ever to hit it. I've put this thread together to hopefully help communicate some of the more complex ideas that we're trying to get our heads around....
Finally someone who has a clue. That was well written and easy to understand. Thank you for all the work you put into that post!
Defederation is about what an instance allows in, not what an instance allows out. Defederation stops you seeing the defederated instance's content, but it does not stop them seeing your instance's content.
As a final, tiny little point of interest - there is a setting called AUTHORIZED_FETCH (Secure mode) which will force the requesting instance to authenticate. This can be used to stop the data from flowing out.
Of course enabling this is somewhat problematic as it tends to break other things. But it's there.
As an added bonus, you can also use the https://kbin.social/d/[instance domain here] scheme to block entire domains, if you find that they include content you don't want to see in your feed.
@pollodiabolo - this user is a karma whore of epic proportions and they have made a shit load (10-15+) accounts on kbin that boost and upvote each other while sometimes mass downvoting others that have posts trending towards the top - all to farm karma....
Contacting the project "officially" through the the public tracker was the right thing to do.
As for the tone of the message - I don't think it was out of line considering the circumstances.
Mistakes do happen (licensing is actually hard) - and I'm happy to see it got fixed fast.
Edit: For some reason this keeps bouncing around in my head and the more I think about the more I believe that Emma should have contacted you privately (at first, anyway) instead of jumping right into attempting to publicly shame you.
The issue tracker for kbin codebase was the correct place to submit the complaint.
Licensing issues are tricky and if you're the copyright holder there's no way to know if people stealing your code are acting in good faith or not. Best course of action is to document and report the violations "officially". You need to have a clear track record in case the other part is going to try to deny or obfuscate the situation.
It was the right thing to do.
As for the tone and the username.
From what I can see, she's the main dev for that codebase and has been for many, many years. She gets to decide the tone, she's the one who's defending her rights and work.
Having said that, ernest handled it well - and is clearly acting in good faith. So that should be the end of that.
Untangling Threads (erinkissane.com)
Erin Kissane posted a long and well researched article about Threads federation risks and trust and safety issues around Meta. If you're taking part in the debate and discussions about Threads federation - or if you're instance admin on the fence - you should really read this.
Where can I find documentation on how federation works? (kbin.social)
I can't find anything on the specifics of how federation actually works. The op thread gets copied to any federated server? What happens if the thread is deleted on the op server? Does it still exist on all other federated servers? How do comments and votes work? That kind of thing.
clients are the libre future; I hope kbin catches up (kbin.social)
On desktop kbin is 5x better than vanilla lemmy....
deleted_by_author
Defederation, Threads and You (kbin.social)
A lot of us are pretty new to the fediverse and we've arrived just in time to grapple with what is easily the biggest federation/defederation controversy ever to hit it. I've put this thread together to hopefully help communicate some of the more complex ideas that we're trying to get our heads around....
YSK that Kbin can subscribe not only to magazines and communities, but entire instances. (kbin.social)
This may be useful for folks looking to expand their feed. I discovered this on accident and it completely revolutionized my experience on Kbin....
Call out post for a particular karma farmer on kbin.social (kbin.social)
@pollodiabolo - this user is a karma whore of epic proportions and they have made a shit load (10-15+) accounts on kbin that boost and upvote each other while sometimes mass downvoting others that have posts trending towards the top - all to farm karma....
Hey guys, this time I really messed up :/ (kbin.social)
I think you should see something....