3np

Germany specifically seems to have an out if it comes down to it.

https://en.m.wikipedia.org/wiki/Primacy_of_European_Union_la...

US interests are running the show.

I guess you can (soon) go live in a Thiel enclave of your choice and find out.

Meta is obviously Bad these days. I advise not engaging and giving them more money and insight into your life and business.

In the other direction, in East Asia they go "A-P-P" for app(lication) (:

I think I've even overheard M-O-D for mod(ification).

Anthropic having to raise a new round doesn't sound "catastrophic"...

Do you also believe it plausible that aside from redacted parts, this module has not been changed in any way on production servers for over 2 years (last commit is spring 2023)?

More importantly, avoid yarn[0] if you have a choice. They do not have a security posture fitting for 2025. There's way too much assumptions like "helpful" "magic" guessing/inferring what the user "actually wants" to "make things just work". See also: corepack.

[0]: legacy 1.x projects aside

This is not believable. It's not syntactically valid Python.

https://github.com/twitter/the-algorithm/blob/c54bec0d4e029f...

> For all the controversy DOGE has generated, its time at the Social Security Administration has not amounted to looming armageddon, as some Democrats warn. What it’s been, as much as anything, is a missed opportunity, according to interviews with more than 35 current or recently departed Social Security officials and staff, who spoke on the condition of anonymity mostly out of fear of retaliation by the Trump administration

There's a contradiction there. Fear (and real risk) of retaliation from the White House for speaking up is a new and bad thing.

It's likely the phrasing more than the idea. If you want to raise controversial talking points, predictable quips like that ain't the format for it.

Good to see

I think one source of confusion is that many probably see "Chat Control", expecting it to be a reference to one specific proposal or legislation (a la "GDPR" or "DMA"), while it's an umbrella term you use to group different proposals pushing the same agenda and end-results. Readers look for one face to point at but it's a hydra and they just leave confused.

Clearly defining the term and its intended meaning would do well, I think.

I believe even Raspberry Pi4B and 400 are still only having first-class drivers for 32-bit?

Kiosks and desktops and whatnot on Raspis still on 32-bit and likely to have Firefox without telemetry.

Food: In order to survive and thrive, we need to balance our nutritional intake (lest we die of malnutrition). We all do this. Yet for most of us, calories is not what life is about. For many of the privileged of us, it's barely what eating is about. Over-obsession with calorie-counting can become a sickness as much as neglect and overeating.

Same with your money as participant in the economy. Maintaining a healthy flow and preparing for the future is a good idea. But remember that fundamentally money is supposed to be a measure of value, not value itself (the tragedy of our society is confusing the map with the territory).

Continue focusing on impact and the money will follow. At the same time you still want to have a healthy balance and stable trajectory on the day-to-day and month-to-month without that turning into minmaxing or letting it direct your life-choices to an unhealthy degree. You'll probably want some form of income - not necessarily in the 1%.

> Signal's threat model has never included "you are directly messaging an adversarial party and expect to retain control over redistribution of those messages".

On the contrary.

https://signal.org/blog/signal-doesnt-recall/?pubDate=202508...

> This is so incredibly important! I am very happy to see this, the fact that you could not do a backup on iOS and you would lose everything in case your device dies is the biggest drawback of iOS.

FTFY. It's originally Apple preventing its users from easily controlling their own data.

I recommend you read up some more on prior art and work before digging the design deeper.

Good insight and goes along with keeping abstraction layers from leaking in any direction best you can.

You can start with the wireguard only and see how that works.

You can "dry run" by setting up a local staging server on your LAN (using some nonblocked sites to test) first and then replicate on the VPS.

Try to get comfortable with tcpdump and wireshark to troubleshoot and verify.

Recommended to use some configuration management (ansible or whatever you prefer) so you can easily jump to a new provider if need be in the future.

If things are working fine locally but not on the VPS, that's when filtering may be at play (also check your MTUs; this is where tcpdump is your friend). You can add obfuscation under wireguard (meaning wg will be running on top of another overlay network). Shadowsocks used to be recommended. These days the Chinese are at the front of the game. Search for shadowsocks successors and you will find.

Sometimes openvpn (tcp) works more reliably where wireguard (udp) doesn't.

Also take care of your DNS. Check for leaks.

Sometimes it's more straightforward and can be safer to set up a forwarding HTTP or TCP proxy on the VPS (and/or locally: these can be chained) and configuring that in your browser/apps rather than straight up routing all traffic over the tunnel.

Consider how much you trust the VPS provider and its infra provider(s). If you want to be more careful you can set up multi-hop, exiting either via another VPS on a separate provider or a commercial VPN provider. Using a commercial provider for your exit can help improve anonymity wrt to the sites you visit (since your IP won't be unique from their view).

Oh, and do try to get off facebook, youtube, instagram, reddit, discord. It's really time to migrate for several reasons. Try to find better online connection points for your friends and family, as well as connecting to the world, than US Big Tech (yes I see the irony in saying that here).

It does sound like making your site and going wild there is a better approach than contaminating HN threads with LLM-generated comments.

While it will probably be appreciated as a "Show HN", please refrain from spamming links to it in threads here.

No. And it's not just "anti-AI folks" who consider it spam and noise to copy-paste LLM summaries into a discussion forum.

looking at the OP account history: HN comment engagement

Please refrain from using duplicate accounts to circumvent flagging.

https://news.ycombinator.com/submitted?id=FerkiHN

https://news.ycombinator.com/newsguidelines.html

https://news.ycombinator.com/item?id=44613792

no, no forwarding. have the client contact all sites directly.

> What if he changes the code and forward a false data:

Presumably you will find a cryptographer to help you construct a scheme preventing this via cryptographic signatures. You'd do well to investigate prior art.

I think it's a very important and interesting problem you're tackling and you probably need to iterate a bit further on several points of the architecture and protocol.

As to your main question re the proxy: Why is there a proxy in the first place? The client could just make the same requests the proxy would directly to the multiple parties, obviating the for it, no?

> If you had multiple datetime values from different timezones in this representation, you wouldn't be able to sort them so that earlier ones come before later ones.

That's irrelevant.

Besides, you could, assuming you have a timezone db on the side.

> If they were instants in time, you would be able to do that.

How do you synchronize with and translate to timezones in Andromeda?

And I am saying that storing it verbatim as the string "13:00 on the 12th Sept 2025 Europe/London" is an instant in time as much as any other formats and types you can come up with. Just not very parsable by your typical stdlib.

It all boils down to picking the appropriate reference frame, which varies by context. I believe your point should be that there is no single universally applicable reference frame for mapping all future events to future cultural time (and/or that in any case it's not UTC).

"13:00 on the 12th Sept 2025 Europe/London" is already (a pointer to) an instant in time as much as any unix timestamp. Just a different reference frame. Now it's true you can not know in advance what UTC time will be at that moment which may bring practical concerns if one wants to synchronize that with a contemporary typical computer system clock. It would be true to say that not all points in time can be reliably stored as unix timestamps[0].

Recalling Einstein and that such a thing as global time reference is fundamentally impossible, you're nitpicking while being technically incorrect.

[0]: but please keep defaulting to it in code unless you really know why lol

https://doi.org/10.5281/zenodo.17070518

And what did you learn from what article, actually?