eurg

All good. I tell people how to add another mailbox to their Outlook, "click here, now there". Not glorious. Necessary anyways.

Companies pay for it. And except for their DERP servers, free users don't cost them much.

Yes, but it tunnels arbitrary IP packets encapsulated in UDP.

So, the response is here. Without a closer look I can't say what's really going on - although I lean toward believing that Core is going in the right direction - but there still seem to be some orange flags.

Unfortunate. I'll wait some days for the response, but it better be a good one.

This behavior from Core may be par for the course, but I can already buy watches from companies that have values only for marketing. It's a small niche, and being nice would not cost much.

And they already died once, without having a proper off-ramp for their users - for now I don't trust them to exist in another two years. (I'm not really sure they even are in this for the long term - talk is cheap.)

Cities may find themselves in other countries easier than on other continents.

And also, some tools still break when using the non-default umask.

Yes, yes, we all run Postgres in containers, but if you don't, and you upgrade to a new Postgres major version, gladly using the Debian scripts that make it all more comfortable, while using umask 027, you will enjoy your day. Though I don't remember if those upgrade-scripts where from Debian proper or from Postgres.

Since that experience I always wondered what other tools may have such bugs lurking around.

I once had a colleague from Iran. Working (legally) in the middle of the EU. He was already blocked from using credit cards, but thanks to not-100%-US-dominance still allowed to use local banks. For such local banking he will likely need to have Play services.

It's not countries that are affected, but people. And people sometimes move.

All these announces are scenery and promotion. Very low chance any of these "corrections" were not planned. For some reason, sama et al. make me feel like a mouse played with by a cat.

Not just Postgres. It's in the SQL standard, and widely supported.

I'm not sure if you are serious or joking. "6 degrees of separation" is the famous radius for how many steps are needed such that everyone is connected.

https://en.wikipedia.org/wiki/Six_degrees_of_separation

Related to "iFixit created a new USB-C, repairable soldering system" at https://news.ycombinator.com/item?id=41521919

Europe is not a single country, and even a single country would usually not have perfectly homogenous laws in all is regions.

Can confirm, and there are worse offers prevalent than this. However, that's industry average, I don't know about the specific companies in question.

This was a nice overview, and I basically concur.

I want to add a few things.

Once you know your grinder, too high a max pressure is not so much of a problem, as choking a shot becomes a rare issue.

Consistently good Espresso is easier using a slightly coarse ground, but something needs to give, like texture or concentration.

Taken together, cheap machines can work well, although learning on them can be frustrating.

Use fresh roasts, and use them up quickly. Some days after opening a bag of not single dose frozen beans , many coffees lose their good aroma, and only the roast itself remains.

For a company I once worked, it was because the VCs held more than 50% of the company, and the founders - ultimately - didn't have a say.

Not nicely put, but not wrong. I had half an heart attack when that feature was rolled out, and the danger was split only between myself and a colleague. I can't even trust myself to not screw up. I needed another permanencied invocation of the principle of hope.

Both the bug list and the reaction to it are deeply concerning, if you are depending on this project - but I don't know how much real world use this code gets.

Shows that reviewing dependencies is not optional. Hundreds of stars on GitHub is not a helpful data point, even if my own monkey brain says otherwise.

KeePassXC even had the advantage that I only have to unlock once for both desktop app and browser extension.

BitWarden requires separate unlocks.

Note that CNAMEs is literally caused by GDPR

How so?

The failed agreements are meant to make it possible to legally use certain SaaS in the EU, at all. That such agreements seem to be impossible under current law, despite being attempted to create by parts of government, is the interesting part. EU governance is very non-homogeneous even w.r.t. desired results.

Matamo is a great option. Beware that - depending on mode - a cookie notice is still required even if everything is first-party only.

Most companies hope to sit it out non-compliantly until the law changes, and seek protection in numbers.

Given the strange situation of repeated, failed attempts at making a cross Atlantic agreement, I wonder how GDPR ever became law.

but they do however own the domain which you point to your server.

Not necessarily. .at domains are owned directly, the registrar is only a service provider handling the process.

I assume that for most other TLDs this will be different.

Do you have a link to an article about that? My google-fu is weak, and this sounds interesting - that should not happen to DNS - at all - and from the outside Route53 looks quite well managed. So what the heck did they do?

Hetzner has some attractively priced dedicated servers - for some heavier workloads that might be nice. Do they use a very different management API? (They have a cancellation period of "30 days to the end of the month", which would complicate matters.)

"legitimate" is doing a lot of work here.

Compression and content-addressing are two separate things.

Content addressing across accounts on private, AWS encrypted S3 buckets would run counter to their claims.

See also: https://news.ycombinator.com/item?id=31419121 "Bringing bcachefs to the mainline"

What were the most challenging technical problems?

While technically the customer asked for the solution to problem A, they wanted us to solve problem B, but we failed to invoke our inner patio11, and as a result delivered what they said instead of what they meant. A frustrating lesson for me. At that point in my career I should have known better already.

ETA: sibling comment about Cortex-M0 is spot on. You really start counting bytes. Some kiB of RAM sound a lot, but when you have to juggle several tasks, and don't have to option to write from scratch but instead reuse existing old code you've lying around, stuff gets dirty pretty quickly. Other team member was doing the hard work, I was just providing tooling for them.