tambre

You're on an network with DNS64 and NAT64 as its IPv4 compatibility mechanism probably.

One example of such an application is Adobe After Effects [0]. Or at least used to be, I no longer use Windows.

[0] https://tambre.ee/blog/adobe_after_effects_windows_utf-8/

Usage of Steam's DRM is actually optional. There are plenty of games that you can copy the files of and run on another system without Steam present. [0]

[0] https://www.pcgamingwiki.com/wiki/The_big_list_of_DRM-free_g...

For me: yes. Dreaming is the only experience that kinda matches the descriptions of others' mind's eye. Day to day? Just blackness, only the light that comes through the skin of the eyelids.

Also known as jumbo and single/combined source file builds.

Finnair at the end of last month suspended service between Helsinki and Tartu due to Russia's GPS jamming [0]. DME is being added next week and they'll resume service next month [1].

[0]: https://news.err.ee/1609328058/finnair-suspends-flights-to-t... [1]: https://news.err.ee/1609343694/finnair-restarts-tartu-flight...

I don't think that's known yet. But M3 was ARMv8.6-A and Apple's been keeping up nicely.

If Oryon is ARMv8.0-A then that's quite a disappointment. The LSE instructions are incredibly nice.

I'm guessing, but manta rays are flexible and can form vertical surfaces by how their wings flop. Or maybe they just can flop their wings different amounts to generate differing thrust for turning.

Neither is possible with todays technology. Adding a vertical control surface is a pretty easy solution though.

Seems it has the necessary integration points to run CMake builds as an external command. The same way you could build Make, Autotools, Meson or Bazel projects from CMake with the necessary external command plumbings.

Obviously both fille the same purpose of being a build system, though Bazel is also a build executor not just a generator. Integration would mean either adding BUILD language support to CMake or vice-versa, but you wouldn't get the particular benefits of either this way.

Yeah, rDNS is a hard requirement for IPv6. I believe you should get a hard reject for missing that with a pointer to the documentation.

What year was this? While I can't find a source I believe Gmail has supported IPv6 for sending and receiving since the World IPv6 day back in 2011. I've certainly been doing it since 2017.

Your issue might be rather that Gmail actually enforces all their guidelines on IPv6 instead of silently degrading your reputation behind the scenes like they do for IPv4. So proper RDNS, SPF and DKIM are tablestakes with DMARC and MTA-STS strongly recommended.

Checkout RCHD-SPARX [0]. You'll need to draw the rest of the owl, but the really hard part's there. I hope someone builds a switch on that.

[0] https://conclusive.tech/products/rchd-sparx-networking-som/

Run BOINC maybe? [0]

[0]: https://boinc.berkeley.edu/

Sounds like a good use for Multicast DNS?

Both recent GCC and Clang are able to generate the most optimal version for std::clamp() if you add something like -march=znver1, even at -O1 [0]. Interesting!

[0] https://godbolt.org/z/YsMMo7Kjz

But it isn't a password for Microsoft's services that's being sent. It's your username and password for another service you probably didn't intend Microsoft to have your credentials for. And it's intended.

The marital example is something I came up with, but not actually sure if that happens as I haven't gotten married myself. But it sounds something like that would exist so you can react to someone faking your identity and registering a fictive marriage with someone in your name.

Not yet compliant, but working on it. There's quite a few ASIL-D components too. We don't use GCC but rather tip-of-the-tree LLVM. Embedded is a completely separate and different mess using whatever the vendor ships for a particular microcontroller.

So far our safety guys haven't seen any issues with tool qualification besides requiring everything to be documented and the whole system to be re-tested in case of any tool changes.

Estonia has personalidentificationcode@eesti.ee and registrycode@eesti.ee, which you are supposed to set up to forward to your actual email aadress. Unfortunately these are restricted for use by governmental agencies for important official notifications (e.g. you're being conscripted, your marital status changed, something has changed in regard to a property you own). [0]

You could create a public alias of the form firstname.lastname.n@eesti.ee, but creation of those was ended in 2018 and they were shutdown in November 2023. [1]

[0] https://www.eesti.ee/en/using-the-state-portal/terms-of-noti... [1] https://www.eesti.ee/en/closing-alias/closing-alias

Is there anything that GCC is missing? Looks complete to me [0]. Everything besides modules is also there for C++20 [1]. I'm at an automotive startup and we've been using a few C++26 features since summer already.

[0] https://en.cppreference.com/w/cpp/compiler_support/17 [0] https://en.cppreference.com/w/cpp/compiler_support/20

Do you have any pointers to such fineprint? I can't find it nor did I notice it when I just very recently began using Backblaze.

The fact that made me switch away from the N edition was the fact that the separately installable media codecs weren't available for weeks after my computer auto-updated to a new major Windows release. This basically made my computer unusable for many regular tasks I did, since as you noted most programs assume they're available.

They're more constrained by advanced packaging (CoWoS) capacity rather than the manufacturing of the silicon.

> Implementations of AV1 in discrete GPUs similarly only landed last year with Nvidia 40 series

NVIDIA has supported AV1 hardware decoding since the 30 series. I believe they were the first to market with it.

RFC 9114 §3.1 ¶2 [0] requires TLS certificates, but I imagine you can easily modify existing implementations to remove this restriction. And even if the spec didn't require it I'd expect all major implementors (web browsers) to still impose this. I imagine something like curl has an opt-out for this (-k?).

Note that the spec essentially says "if verification fails don't trust this connection". What not trusting means is up to the application. For browsers that's probably equivalent to not allowing the connection at all.

[0] https://www.rfc-editor.org/rfc/rfc9114#section-3.1-2

Doesn't seem to much too relevant for image codecs though, no? Decoding 10s of still images on a CPU for a webpage that'll be used for minutes versus 10s of delta images in a much more complicated video coded aren't quite comparable.

I don't think we have much deployment of WebP or AVIF hardware decoders yet the formats have widespread use and adoption.

464XLAT should be the solution for this [0][1]. Requires network and OS support.

[0]: https://datatracker.ietf.org/doc/html/rfc6877

[1]: https://en.wikipedia.org/wiki/IPv6_transition_mechanism#464X...

Would be nice to also include IPv6 variants for each.

Having something like Boost these days is quite far from essential and unless it was in a company's stack already or someone loves it I think you're unlikely to find it in greenfield projects.

> IATA code (3 characters)

What do you do if there's no airport?