I don’t think there is a technical issue or any kind of complexity at issue here, the problem seems trivial even though I haven’t worked the details. It is moot since it’s broken on purpose to preserve “They’s” business model.

I’m explaining what the technical problems are with your idea. It seems like you don’t fully understand the technical details of these networking protocols and that’s okay but I’ve summarized a few non trivial technical problems that aren’t just people keeping multicast from being used. I assure you if multicast worked, big tech would want to use it. For example, Netflix would want to use it to distribute content to their CDN boxes and save tons of bandwidth.

I don’t know who they is in the case, but let’s think about this for a minute.

Technically what do you need for this to work?

How many Multicast Addresses do you need? How are multicast addresses assigned? Can anybody write to any multicast address? How do I decide that 239.53.244.53 is for my file not your movie? How do we know who is listening? This is effectively BGP, but more tricky because depending on the answer to the previous question you may not benefit from any network block sizes to reduce the routing info being shared. How do you decide when to start transmitting a file? Is anybody listening? Does anybody care?

You seem latched on to assume that technically would work and haven’t asked if it is actually technically a good solution. P2P is going to work better than multicast

Multicast addresses are handled specially in routers and switches all over the world.

Changing that would require massive firmware updates everywhere to get this to work and we can’t even get people to adopt IPv6. Nevermind the complexity in figuring out to how manage IGMP group membership at the Internet scale.

Given the complexity with either change, its better to adopt IPv6 and use PeerTube. Multicast at the Internet scale won’t work and IPv6 is less work

Assuming multicast worked across the internet, it’s not going to work in practice. Multicast works by sending a packet and fanning it out to all receivers.

It works with broadcast TV like IPTV because everybody is watching the same few set of channels at the same time, but on YouTube I can watch any video at any time. How does a mythical Transmitter know what video packets to send when? Are they on loop? Are clients receiving packets for videos they don’t care about?

You might be interested in PeerTube which uses unicast peer to peer to distribute videos in a way that works.

I use a variant of this: https://github.com/linuxserver/docker-wireguard

You don’t need two different containers for this. They’re going to either fight each other for control over the networking tables or run wireguard in wireguard

So I had a chance to try this out. It wasn’t on Google Play Store, only F-Droid. There isn’t really SSO support, you either login with User/Password or a token. Instead, I login with my browser, get the token and paste it in. That works fine, but an ideal world is just pop up an browser WebView and go through the flow, then grab the token. Maybe it was intentional, but PaperlessShare registered as an Open handler for PDFs and the share menu, whereas this is only share menu. This seems to mean that I need to grant file access, whereas the open handler didn’t need that I think.

Overall, it does the job and gets my docs uploaded.

My prediction is that manually reviewing user creation won’t scale to a high level and unless systems develop spam detection and reputation management similar to email then it’s not going to be limited to just one or two bad instances.

Its trivial to create my own instance with a new domain and there’s no limitations against sending ActivityPub messages to a server. Unfortunately the simplest fix is for big instances to restrict what instances can communicate to it, but that causes centralization.

Plus, we don’t need to be huge. There’s no benefit from it.

The benefit is breadth and depth of communities. Reddit is great because if you are interested in a topic, there’s a bunch of people talking about it.

How hard would it be to contribute these improvements back to the project in the form of either distro package updates or documentation changes? Did you consider that?

Can you expand on the OIDC/OpenID support? Does it support SSO based authentication to Paperless? That’s my biggest problem with PaperlessShare right now. I can’t actually sign in because I use an SSO provider.

I respect your strong ethics and sticking to them, but saying they people support genocide for using software hosted on GitHub is an extreme position.

I could easily change this: Do you drive a car or fly a plane? Then you must have no red lines against climate change.