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.
They also moved its date to June in order to move the Canada GP right after Miami in May, preventing a trip to North America in the middle of the European leg of the Championship.
I'm not sure what you mean. There is a list feature much like the one that existed on Twitter, but since I don't use it, I don't know if you can share lists.
Edit: I tried the List feature and it does not work like on Twitter (at least the way I remember it): it only can only contain users you already follow and is private. It acts more like a feed with only a subset of your follows.
I was thinking of benefits along the lines of merch shop, meet'n'greet, possibility to get autographs, etc. It is not clear if there will be such things ATM.
I really wonder what being there brings that watching the event live from home does not. (it has been confirmed that the event will be broadcasted live: "Fans who cannot attend in person will still be able to watch the action live, with broadcast details and further event information to follow in the coming weeks." )
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.
--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.
Okay, that makes much more sense.