froggerexpert

Fair. I didn't know Bitwarden was open-core. In light of this, accidental packaging mixup sounds plausible.

> But one bad release with a license screw up and nobody is willing to give them an inch?

I don't have a lot of context on the issue.

Is it clear it was just a packaging bug, rather than a move towards partially proprietary?

Very cool. What program is that?

It'd also be nice if the colour was not just day/night, but the actual predicted daylight at the time of day, which would result in a continuously changing colour.

I guess at that point, the sine approximation from OP would no longer apply, and https://en.m.wikipedia.org/wiki/Sunrise_equation would have to be used.

Yes, exactly!

The sunlight plot is interesting.

Since Dec wraps around to Jan, you can fold the left and right to make a tube.

Since 23:59 wraps to 00:00 you can fold the top and bottom of the tube, making a torus (a donut).

For a fixed lat/long, each point on the torus corresponds to the sunlight observed at a particular time throughout the year. Why bother with a torus? The shape itself embeds the continuity of time across days/years that is otherwise left implicit in the typical 2D plot.

I've wanted to plot this in 3D or have it printed on a ring, but never got round to it.

Any one seen anyone do this?

Consider https://www.gnu.org/software/recutils/

Plain text, but with querying, and likely exporters/importers into calendars.

CardDAV.

I host this end-to-end encrypted on https://www.etesync.com/ .

I sync to my Android phone with the etesync app.

I use the Android contacts app to manage details.

I don't keep detailed records. Just contact details, how I know them, name of children, etc.

This is disappointing. I use gopass for my personal passwords, but had moved family passwords to Bitwarden, and selected that hosted provide becauser it was open source.

I will continue to vote with my wallet, with other open-first solutions like ente and etesync.

Part of why I do this is so that if the company changes direction, the community can potentially fill in.

With the momentum behind vaultgarden, maybe open clients will flourish too.

In spite of its wider adoption issues, it's valuable for my personal infrastructure: each of my services/machine has an IPv6 globally routable address.

Why bother, when I could just do TLS SNI reverse proxying via nginx?

* Some services don't use TLS, or even TCP.

* A reverse proxy is yet another intermediary in the chain.

* Plain IPv6 routing is simpler than reverse proxying, and I already need a network layer anyway.

There are downsides:

* some software doesn't support IPv6. I haven't experienced this on the Linux servers I run.

* in a dual stack network, now you have two networks! I use NAT64/PREF64 like https://labs.ripe.net/author/ondrej_caletka_1/deploying-ipv6... to have most clients only be on IPv6. They get IPv4 connectivity over IPv6 via NAT64.

* If I'm in another country then I often don't have IPv6 connectivity. In this case I use any VPN that offers IPv6 (and have one available via my home, via Wireguard).

* Learning IPv6 takes time, but not much. It's one-off. It's not more complex than IPv4, but it is different. If anything, it's simpler. (SLAAC rather than DHCPv4; IP reachability rather than NAT/port forwarding).

Great project, which has sorely been in need of a better name.

"Luanti" works. Unique, pronounceable, alludes to Lua ties.

I understand this is a sensitive topic, but I don't think it's fair to characterize robertlagrant's comment in the way you did.

Their comment looks similar to any other comment on technical/UX matters, including yours and mine.

I understand the happy case. When it works, great.

My critiques were on the sad cases:

* Presses <Ctrl><Ctrl><Ctrl>. Wait why isnt this working? Too late.

* Presses <Shift><Shift><Shift> on another sensitive site that doesn't implement this. Too late.

* Presses <Shift><Shift><Shift> on a poorly supported browser, or after the functionality is removed, or after it conflicts with OS-level (it might not today, but who knows about future OS updates)

> This seems like such a contrived scenario with a solution that only works for gov uk sites. Why not teach users how to switch or close tabs with keyboard shortcuts?

+1. "Close tab" is more robust, well-supported and well-known.

It seems more likely a user will load an inoccuous page as a decoy, than learn triple-shift is a quick exit.

Still, interesting read, to hear the reasoning. Would like to see empirical evidence/user testing.