BlackEco

Unfortunately you can’t follow users on Lemmy. On Kbin, Mastodon and others, you can follow Bluesky users through Bridgy Fed but they must opt-in first by following @ap.brid.gy (which very few people do)

Okay, that makes much more sense.

Wait, is it required to mirror the entire Bluesky history? Can’t you just store only new messages? Because the storage requirements (4.5TB according to the article) make it almost impossible to self-host.

TIL that Schneider Electric is a French company. I always assumed it was American or Swiss.

I have been contemplating moving to SearNXG for a few weeks, but I have a hard time finding whether I can configure things like domain down-ranking/blocking or custom bangs and lenses, does anyone know if you can do that on a user or instance-level?

I still don’t get why Strava activities are public by default and why they do not make their users aware of it. I remember having to rummage through the settings to make activities private by default.

If you want an experience similar to Arc without the AI nonsense, there is Zen Browser, a Firefox fork with vertical tabs, profiles and side panel.

I’m not familiar with Nextcloud, but from reading the How to use this? section of the README I believe you can run it behind a reverse proxy:

--publish 80:80 This means that port 80 of the container should get published on the host using port 80. It is used for getting valid certificates for the AIO interface if you want to use port 8443. It is not needed if you run AIO behind a web server or reverse proxy and can get removed in that case as you can simply use port 8080 for the AIO interface then.

(Emphasis mine, in “Explanation of the command”)

My understanding is you only have to forward traffic from the reverse proxy to the port 8080. It uses a self-signed certificate though, so you might check if the reverse proxy you are using checks certificates signatures for upstream servers.

It is possible, what you’re looking for is a reverse proxy: it’s an HTTP server that will listen to the standard ports for HTTP and HTTPS that will redirect traffic to the chosen service based on the domain name or URL.

In your case, every subdomain would point to your VPS’s IP and traffic that’s for mastodon.example.tld will be seemlesly proxied to your Mastodon container.

Do some research on Caddy or Nginx, and I strongly recommend you learn Docker Compose and Docker networking, it will help you make it easier to maintain everything.

PS: CNAME pointing to A record is the way to go. You can do it one better by having a CNAME entry for *.example.tld, so that you don’t have to create a CNAME entry for every new service you deploy, but you better make sure that your reverse proxy won’t proxy requests to an unexpected container when requesting a bogus subdomain.

Firefox for Android with Automatic Reader View