Fresh versions of Firefox-ESR, Brave and Opera made it for the moment, however you need to find a way to allow them cookies while they persistently re-iterate, disabling our settings window. I find it absolutely unacceptable behavior to lock people out of their data - their property - without providing comprehensible reasons such as 'your browser is too old, only versions from xxx are supported'. And if this doesn't happen automatically, it should be communicated immediately in support requests. The way it is done, despite all good intentions, are malicious experiments with the users.
Anyone else unjustified blocked by TecharoHQ/anubis?
Experience a silly 'Oh noes!' page and no help in the bug tracker ( 'we are new and experimental, pls. contact your sysadmin' ). Affected site: gitlab.gnome.org/GNOME .
Author here - yes, I know about robots.txt! This is one of those cases where, because I was already looking at data in one place, I implemented the fix I could in the same place :p I do plan to add a robots.txt and contribute one upstream as well.
Maybe so, as what we're doing in absence of proper docs is rightly classified as something worse than alpha. The best docs they had so far up to this point:
These are great, for someone who knows Kubernetes. You should understand that creating the tailscale subnet router as a pod directly means the connection is not resilient. It's also key to understand that tailscale will break if you have more than one instance of subnet router at a time, so substituting Deployment in place of where these docs use Pod is not a really good choice without some fine tuning because of the risk that a rolling update creates another copy of the pod before the old one has shut down.
Maybe stateful set, if there was a way to permanently imply that statefulset can only have one replica. I appreciate the link anyway. I figured all this out on my own, and I'm using tailscale productively with Kubernetes based on the old docs, with my open source project. Tailscale has a great and generous free software tier for supporting OSS maintainers. :tada:
I wrote about this pretty recently, but the short version is a mix of NixOS and a k3s-based Kubernetes cluster using Tailscale to connect everything together.
If only applications sent their notifications through e-mail.
I particularly miss the times when Facebook would send notifications to your e-mail, with full content included, within minutes to hours of an event, if you happened to be logged out from the service. This was a neat way of reading chat messages without making the sender aware you've read them (that was before the whole thing got separated out to become Messenger).
EDIT: one major benefit of e-mail as notification channel is that a typical non-ISP personal mailbox has practically infinite storage and a sensible search mechanism, giving you historizing/archiving for free.
Taildrop (https://tailscale.com/kb/1106/taildrop/) mostly filled this for me, although this is just for the same Tailnet. AirDrop is also pretty slick. Otherwise I chuck it onto my NAS.
Of course all of these solutions have some serious pre-requisites...
The TL;DR is there isn't much difference besides the protocol being used. Tailscale published their own comparison that seems pretty fair to both sides (they do this for a few other options as well) https://tailscale.com/compare/zerotier.
And I /just/ got my infrastructure bits and pieces running Litestream! Guess I'll have to figure out if it's worth switching to this -- my gut reaction is no, since I only really run one pod at a time, so Litestream serves the purpose of not only saving the database offsite but also restoring it. But I will be keeping a very close eye on this thanks in part to my love of SQLite.
Hats off to Ben and Fly.io, you're doing some cool stuff.
As an ex-CircleCI employee, this is really exciting because it marks a pretty significant milestone in a particular internal effort. Very much looking forward to what comes after this.
This might strike some as a weird event (Gitlab already has CI/CD!), but it _was_ highly requested and is (probably) of other similar things coming to fruition!
