You can see the remote community once you search and you can see all posts in that community, from your server.
On Mastodon, even after you subscribe, you CANNOT see old posts on your instance, unless you put each post url individually in the search bar.
So, not the same at all.
I think the biggest problem with that is all the people complaining about “meta” trying to get into the fediverse (don’t get me wrong, I am not a meta user).
Because the protocol is open, it is impossible to stop it. If meta does make a product with better UI, even if they don’t change the underlying protocol, guess what the majority of people will be using?
It isn’t working perfectly, I tried following !programming@programming.dev from mastodon and couldn’t.
+1 for Fedilab It could use some improvements, but I am quite happy with it being able to look at multiple servers and follow different user from a single place.
Subpar UI really is what kills almost everything…
I can’t be tired of saying how much I hate mastodon’s default UI, where you can’t pull posts from users simply because you server doesn’t synchronize (what’s wrong with pulling it straight from the original server)? Imagine if you subscribed to a community on Lemmy and it only showed posts AFTER you subscribed…
Or the follow menu that says “please copy and paste this on your app”… Really? If you check docs.joinmastodom…something it even says “just type your username@domain and we will do a remote follow”
I think Lemmy apps will evolve faster and show others what is needed to progress quickly. This is natural when considering how Lemmy users interact with each other.
Yet I disagree with the article in many points. It didn’t always belong to Facebook, and that’s how it started, originally it even asked for something akin to one dollar for one year of usage (it was converted to some very small amount for each country).
One should also understand that in countries like India, Brazil, and a few others SMS and Internet on phones are extremely expensive. WhatsApp provided a very nice way to bypass SMS and stay within the lower plans for internet usage on mobiles. The big advantage here was to use your work or home internet to still reach out to people.
I know that in Brazil telcos introduced an entry line phone plan at one time saying that Whatsapp messages would be exempted from data caps.
Eventually, Facebook bought WhatsApp.
Saying it is simple to replace WhatsApp without considering the economic situation of the people relying on it is absurd.
Comparing it to FOSS alternatives at the current stage is easy enough, but every attempt at creating a FOSS alternative didn’t take. It is not uncommon to see the FOSS software not prioritizing the functionality and needs of users, and that will have people flock to whatever is useful to them, despite possible hidden costs.
I say this as someone who uses Matrix for chat, yet there are some critical bugs in usability that developers just ignore (like doing something basic like sharing from IOS breaks the spec and causes errors to several others).
When things like these happen there is always someone who will come ahead and say “this is provided for free” or “learn to code and fix it yourself”.
Eventually we get Pikachu faces or articles talking about the greatness of FOSS while ignoring all the main point “people still need a stable tool that fits their economic power while someone argues about how to fix a problem they don’t really care about”. As someone who mostly uses open source software, this is really frustrating.
As much as I love and follow matrix closely, I can’t fully trust developers who aren’t capable of deploying SSO in their product (look at dendrite mess). Unfortunately, following their SSO ticket chain was a mess and disappointment.