TLS certs can have one level of wildcard (even let’s encrypt supports this), and creating subdomains programmatically is not exactly black magic - the main blocker from the technical side is that the code to update the DNS is usually not portable between providers, so it’s not adequate for a federated open source project.

One of the effects of capitalism is that people are conditioned to think as growth in quantity is the end goal of all human activity.

This makes it harder to realize that, as far as the Fediverse is concerned, at very least, Lemmy and Mastodon have achieved viable self-sustaining networks and that driving inorganic growth by targeting users in other platforms would reduce the viability of the network because it makes onboarding new users harder. An example of this even inside reddit was when a subreddit got a sudden large influx of new subscribers they invariably lost what made them stand out in the first place.

And honorable mention to the non-existing Matrix sequel that had an actual SSH vulnerability on screen.

Wait, you’re telling me that Discord is probably still vulnerable to the Webp RCE vulnerability?

*Badly outdated Chrome with a bunch of critical vulnerabilities.

Don’t forget every Electron app comes with its own Chrome.

Except most people running their services on AWS are not using just the EC2 instances. I would even go as far as saying no one in their sane mind uses AWS just for EC2, at which point you are probably tied to the services you use. If Amazon goes full Unity, and you are lucky it’s things that have alternative implementations like S3, if it’s something like sagemaker you’re fucked.

This is what it looks in the web UI:

The problem with hosting your own instance is that you can’t create a community in another one.

And since they are a central aspect of Lemmy, your experience can still suffer if the instance with one of your favorite communities goes belly up.

Ideally communities should be fully distributed (i.e. not tied to a specific instance) to avoid these issues. Unfortunately, that would lead to its own series of challenges.

For example, what would happen if two people change the same paragraph in two different instances at roughly the same time?

This is already a problem for existing distributed versioning systems (like git), and in those the merge conflicts can only happen when the users explicitly request them. With activitypub the merge conflicts would happen in response to asynchronous events and to make things worse, different instances might see different events. How would you surface the conflict to the users so they can solve it? Do you send an email to the user which was a fraction of second late saying their edit got rejected? Do you reject both of them and keep the old content? Do you overwrite the first edit silently?

These are already hard UX problems on centralized wikis, and the technical aspects of a distributed system would make them worse. So much worse that I would say it’s orders of magnitude harder to implement than a link aggregator.

It would be a nightmare to implement a wiki over activepub, so it would probably need to exist outside of federation.

It also feels like the kind of feature creep that made Reddit unsustainable. Software should do one thing and do it well - Reddit’s reliance on 3rd parties fixing core functionality while they pursued every shiny new thing their product managers and software engineers wanted to put on their CV should be a cautionary tale.

I feel we would be better served with wikis stored outside of Lemmy and simply linked in the description. Lemmy exists on the web and shouldn’t try to pretend it doesn’t like corporate social media.

You can easily store the video somewhere else and share it here. Lemmy is primarily a link aggregation platform and more walled gardens is the last thing the internet needs anyway.

The alternative is no Lemmy because copying every single video to every single instance would bankrupt most of them.

I actually think that’s a bad idea, storing video is expensive and will quickly make hosting instances unsustainable. This kind of feature creep is what made Reddit an unprofitable black hole, and should be avoided.

On paper there’s lemmy-lite, but I don’t know if any instance supports it.