jorams

It is also available in the Vaultwarden web interface (which is just a rebranded Bitwarden web interface).

The term "gatekeeper" is strictly defined in the DMA and currently doesn't cover the Chrome Web Store. Perhaps in the future it will. The DMA and DSA don't strengthen the big American companies; it rather specifically targets them. Smaller players can do whatever they want.

> Omarchy has some how managed to attract 134/782 open/closed PRs [1] vs 6/90 for CosmicDE (since 2022) [2]

You're linking to the PRs on one of many Cosmic repositories, the top-level wrapper repository. The total number of PRs on all Cosmic repositories it includes is far larger than Omarchy.

This article is just a lie and also seems deeply confused. First it talks about the (false) claim that you can no longer count a yearly contract as such, then it switches to "involuntary churn" without at any point explaining why those concepts are related in any way.

The regulation[1] explicitly says:

> Nothing in this Regulation prevents a customer from compensating third-party entities for support in the migration process or parties from agreeing on contracts for data processing services of a fixed duration, including proportionate early termination penalties to cover the early termination of such contracts, in accordance with Union or national law.

[1]: https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng

Your screenshot shows a menu in which features, namely the menu bar, have quite explicitly been removed from the default layout because you are unlikely to use them. You are showing the second tier of a menu structure where they are available if you need them occasionally. If you happen to need them more often you can easily add them to the toolbar.

It's been in the title of the RFC since 2018 and practically every mention I see is formulated as "DNS-over-HTTP (DOH)", so I imagine that's pretty rare.

As pointed out by amiga386 both here[1] and in earlier posts, macOS is not actually compliant with the Unix spec and never has been. This has apparently not been a hindrance for the certification of every single non-compliant version. Unix certification for Apple might not involve anything other than payment.

[1]: https://news.ycombinator.com/item?id=45239534

That is covered in the article:

> Recently, however, that long-held truism has been shaken: The show has started releasing statistics about buzzer attempts, revealing that some contestants, especially those in the game’s upper echelons, ring in much more often than others. It’s not that the buzzer doesn’t matter—it just matters much less than was previously believed, a shake-up that has reelevated the importance of subject-matter expertise.

Sounds like a good development, but some statements in the post are a bit odd to me:

> Your app has styled-components. That's not changing today. But it doesn't have to be slow while you figure out tomorrow.

It always was. You decided to make it slow and were fine with it, not sure why that's suddenly unacceptable.

When they got hacked three years ago the notice included this:

> Even though all account passwords that could have been accessed were hashed (with bcrypt plus salted and peppered) and secured in accordance with best practices, out of an abundance of caution we are requiring all Plex accounts to have their password reset.

Whether that later changed for the worse is anyone's guess.

Two paragraphs from the article that I think sum it up pretty nicely:

> Judge William Alsup at the hearing said the motion to approve the deal was denied without prejudice, but in a minute order after the hearing said approval is postponed pending submission of further clarifying information.

> Alsup said class members “get the shaft” in many class actions once the monetary relief is established and attorneys stop caring. He told the parties that “very good notice” must be given to class members to ensure they have the opportunity to opt in or out, and protect Anthropic from potential claimants coming out of the woodwork later.

Essentially he has concerns about missing details in two directions:

1. How class members are going to get notified, submit claims, and paid out, what works are even included, and the involvement of an army of lawyers that shouldn't be paid from the settlement.

2. How this deal is going to prevent Anthropic getting sued for cases that should have been covered.

> Kagi gets talked about on here constantly, and it's not even on the list (though I suspect there's a reason?)

Not that I'd expect them high up on the list, but Kagi sends the following response header:

    Referrer-Policy: same-origin

As a result the browser won't send a Referer header with outgoing links, completely excluding them from this report.

> You know something's broken when Microsoft gets to claim to be the biggest backer of open source.

They can say whatever they want. They're just lying. If you spend even a little bit of time looking into it you'll find it's just a marketing strategy.

FWIW: RAID 5 and 6 having problems is not a random hole you'll accidentally stumble into.

The man page for mkfs.btrfs says:

> Warning: RAID5/6 has known problems and should not be used in production.

When you actually tell it to use raid5 or raid6, mkfs.btrfs will also print a large warning:

> WARNING: RAID5/6 support has known problems is strongly discouraged to be used besides testing or evaluation.

Namespaces aren't so much a concept in Elixir, but this refers to the names used for things like modules. Expert will rewrite the code of its "engine" so that the engine's code and dependencies and those of the application it is embedded into don't overlap.

Wikipedia also says the same thing, both in English and in Japanese, and in both languages uses this report[1] as the source. This in turn sources a medical journal and a report by a mountaineering club. I don't know Japanese and can't really check whether these are reliable sources that actually exist. Essentially what this report says is that after WWII, particularly in the late 50s and the 60s, there were lots of climbers and unsafe routes, causing a large number of fatalaties. Afterwards there's a sharp decrease, though still pretty significant numbers.

[1]: https://soka-yamanokai.com/study/study18.html

Those are not comparable dates. The Zig "first appeared" date is a few months into development by Andrew in his spare time. The Rust "first appeared" date is after 3 years of development by Graydon in his spare time, followed by 3 years of development by a Mozilla-sponsored team of engineers.

You may be confusing the general concept of Publish-Subscribe with PubSubHubbub, now standardized as WebSub, which is a web standard implementing the concept.

> Are there more examples?

Practically every WordPress site with one of the top two SEO plugins (I'm not familiar with others) serves XML sitemaps with XSLT. It's used to make the XML contents human readable and to add a header explaining what it is.

> If they were willing to sell movies and tv shows WITHOUT DRM, I’d happily buy what I want

So much this. I take the simple moral position that I won't pirate things I can reasonably buy. That includes almost all music, and almost no movies, TV shows, comedy specials, etc. I still largely avoid pirating things and seek out alternatives instead, but I don't feel bad about it when I do because it's an industry that doesn't consider me a potential customer anyway.

Almost every laptop that isn't a MacBook has an insert key. The only other manufacturer I've seen leave it out is HP, and then only on some models.

Two of them being at 0.5 brings the total to 1.5 vCPU, which over an entire month adds about another 375 compute hours for an extra $60, which is still much lower. Indeed autoscaling seems like it could be the cause. According to the documentation that's a setting you can configure per "compute", but I don't know if it's the default.

They charge €0.50 per month to add an IPv4 address. A shared IPv4 NAT gateway introduces a whole lot of problems for them just to support customers who need IPv4 but don't want to pay a tiny amount for it.

Having plugged your numbers into the pricing for both Neon and Planetscale I'm rather confused. At Planetscale, given the numbers cited in the post, you're paying for 4 servers (+ replicas) with one eighth of a vCPU each, running 24/7. That's equivalent to about 375 Neon compute-hours per month. Your $69 Neon plan included twice that. Neon only goes down to 1/4th of a vCPU, but that does include the same amount of memory as the 1/8th at Planetscale, so take that 4 times and you have 4 databases running all month for the price of your $69 plan at Neon. How did you get to $250?

The "on average" is doing an awful lot of work. Some cells are never replaced, some organs are replaced every few years or even partially over decades, some organs are replaced every few months (one of which is the skin).

Tattoos however, IIUC, sort of "float" between cells, and as those cells are replaced one-by-one the ink is kept in place by the surrounding cells that are still there.

> as far as I'm aware, it simply taxes you on all assets as if you disposed of them the day you leave.

That is also what Germany does. The 13.75 multiplier is the fallback number used if there is no valuation for the company. It's such an irrelevant number that tax advisers writing about the topic don't even bring it up. Get a valuation.

They paraphrased what you said in the thread, but I don't think it's much of a misrepresentation.

You may have "been one of the most vocal proponents of synced passkeys never being attested to ensure users can use the credential manager of their choice", but as soon as one such credential manager allows export that becomes "something that I have previously rallied against but rethinking as of late because of these situations".

There may not currently be attestation in the consumer synced passkey ecosystem, but in the issue thread you say "you risk having KeePassXC blocked by relying parties".

The fact that that possibility exists, and that the feature of allowing passkeys to be exported is enough to bring it up, is a huge problem. Especially if it's coming from "one of the most vocal proponents of synced passkeys never being attested", because that says a lot about whoever else is involved in protocol development.

> If you assume that YAML 1.2 is the default, you don't need that nasty %YAML header.

Indeed the YAML 1.2 spec says a document without a YAML directive should be assumed to be 1.2[1]:

> A version 1.2 YAML processor must accept documents with an explicit “%YAML 1.2” directive, as well as documents lacking a “YAML” directive. Such documents are assumed to conform to the 1.2 version specification.

It's only the YAML 1.2 spec that says it's a superset of JSON. The YAML authors weren't aware of JSON when publishing version 1.1[2]:

> The YAML 1.1 specification was published in 2005. Around this time, the developers became aware of JSON. By sheer coincidence, JSON was almost a complete subset of YAML (both syntactically and semantically).

> In 2006, Kyrylo Simonov produced PyYAML and LibYAML. A lot of the YAML frameworks in various programming languages are built over LibYAML and many others have looked to PyYAML as a solid reference for their implementations.

> The YAML 1.2 specification was published in 2009. Its primary focus was making YAML a strict superset of JSON. It also removed many of the problematic implicit typing recommendations.

The middle paragraph there is the reason this is a problem people keep running into: Most implementations are based on LibYAML, which is an implementation of YAML 1.1 that does not really support 1.2[3]. Indeed the last example from the post doesn't actually work for me on Ruby 3.4.4 with LibYAML 0.2.5. It produces the exact same output as the one before it.

[1]: https://yaml.org/spec/1.2.2/#681-yaml-directives

[2]: https://yaml.org/spec/1.2.2/#12-yaml-history

[3]: https://github.com/yaml/libyaml/issues/20

> I would never visit a site like pornhub in a profile that I was logged in to anything other than similar sites.

But that's not relevant. The popup appears whether you're logged into a google account or not. It's just an extremely annoying popup that appears all over the web.

For what it's worth I checked for The Netherlands, and the data can be correct if they always round down.

In 2021 The Netherlands had ~17.5 million inhabitants[1]. 99 people drowned[2], of which 19 were from different countries. Per 100 000 that's either 0.56 or 0.45.

In 2020 The Netherlands had ~17.4 million inhabitants[1]. 138 people drowned[2], of which 31 were from different countries. Per 100 000 that's either 0.79 or 0.61.

This is of course dependent on the per 100 000 being inhabitants. If it includes tourists the rates go way down, because millions of people visit. For 2020 and 2021 it adds 7.2 and 6.2 million people respectively, for non-pandemic years closer to 20 million[3].

[1]: https://www.cbs.nl/nl-nl/visualisaties/dashboard-bevolking/b...

[2]: https://www.cbs.nl/item?sc_itemid=7491f794-6e63-4556-bdcc-d9...

[3]: https://opendata.cbs.nl/#/CBS/nl/dataset/82059NED/table?dl=C...