Well, obviously if you host from your home ISP, people will be able to figure out your home’s approximate location via a reverse IP search.

But otherwise go for it. It’s not that hard to do and a nice learning experience.

This guy also being a perpetrator of bullying because he didn’t like moderation decisions makes this post a bit ironic though 🤷

This is odd because I know a few mainland Chinese people that use XMPP without problems (and afaik without a VPN).

Sounds like your server got blocked for another reason?

That’s quite competitive energy density wise to LiFePO4 batteries. I wonder what the prices are.

Well, instead of leaking metadata to Signal, AWS, Cloudflare, Google/Apple and your ISP, like Signal does, RCS only leaks it to your ISP /s

You can easily redirect xmpp to port 443 which is not blocked by most firewalls. If you have problems with firewalls or public wifis your xmpp server is misconfigured.

The actual military grade (xmpp based) messengers implement security lables, meaning messages are tagged with the required security clearance and if you invite random people to a chat they can’t see the messages.

Something like that could be also interesting for a Lemmy frontend to make it easier to share images on instances that have strict upload limits.

Hmm, maybe they are running some developer release? I don’t think this has made it into an official release yet, and if so that must have happend very recently (I tried selfhosting Pixelfed about 6 months ago and it wasn’t available yet).

This is a planned feature for Pixelfed that is perpetually finally almost finished since about two years now 😅

Well, like I wrote below, it is basically about scaling Lemmy across multiple servers, with all the complexity that entails. I am probably not the best person to given advise on that though.

If our smaller instance ever gets to a size that is not feasible to run on a single server anymore, we will likely close registrations.

I am not against showing cross-post links like Lemmy currently does. That helps finding communities that you have not subscribed to yet (but are already known to your instance). But automatically loading all the comments as well seems a bit too much to me.

We are talking about a feature that makes it easier to view comments, so general concerns about the feed concept aside (I find it a bad idea), it seems like forcing people to block communities so that their comments are not inserted into threads they are otherwise interested in seems counterproductive. It would be better to only show comments from communities that the user has actively subscribed to before.

Like for example I might be interested in the discussions happening on [email protected], but the comments in threads at [email protected] is something I would rather avoid. So this feature would force me to block [email protected] which is the opposite of making it easier to read the comments from communities I am actually interested in.

What happens if a thread is crossposted into another community that your instance knows about, but which you are not subscribed to?

I think it would be good to only display comments from communities you are already subscribed.

Lets agree to disagree on the “natural” centralisation aspect, which is IMHO nonsense. And very recently the US empire was beaten by some tribes in Afghanistan, so I think your argument needs some further thinking 😏

The reason it gets so much more expensive after a few thousand users is complexity. Up to that point a single server can be used and the necessary sysadmin skills are not very high. Basically anyone with a few weeks of training can rent a server and run such an instance.

After a few thousand users it gets steeply more complex, when you need to think about running a database cluster and load-balance the frontends etc. Not very many people have the necessary skillset for that, and even less are volunteering to do this. So you end up being forced to hire someone expensive with a high in demand skill. Basically your operation suddenly jumps from an easy to fund with donations volunteer effort, to a must commercialize or otherwise fund venture that is highly unsustainable in the short term.

As someone who runs a Lemmy server I can tell you that it isn’t as simple as that.

Yes, there is an initial benefit from having more users on an instance, but this initial scaling benefit isn’t linear. It rather abruptly stops at a few thousand users and after that it becomes much harder and more expensive to scale further. Only after going over that hump it might become cheaper again at the scale of hundred-thousand of users or so, but Lemmy the software is currently also unlikely to scale as a single instance to such numbers, so it isn’t just a system operator question.

So no, unless you want to fully commercialize the Fediverse and bring in external investors to fund the getting over that initial hump, semi-centralisation is not a feasible way forward. And what would even be the point of that? Reddit exists and is basically the same.

Luckily ActivityPub is designed to scale horizontially through lots of smaller (but not tiny) instances, so I think we can manage without the above.

This is a terrible distribution and the semi-centralisation and gatekeeping by the established actors is one of the reason email is dying.

I think we can do much better than that 👍

Wait for the next hardware upgrade and then set up a new system while keeing the old system running in parallel.

It requires a bunch of browser features that non-user browsers don’t have, and the proof-of-work part is like the least relevant piece in this that only gets invoked once a week or so to generate a unique cookie.

I sometimes have the feeling that as soon as some crypto-currency related features are mentioned people shut off part of their brain. Either because they hate crypto-currencies or because crypto-currency scammers have trained them to only look at some technical implementation details and fail to see the larger picture that they are being scammed.

This goes to the main developer, which is a person in Canada. But I think they have a few collaborators that will likely get on board more now that they want to set up a non-profit (?) foundation to manage the Pixelfed codebase and IP.