I used to think the same for WhatsApp, Spotify, Twitter and Apollo but they can all be replaced by alternatives (Telegram / Signal, Amazon Music, Mastodon, Memmy).
I know about Keepass but it’s definitely not as convenient and easy to use as Bitwarden.
I don’t use YouTube app because of ads everywhere but I would have trouble stop using YouTube on my computer.
KeePass is really good, but it definitely requires to handle everything outside the password management (like syncronization between devices, TOTP, password quality check, etc.). It is not user friendly at all. Thankfully KeePassDX (on Android, not pc) has a way better built-in experience.
For YouTube, check out newpipe on F-Droid. No ads, you can download content, play videos in background, etc.
youtube revanced is the goat, but make sure to get it from github. It’s the only official source at the moment. You gotta patch it yourself but it’s basically youtube vanced once it’s all set up.
You are in a large instance, so searching for communities shouldn’t be so much of a hassle, since most are fetched. You use the feddit community browser, look for some keyword of your interest and if it exists you just search it within your instance. Subscribe and you’re done.
If you for some reason can’t find it, it means it is not fetched yet.
So you copy the whole URL (any.instance/c/anycommunity), paste in the search bar and then search again for the community name only. It will show up and you can subscribe to it.
That’s confusing. Let’s say that there is antance A, B and C. (Instance A is Beehaw) Now let’s say A bans C, but not B. And B hasn’t banned anyone. That would mean instance A would still see the comments of C, when replying to B, right? If so, people from Instance A would feel like they are being gaslit more then people blocked from instance C.
My understanding is that Lemmy isn’t peer-to-peer, it’s more like hub-and-spoke, relative to the instance that the community is on.
So if users on B and C are interacting with a post on A, then it’s the responsibility of A to be the postman and handle the syncing between A<>B and A<>C; B and C don’t directly talk in this case.
Thus, nobody outside of Lemmyworld sees posts from Lemmyworld, because Beehaw doesn’t accept them, and therefore doesn’t pass them along to the other instances, either.
My understanding is that Lemmy isn’t peer-to-peer, it’s more like hub-and-spoke, relative to the instance that the community is on.
So if users on B and C are interacting with a post on A, then it’s the responsibility of A to be the postman and handle the syncing between A<>B and A<>C; B and C don’t directly talk in this case.
Thus, nobody outside of Lemmyworld sees posts from Lemmyworld made on Beehaw communities, because Beehaw doesn’t accept them, and therefore doesn’t pass them along to the other instances, either.
Not quite. So imagine each Lemmy instance is a post office, responsible for receiving mail from other instances on your behalf, and also responsible for sending your mail to other instances.
The post office (instance) that matters is the one where the thread is taking place. When you write a message on a thread - if the thread is on your home instance, great! No outbound mail. If it’s not, your post office (instance) will send your mail across the fediverse to the instance where the thread actually lives, and the receiving instance adds it to the thread.
Likewise, when users reply to you, their instances mail their replies to the instance where the thread lives; the thread’s instance is then responsible for re-forwarding their mail to you.
In this case, Beehaw has unilaterally decided not to accept mail from, or deliver mail to, Lemmyworld. So your experience varies based on which is your home instance, and which instance you’re interacting with.
So exploring it by example, let’s consider we have three instances: Beehaw, Lemmy.world, and (shameless plug) my adorable little home instance of federate.cc, which is federated with both of the above (and is accepting membership applications by the way!)
If the thread lives on Beehaw, and you are a member of…
Beehaw, then you can interact with the post (it’s your home instance), but you won’t see any replies from Lemmyworld users (your post office is refusing to accept letters from them)
Lemmyworld, you probably won’t be able to see the thread at all (Beehaw refused to deliver it to their post office) - but if by some chance you can, you won’t see any comments by Beehaw users (Beehaw refuses to deliver them to the Lemmyworld post office)
federate.cc, then you will be able to interact with the post (Beehaw delivers mail to our post office), but you won’t see any replies from Lemmyworld users (Beehaw refuses to accept mail from Lemmyworld users, and by extension refuses to deliver their mail to our post office)
If the thread lives on Lemmyworld, and you are a member of…
Beehaw, you probably won’t be able to see the thread at all (Beehaw refused to accept the mail from Lemmyworld, returning it to sender) - but if by some chance you can, you won’t see any comments by Lemmyworld users (Beehaw refuses to accept mail from Lemmyworld, returning it to sender)
Lemmyworld, then you can interact with the post (it’s your home instance), but you won’t see any replies from Beehaw users (their post office refuses to deliver letters to yours)
federate.cc, then you will be able to interact with the post, but you probably won’t see any replies from Beehaw users (Beehaw’s post office refuses to deliver mail addressed to Lemmyworld)
If the thread lives on federate.cc, and you are a member of…
Beehaw, you will be able to see and interact with the thread, since Beehaw’s post office both sends and receives mail from federate.cc; but you won’t see any messages from Lemmyworld users, because Beehaw’s post office will refuse mail that originated at Lemmyworld; when we try to forward that mail to Beehaw’s post office, it will be refused and returned to sender.
Lemmyworld, you will be able to see and interact with the thread, since Lemmyworld’s post office both sends and receives mail from federate.cc; you will see messages from Beehaw users, because Beehaw’s post office will deliver mail to ours; but if you interact with them at all, they will never see it, because Beehaw will reject mail that originated at Lemmyworld (see above).
federate.cc, then you will be able to interact with the post as normal, you will see replies from people at all three instances, and they will see yours
Phew! How confusing. A far better solution would be… don’t defederate, splitting the community!
My understanding is that Lemmy isn’t peer-to-peer, it’s more like hub-and-spoke, relative to the instance that the community is on.
So if users on B and C are interacting with a post on A, then it’s the responsibility of A to be the postman and handle the syncing between A<>B and A<>C; B and C don’t directly talk in this case.
Thus, nobody outside of Lemmyworld sees posts from Lemmyworld made on Beehaw communities, because Beehaw doesn’t accept them, and therefore doesn’t pass them along to the other instances, either.
Had some friends round last night. Watched the boxing and got drunk. Went to bed about 2am. Cat woke me up about 7 demanding food! Meows louder than an air raid siren. Climbed back in to bed now and browsing Lemmy. Been a busy week so just catching up with the latest posts.
kbin.life
Oldest