jorams

That's correct, that's why the hourly billing makes it more complicated. If you don't use cloud storage the entire month you only pay for the time you do use it, and you only get included quota proportional to the amount you pay for. The sum of hourly costs is capped at €5 per month, which is also how it works for their VPSes.

It's not explained very clearly and made more complicated by being charged hourly instead of monthly, but essentially there's a minimum charge of €5 per month, which includes 1TB of storage and about 1TB of bandwidth.

Their VPS hosts have a 10GBit uplink, but they offer no bandwidth guarantees per VPS and state you can expect 300-500MBit/s[1]. Their dedicated servers have a 1GBit uplink with guaranteed 1Gbit/s bandwidth.

[1]: https://docs.hetzner.com/cloud/technical-details/faq#what-ki...

The creation of a list in the Gleam example is a choice, you could replace 'list' with 'iterator' and it would be lazy.

For what it's worth, it appears the paper "Everything we know about CRC but afraid to forget" was originally published as part of the release of crcutil on Google Code[1]. This is a hg repository with one commit that includes the paper, the source of the paper, and an implementation.

[1]: https://code.google.com/archive/p/crcutil/

The second half of the video is about the people who ran this project and that it was indeed done for fun. They gave a talk at DEFCON. They had a website explaining everything[1]

[1]: https://web.archive.org/web/20100413212320/http://projectevi...

I did, it does not change what I said. uBO works perfectly fine on Firefox Mobile and doesn't use much battery. People can prefer uBOL, but that doesn't make it important to the ecosystem.

The purpose of their comment is to correct your statement that:

> perhaps they should at least make a carve out for one of the single most important extensions that exists.

uBOL is not an important extension on Firefox.

I'm sorry but if you think 99% of people here would consider this an acceptable approach to licensing I think you have a weirdly low opinion of this forum:

> We thought the license in the root repo wasn’t that important, so we just generated one that we thought was open.

No part of this sentence makes any sense to anyone remotely informed about licensing.

> If I dismiss a tab the "you dismissed a tab" popup blocks the view of the next tab.

This only happens if you close a tab just above the bottom of your screen. You can scroll the entire list up past the point where any tabs will be obscured by the toast (which has an undo button), and it even does so by default when you open the list with one of the lower tabs active.

To reproduce your complaint I have to either explicitly scroll the tab I want to close into the area that will be obscured, or I have to have a tab higher in the list active, then open the list, and then close one of the tabs at the bottom of the screen.

> If I full-screen a video, the "you fullscreened a video!" message blocks the entire video progress bar so I can't move forward or back.

This is/was indeed annoying. It's been resolved in a recent update for me on Beta.

I've never seen the other two things you mention and I can't reproduce them, but they don't seem like UX issues, just bugs.

It is indeed true for LibYAML, which is used by Python, Ruby, and the Haskell yaml package. The majority of YAML implementations I've seen that aren't based on LibYAML implement 1.2. I'm pointing it out because it's highly implementation dependent.

YAML says keys MUST be unique, while JSON says they SHOULD be unique. It is therefore possible to produce technically valid JSON documents that aren't valid YAML, so it is in that sense not a strict superset. At the same time those documents aren't portable across JSON implementations either. Rejecting duplicate keys is a valid implementation of the JSON spec.

Your post's remark about YAML 1.2 being opt-in with a "%YAML 1.2" directive is true for the parser you are using (LibYAML), but is not compliant with the 1.2 spec. The spec specifies it should assume 1.2 and 1.1 should be opt-in.

The YAML 1.0 spec says no such thing, it doesn't even mention JSON. Neither does the YAML 1.1 spec. The YAML 1.2.0 and 1.2.1 specs do say exactly that. 1.2.2 no longer does, but it reiterates that the primary focus of YAML 1.2 was to make it a strict superset of JSON.

Your reading doesn't really make sense. Other browsers don't implement the specification. Firefox does. The specification is very explicit about how this violation should be treated. Those webservers and websites have a broken implementation. Had they tested with any spec compliant client they would have noticed it being broken.

> Nobody is asking them to do that. They are being asked to review C patches to enable Rust-in-Linux.

My understanding of their issue is that this can't really be true. Any C code that affects Rust bindings in any way (which will be more and more as long as the integration grows) will become impossible to change without either knowing Rust or hoping/waiting for someone else to pick up that part.

Rijkswaterstaat publishes quite a lot of information online. Water levels can be seen on a map[1] on waterinfo.rws.nl. It also offers access to historic data in CSV format, but that is handled through a wizard and you get the data by email apparently.

Information about sluices, bridges, etc. can be found on vaarweginformatie.nl, including the live status of many of them. The Ijmuiden sluice complex doesn't have a live status it seems. See [2] for the map.

[1]: https://waterinfo.rws.nl/#/publiek/waterhoogte [2]: https://www.vaarweginformatie.nl/frp/main/#/geo/map

> This is the first thing new user sees.

The vast majority of WordPress users, and even many people who call themselves "WordPress developers" never look inside the database. WordPress is, in almost every way, a terrible platform to develop on. What saves it is backwards compatibility, an enormous ecosystem, and being relatively easy to use for everybody who needs to use it.

Based on [1] it looks like System76 does actually think about accessibility, but it's not upstreamed yet.

[1]: https://github.com/iced-rs/iced/issues/552#issuecomment-2180...

Ah, I interpreted that as the traffic moving over, but it could indeed mean an increase in traffic.

> So, switching the domain to buttondown.com brought an uptick of traffic quickly.

Where did you get that from? The blog post says no such thing.

I don't think endorsing the new framework is something the DPA does. The EC declared the new framework adequate[1], Uber got certified for it[2], so there is now a valid method in place for Uber to transmit data.

[1]: https://commission.europa.eu/document/fa09cbad-dd7d-4684-ae6... [2]: https://www.dataprivacyframework.gov/list (no deeplinks for some reason)

This article[1] by the Dutch DPA has some details about it: The Privacy Shield was invalidated in 2020, leaving only the Standard Contractual Clauses as a valid transfer tool. Uber stopped using Standard Contractual Clauses in August of 2021, before adopting the new Privacy Framework in 2023. For a period of two years they were transmitting extremely sensitive information without a valid way to do so.

[1]: https://www.autoriteitpersoonsgegevens.nl/en/current/dutch-d...

A weird aspect of the reddit API crackdown is that they never actually shut down unauthenticated access to the API. rif is fun also still works (or worked last time I started it a month or two ago), it's just read-only. The JSON endpoints Geddit uses are the reddit API, and it's wide open, so in no way is it "bypassing API restrictions".

In the PDOK viewer linked above you can enable the "Adressen" layer[1] and it will show markers on everything that has an address. Everything that has an address has a postal code, which is listed in the details if you click the address. (There might be an exception with an address but no postal code somewhere, I'm not sure, but not here.)

[1]: https://app.pdok.nl/viewer/#x=124175.54&y=471068.96&z=11.290...

Here's the same page on the better wiki: https://minecraft.wiki/w/Tutorials/Redstone_computers

Manifest v3 is an effort to make a browser slightly better at its core feature, that it is importantly already fine at, at the cost of making it worse at serving the user. The internet is increasingly user-hostile, and manifest v3 makes it harder to fight back.

The fees I'm proposing are the exact fees Apple has been charging since the beginning and that have kept them extremely profitable all along. They are higher than the fees they charge for macOS, and they're doing fine with that. All the new fees Apple is introducing are extra, and they are for things that don't need to involve them.

The actual solution is very simple, and wouldn't even need the EU to "look at it": They charge consumers for the hardware and the OS, they charge developers the $100 per year for the tooling, they charge however much they want to sell apps on their app store, and they stop restricting and demanding to be a party to anything else.

RFC 4180 says it "documents the format that seems to be followed by most implementations" and in practice I find that to be true, though my CSVs don't interact with a lot of very old software. You get very far by treating "RFC 4180, UTF-8" as a standard and considering every implementation that doesn't follow it to be broken. I'm not sure I have ever seen software that simultaneousy doesn't follow the RFC, but does consistently support escaping.