Working this weekend, as with most weekends. It’s not so bad as I finish at 1400. Hopefully get home to an empty house and have a powernap. It’s the simple things.
I apparently have always used Twitter wrong since I mostly just lurk and people I follow don't get into flamewars or whatever they're called. It's kinda unrecognizable for me how you describe Twitter.
Mastodon on the other hand is just pretty dead for me. I haven't found that much interesting stuff and I don't really know where to look.
From my perspective, they function pretty similarly. I don't see the toxicity you're talking about. Quote tweeting is handy because it's not used to put down others but just, you know, sharing and adding something to the original tweet.
Hyperion Cantos -Dan Simmons Cryptonomicon - Neal Stephenson A deepness in the sly - Vernor Vinge Insane City - Dave Barry Where Eagles Dare by Alistair MacLean.
That list won't show which instances have block the home instance. The blocked list lists only the instances the home instance has blocked, not the other way around.
How does this work exactly? If another instance blocks lemmy.world for example can I still see (but not interact with) content on the other instance, or is it completely invisible?
Instances A, B, and C are federated initially. When a user posts on Instance A, users on Instances B & C can see and interact with the post directly. Any comments they make will be sent back to Instance A as the "home" instance for that content.
Now let's say Instance A decides they don't care for the type of interaction they're getting from Instance C's users and decides to block - or defederate - Instance C.
To users on instance A, nothing changes other than new posts and comments from users on Instance C will no longer show up. To users on Instance B, nothing changes other than new comments from users on Instance C won't appear in posts they interact with on Instance A. However, for Instance C, things are suddenly branched.
On Instance C, any posts that were created prior to defederation still exist in Instance C's record. However, any comments that users on Instance C commit to those posts will no longer be distributed to users on Instances A or B, because Instance A maintains the "primary" record of the post. Similarly, Instance C's users will not receive updated comments from users on Instance A OR Instance B, because again, Instance A is what determines which comments appear in federated instances. Furthermore, new posts created on Instance A will no longer show up in users' feeds on Instance C. From the moment of defederation, Instance C's copies of all posts on Instance A are now distinct, and the only new comments or updates they will receive will be from local users on Instance C.
Thanks, very helpful! What about posts from instance B and comments in instance B post? I'm assuming instance B users can see both comments from instance A users and instance C users but for them (instance A and C users), they can only see their respective instance users' comments and instance B users' comments?
The most important part of the federation process is played by whichever instance hosts the original post. They’re the hub and all other instances are the spokes.
So once Instance A defederates from Instance C, nothing Instance C users add to posts hosted by Instance A will be added to the master manifest. Basically, everyone is updating Instance A’s copy of the post, and that copy is then being redistributed to all other federated Instances.
Once Instance A defederates from Instance C, the only time their users will interact from that point forward is on a mutually federated instance. Both communities can comment and interact on a post hosted by Instance B.
I've been working on a bot, and when things are working it synchronizes almost instantaneously, including edits to posts and new comments. Any significant delay should be rare.
There are a bunch of reasons why things might be out of synch - load issues, software compatibility (lemmy.world is still on 0.17.4 while lemmy.ml has upgraded to 0.18), bugs... It helps to keep in mind that Lemmy is barely more than beta at this point.
Started with Jerboa, but it started crashing on me yesterday (plus, it apparently isn't working right now with lemmy.world). So I tried Liftoff yesterday, which I'm using to comment this. Definitely going to Sync again once it's done!
A lot of this has more to do with the mindset people approached Twitter with than the service itself. Honestly, I always approached Twitter the way you describe Mastodon here. I just wanted to find people who had interests similar to mine and connect with them, as well as find interesting news. Maybe that’s why moving from Twitter to Mastodon has been to seamless. Just a lot less anger and hate on Mastodon from what I’ve experienced. A much nicer atmosphere.
It's how Twitter started. You followed people because they were your friends or had similar interests. It being a platform mainly for celebrities and influencers came later.
End of the World running club. As someone the UK the concept of a massive apocalyptic event set in the uk was intriguing. I loved the book.
Also Sphere by Michael Crichton. In my own head canon, I seem to recall reading this in one sitting over a single night I was doing an all nighter. It was just super gripping!
No, communities on different instances will not have the same content. This is one of the features of the fediverse.
Each instance can have it’s own /c/memes and they won’t conflict. So, there could be lemmy.world/c/memes and lemmyverse.org/c/memes and they could each be different with different content and rules. If you want to see each instances ‘memes’ community, then you will need to subscribe to them individually from your home instance. Once you do that, the ‘memes’ community will be ‘cached’ on your home instance and it will show up in everyone’s feed on your home server.
Right now its a bit of a mess while things are quickly developing. Ultimately, federated communities should look the same across the fediverse, with a slight delay.
There are some caveats to that around defederation.
kbin.life
Active