Notices by silverpill (silverpill@mitra.social), page 15

@elvecio My instance is in some shared block list. I don't know for sure, probably cryptocurrency

@jeffcliff @sun No, but Streams can do this, and Mitra has partial support.

@aeris @privateger Well, I'm blocked by 283 instances. Couldn't care less

Moderation is not censorship. If people don't want to interact with you, there's no good reason for you to interact with them.

@jeffcliff I don't think blocking 20000 domains at once is a realistic scenario, because normally censors are tasked with suppressing specific sources (while minimizing collateral damage).

However, you're right that deep dependency on DNS is not a good thing, even though DNS is necessary to maximize reach and provide good UX. I designed FEP-ef61 which addresses this issue by detaching identity from domain name.

@moon Some clients make connections to relays directly from the browser, so they won't be able to connect to blocked relays. If requests are proxied by client, it won't be affected.

@taylan I agree that instance admins are often over-reacting with instance blocks, but I don't see how moderation can work on a large scale without such mechanism.

The situation can be improved by making identity decentralized. I've been working on it: https://codeberg.org/fediverse/fep/src/branch/main/fep/ef61/fep-ef61.md
This solution allows full account migrations (not just followers), and multi-homing. A bit like Nostr, but "instances" still exist as moderation domains.

@taylan

>Is there a technical reason Nostr couldn't have as many relays as Fedi has nodes?

There is no technical reason, but I think there's a social reason. People are not good at managing secret keys, so as the network grows, more and more people will forgo key management and will use trusted services. Basically, the same scenario that played out in cryptocurrency world. An average user don't want to think about keys and relays, so market will provide convenient but centralized solutions.

This hasn't happened in Fediverse because of the very feature you're criticizing it for. Reputation of the server can be damaged by actions of its users, and that creates a strong incentive to split into smaller communities.

@877308276be50ce9bafa7e5e374e4fcbf5e9859a21918f34baefd000746b7d35 Moderation is not censorship. Mastodon.social users don't want to interact with poa.st users, so they disabled federation with them.

>have you seen https://how-nostr-works.pages.dev/

It talks about a situation when user is banned by multiple relays. To recover from that, he deploys new relays and then attempts to contact his followers. Nice idea, but realistically, who is going to do that? Software developers, and a small number of power users?

And again, this is "ban resistance", not censorship resistance. Censoring almost always happens at the network level, not the application level. In that case people use VPNs, Tor and similar tools

@moon The value of a network depends on its size, so the total number of nodes and distribution of users are quite important. If you cut off 99% users the network will be dead no matter what.
Censorship circumvention has a price, and most users will not pay it.

By the way, the cheapest solution is not to deploy a new node, but to use a VPN.

@taylan Yes, in theory you can run your own relays, and switch them easily. Most users won't do that. In practice the network is smaller and easier to disrupt, that's what my post was about.

>"admin dictatorship"

No idea what it means. You can run your own fedi server if you want to be in charge

>means you will be banned from interacting with half of the Fediverse or more

If those people don't want to interact with you, I don't see any problem

@aeris Bluesky is not decentralized and never will be. You have no idea what you're talking about.

@gemlog I don't know about Jami, it probably uses bootstrap nodes and relay servers that help clients behind NAT, both can be blocked by domain name.

Many apps that are advertised as decentralized or peer to peer are not censorship resistant (by censorship I mean attacks by state actors). Tor and I2P are good at that.

@moon Nostr relays are servers too. You can use multiple servers at once, but users tend to concentrate on a small number of popular servers. Hosted web clients are just regular websites and can also be blocked by domain name.

@moon It's a micro-blogging server I'm building https://codeberg.org/silverpill/mitra

@sun

Still pending?

You follow request was processed and my server sent Accept activity back. Then your server responded with 200 OK

@sun @fediverse @deadsuperhero Not yet. But Mitra can display a "Subscribe" button and subscription terms for sub.club accounts if they start publishing a Proposal object as described in FEP-0837. Alternatively, I can add support for their custom subscription property

@deadsuperhero @fediverse @quillmatiq Protocols described in these FEPs are currency-agnostic and developers can build actual platforms and solutions on them (as I did). This is the only ongoing effort to bring a payment layer to the Fediverse - there are no alternative proposals. FEP-8c3f was withdrawn in favor of FEP-0ea0.

Okay, you didn't know about it. But now you do and it would be nice to include at least some of that information in the article.

@frogzone @r @marty_bent The viewer shouldn't be sent to another site on clicking. Thumbnail images will be displayed as regular attachments

@deadsuperhero @fediverse FEP-ef61 is what Mike was implementing and rolled out in production this summer. It's not like we didn't advertise that. All work on this FEP (and ones that precede it) was done in public channels, it's really hard to miss if you're interested in nomadic identity.

Give @weekinfediverse a follow. It provides a concise summary of what is happening in Fediverse

@quillmatiq

https://wedistribute.org/2024/03/activitypub-nomadic-identity/

In another article @deadsuperhero talked about nomadic identity and Mike Macgirvin's efforts to implement it in ActivityPub, but similarly failed to mention another project that implements it (Mitra) and the person who wrote the spec (me).

At least my work was mentioned in a footnote. In the current article it is completely ignored.

@deadsuperhero @deadsuperhero