Civil servant's info is public information (at least in Finland it is).

It's good that bureaucrats can't hide behind bureaucracy.

They are afraid more of their own citizens thn of Americans. That's the reason for secrecy. At the same time, Danish officials push for chat control - a fascist Stasi-like initiative of mass spying on citizens, with a deliberate exception of government officials.

>They are not the ones with the power to decide what happens

This is a very naive interpretation. Bureaucrats have MASSIVE amount of power and control, and in actuality decide many things and how the law is written.

It's so sad that node refuses to add websocket server support.

Adding websocket would simplify stuff tremendously, as well as make deployments much, much more secure.

Why more secure?

I see that Deno has WebSockets, but I've never used them: https://docs.deno.com/api/web/~/WebSocket

Because it entirely removes dependency for external libraries and package repositories, like npm, for basic internet interoperability.

I (also) basically use only one package: ws.

"ws" is regularly the only package in my package.json

Same. Without that I could remove all npm dependence, which would greatly improve security.

If you're not tied to the ecosystem, why not switch to Deno?

I very much don't think this blog post passes any sniff test for anything to be taken seriously or given much thought, it's just political agenda posting.

However, there is an interesting question on how presidential physical and mental fitness is evaluated. Does anyone have insight into what rules and regulations govern this and do they have any (preferably supreme court validated) backing?

It's awful as a library, mediocre as an event space and not really good as a hacker space.

It's beautiful, though, but that's about it.

t. a Finn

Well, you have no idea how good you have it :,)

t. not a Finn.

Just proves that 16 bytes was too much, and we should have just gone 8 bytes.

I'm fine with 16 but they should have only used the bytes as they were needed, at least for 5 and 6 byte addresses, so those who desire short addresses could buy them.

My vrrp address for my dns server at home is 2001:8b0:abcd::53

It's about as easy to remember as 81.187.123.45//192.168.0.53

Almost all ipv6 addresses I encounter start with 2001, so I just need to remember my home prefix is 8b0:abcd, which is about the same length as my home public IP of 81.187.123.45

::53 means subnet zero host 53, which is easier to remember than which rfc1918 range I used (and basically is the equivalent of remembering the 2001:: prefix)

If I have an internal server I'd have on 192.168.4.12 I could address it with 2001:8b0:abcd:4::12 just as easily, with the "4.12" translating to "4::12", and the "81.187.123.45>192.168.x.y" translating to "2001:8b0:abcd:x::y"

Just because slacc gives you an extra 64 bits of randomness doesn't mean you need to use them.

At least on a LAN, you can set up like fe80::3 . I think. Now I'm not sure if I got that right.

fe80:: is for link local. You'd want to use something starting fc00:: or fd00::

In your typical home environment, just set your ULA to fd00::12 instead of 192.168.0.12, or fd00:16:34 instead of 192.168.16.34

Yes you'll run into issues if you were to later want to merge your private IPs with someone else, and you should use fd12:3456:7890::12 instead, remembering those extra 10 digits, but its not a problem at home, and no more of a problem with business mergers than ipv4 clashes anyway.

This is just plain wrong.

An extremely simple scheme is allowing voters to enter an identifier of their choosing and displaying that with the votes publicly. This is both verifiable and anonymous.

Any issues you can come up with this scheme are also iirc pretty easily solvable.

This is huge and amazing!