homelabber

The thing is that right now it's not worth it to buy a raspberry pi if you want to selfhost. It is 4 years old at this point but it cost 50% more than when it was released.

Frankenstein is the name of the doctor, not the name of the monster

If I'm not mistaken to make your instance available to other people you'd have to set up a reverse proxy. And a correctly set up reverse proxy shouldn't reveal your IP, only the local IP (127.0.0.1).

I might be wrong, so ask on the [email protected], since it's more active than this community.

However renting a VPS and hosting your Lemmy instance there is probably a better idea if you plan on creating a community, since it will minimize risks (DMCA notices, bugs in the Lemmy source code that could expose your server, etc). And it would make scaling easier if your instance grows.

There isn't really anything like Spotify. There were attempts to use a service like Last.fm (which isn't self hosted) or libre.fm (which is self hosted but development has been stopped) to track your listening data. Then there were a couple discovery projects that worked with Navidrome (don't really remember the name but they're probably somewhere in r/selfhosted) but they haven't been very succesful.

Even if you somehow managed to solve those problems you've got the next problem which is the fact that you don't have the recommended song available in your library. Perhaps it could be solved wit Lidarr.

Personally I think Spotify is worth $10 a month.

On Mastodon there's a self-destruct command that in theory deletes your content from all of the instances that are federated with you. I thought the same command was on Lemmy but it might not be the case.

Then you would be right that the old posts should remain on the federated instances.

True, I'm not really concerned about the active users dissapearing, because most of them would just join the second biggest community about that topic.

I'm more concerned about the ammount of information/knowledge that would be lost.

I get what you say about not having a be-where-everyone-is mentality. But the fact is that following 15 communities about the same topic is really inconvenient, and people tend to congregate (look at how many users each instance has and you'll see that a few instances have like 80% of the total users).

If we want the fediverse to succeed we have to simulate centralization for a better user experience, while being decentralized. And that means that there should be some sort of protection to prevent whole communities from dissapearing.

Thank you!

A scary thing about the Fediverse right now is that some instances have many of the bigger communities. And the owners of the instance can literally shut it down at any moment (or stop federating with you).

And right now there isn't an incentive to keep instances alive.

Headscale is an open source implementation of Tailscale

Ok so apparently it's a pinned post in their community.

Tldr Lemmy.world has open registration, which means more trolls/extremists and they are tired of dealing with them.

If I'm not mistaken both Beehaw and Lemmy.world are pretty big mainstream instances.

Why has Beehaw decided to stop federating with lemmy.world?

First I'd like to apologize because I originally wrote less than 30TB instead of more than 30TB, I've changed that in the post.

A colocation is a data center where you pay a monthly price and they'll house your server (electricity and internet bandwidth is usually included unless with certain limits and if you need more you can always pay extra).

Here's an example. It's usually around $99/99€ per 1U server. If you live in/near a big city there's probably at least a data center that offers colocation services.

But as I said, it's only worth it if you need a lot of storage or if you move files around a lot, because bandwidth charges when using object storage tend to be quite high.

For <7 TB it isn't worth it, but maybe in the future.

Depending on how much storage do you need (>30 TB?), it may be cheaper to use a colocation service for a server as an offsite backup instead of cloud storage. It's not as safe, but it can be quite cheaper, especially if for some reason you're forced to rapidly download a lot of your data from the cloud backup. (Backblaze b2 costs $0.01/gb downloaded).