tofu @ tofu @lemmy.nocturnal.garden

Posts

6

Comments

150

Joined

4 mo. ago

I'm really not sure about that being inexpensive. The files will grow and the list of people to follow usually grows as well. This just doesn't scale well.

I follow 700 people on Mastodon. That's 700 requests every interval. With 100-10000 posts or possibly millions of interactions in each file.

Of course you can do stuff like pagination or something like that. But some people follow 10000 accounts and want to have their timeline updated in short in intervals.

Pulling like this is usually used when the author can't sent you something directly and it works in RSS Feeds. But most people don't follow hundreds of RSS feeds. Which reminds me that every mastodon profile offers an RSS feed - you can already do what you described with an RSS reader.

But only once. If an account doesn't post/interact for a year, it doesn't cause any traffic. With your approach, I constantly need to pull that account's profile to see if something new showed up.

So I have to constantly check all files from everyone I follow for new entries in order to have a working timeline?

The answer to the first two questions are helm charts. They are collections of parametrized yaml files and the most popular way to install things into k8s. You just need one config file for each helm release (values.yaml).

If you want to go declarative with gitops rather than imperative, check ArgoCD or flux.

That's just how it is. You can only see favs if the post is on your instance, or if the fav is from your server. A fav from a remote instance to another remote instance is not known to your instance.

It's the same on mastodon.social but not as noticeable because it's so big

It's not that difficult. You can create a second VM from the backup with a few clicks and move the necessary data with scp.

I'm sure they are glad they are protected from the free information war and that you, in true solidarity, are decidedly not helping them to gain free information access. 🫡

Not wrong, just saying that every Vaultwarden client is a backup basically since they cache everything and it doesn't expire.

Wtf are you talking about, nobody is climbing anywhere. By running snowflake, you are offering a piece of infrastructure that other people can use, it's not specific to the Iran. They can't install it themselves if the local internet is censored, that's the whole point of this.

It's the best we have. What's your specific problem with it?

Ofc! But since this is the selfhosting community I figured the Docker thing would be more practical. My laptop with the browser isn't always on.

You need a reserve proxy. That's a piece of software that takes the requests and puts them toward the correct endpoint.

You need to create port forwards in the router and direct 80 and 443 (or whatever you're using) toward the host of the reverse proxy and that is listening to on those ports. If it recognized the requests are for nas.your.domain, it will forward the requests to the NAS.

Common reverse proxies are nginx or caddy. You can install it on your raspberry, it doesn't need it's own device.

If you don't want that, you can create different port forwards on your router (e.g. 8080 and 8443 to the Raspi) and configure your service on the Raspi corresponding. But it doesn't scale well and you'd need to call everything with the port and the reverse proxy is the usual solution.

I can open the website. What exactly are you trying to achieve? Are you in some app?

Yeah I think of it the other way round: I couldn't get myself to organize them without combining it with a nice selfhosted tool. The goal is getting my stuff organized, the cost is doing work, which includes setting up a system. I can cheat on the cost a little by including a fun project in the cost part.

I do think there's a hidden cost in selfhosting though and it's maintenance. Fortunately, there's selfhosted tools that help with that too :-)

Isn't that the goal? If you have an old drawer full of unorganized stuff, implementing a selfhosted management tool is getting an organizer and thinking about how to fill it, but you still have to sort your stuff in.

The only selfhosted thing where I really have to re-organize is my documents in paperless but I'm so glad to finally have it all organized and searchable instead of some hot mess of an inconsistent folder structure.

I used to do this. Didn't know the tutorial but used this part of the documentation: https://pve.proxmox.com/wiki/Installation

I switched to have an unencrypted proxmox partition and have all VM disks on an encrypted partition, mostly to have reboot working.

My NAS ist almost exclusively backups. Just installed TrueNAS to have a GUI for ZFS and NFS.

The reason is easy: one likes the fediverse, wants to contribute for it and wants to enabled people to use it even if they can't afford to pay for it.

On a smaller scale, that's not much of a problem. I'm glad I can host for some people who don't have money at all. Some of the others donate and some don't and that's fine as well.

"Stranglehold" lmao. They invented the threadiverse and they are welcoming other implementations like mbin and piefed. That's the opposite of a stranglehold.

Go cancel yourself

Solarpunks can have a little downtime, as a treat