this post was submitted on 19 Aug 2024
52 points (94.8% liked)

Fediverse

17508 readers
18 users here now

A community dedicated to fediverse news and discussion.

Fediverse is a portmanteau of "federation" and "universe".

Getting started on Fediverse;

founded 4 years ago
MODERATORS
deadsuperhero@lemmy.ml
wakest@lemmy.ml
52
Lemmy vs. PieFed vs. Mbin (fedia.io)
submitted 3 weeks ago by elena@fedia.io to c/fediverse@lemmy.ml
46 comments fedilink hide all child comments
 

I've been researching for the past week Threadiverse projects (Lemmy at first, then PieFed and now Mbin) with the goal of testing out their interoperability with the rest of the Fediverse.

Apologies in advance if this is the third post you see from me - this one is my first in Mbin.

I wonder if you have any insights regarding the differences between the 3 - advantages/disadvantages and opinions on your favorite project?

I'm also interested to see if Mbin manages to federate mentions (unlike Lemmy and PieFed who falls short). So for the purposes of this test, I'm mentioning:

  • my Mastodon account @_elena@mastodon.social
  • my Friendica account @elena@opensocial.space
  • and my Lemmy account @elena@lemmy.world to see if anything happens

Thanks and happy to be here!

you are viewing a single comment's thread
view the rest of the comments
[–] Dave@lemmy.nz 14 points 3 weeks ago (1 children)

Both Lemmy and Mbin lack the ability to filter out or block Cloudflare nodes. They both only give a way to block specific forums.

Lemmy lets you block whole instances, it was introduced in 0.19.0 (which was released just before Christmas, but many instances didn't update until 0.19.3 was released around the start of the year due to federation issues with 0.19.0).

I don't get why you want users to be able to apply cloudflare filters, though. If your instance doesn't use cloudflare, then you won't access through cloudflare. I'd actually be really interested in understanding why this is something you're looking for, rather than just the ability to block an instance such as Lemmy.world.

[–] ciferecaNinjo@fedia.io 0 points 3 weeks ago (1 children)

I don't get why you want users to be able to apply cloudflare filters, though.

Suppose an instance has these users:

  • Victor who uses a VPN
  • Cindy whose ISP uses a CGNAT (she may or may not be aware of the consequences of that)
  • Terry who uses a Tor
  • Norm who uses the normal clearnet
  • Esther who is ethical (doesn’t matter what she uses)

And suppose the instance is a special interest instance focused on travel. The diverse group of the above people have one thing in common: they want to converge on the expat travel node and the admin wants to accommodate all of them. Norm, and many like him, are happy to subscribe to countless exclusive and centralised forums as they are pragmatic people with no thought about tech ethics. These subscriptions flood an otherwise free world node with exclusive content. Norm subscribes to [!travelpics@exclusivenode.com](/c/travelpics@exclusivenode.com). Then Victor, Terry and sometimes Cindy are all seeing broken pics in their view because they are excluded by Cloudflare Inc. Esther is annoyed from an ethical standpoint that this decentralised free world venue is being polluted by exclusive content from places like like Facebook Threads™ and LemmyWorld. Even though she can interact with it from her clearnet position, she morally objects to feeding content to oppressive services.

The blunt choice of the admin to federate or not with LemmyWorld means the admin cannot satisfy everyone. It’s too blunt of an instrument. Per-community blocks per user give precision but it’s a non-stop tedious manual workload to keep up with the flood of LW communities. It would be useful for a user to block all of LemmyWorld in one action. I don’t want to see LW-hosted threads and I don’t want LW forums cluttering search results.

[–] Dave@lemmy.nz 6 points 3 weeks ago (1 children)

Ah right! OK first off, you can block all of Lemmy.world with one action now.

Secondly, Lemmy now supports image proxying (with a new feature in Pictrs 0.5, which I believe was also introduced in Lemmy 0.19). I'm not sure which instances have it enabled but in theory you can check the source of images for remote users who have posted images.

Lemmy is already a strain on hard drive storage so I don't think many people have enabled it (proxying will store the images on the Lemmy server for a set period of time).

Thanks for the explanation by the way, it makes sense.

[–] ciferecaNinjo@fedia.io 2 points 3 weeks ago (1 children)

I just need to work out exactly what the effect of the user-configured node block is. In principle, if an LW user replies to either my thread or one of my comments in someone else’s thread, I would still want to see their comments and I would still want a notification. But I would want all LW-hosted threads to be hidden in timelines and search results.

On one occasion I commented in an LW-hosted thread without realising it. Then I later blocked the community that thread was in (forgetting about my past comment). Then at one point I discovered someone replied to me and I did not get the notification. That scenario should be quite rare but I wonder how it would pan out with the node-wide blocking option.

[–] Dave@lemmy.nz 2 points 3 weeks ago

I believe blocking an instance hides posts from your feeds but nothing else, but it's worth testing.

I have lemmit.online (reddit copy) blocked, but I can still search for a specific post and view it. I have also seen others complaining that when they bad an instance they still see comments from users on that instance, so at least at the moment it seems it just hides the posts from your feeds.