(writing this message, I realized how hard it is not to write "product" for the thing graphene and tor make)
1,764 karma · joined December 23, 2021
(writing this message, I realized how hard it is not to write "product" for the thing graphene and tor make)
I suspected he was paranoid, but thanks for the rational explanation!
Currently H2 is clean only at the usage stage, not at the production stage. Just like electricity for EVs in Germany :)
We're all worried about identity fraud, and such documents are actually used to apply for an id in some countries!
In hindsight, making the sync point be paid for all users was a mistake, and an opt-in flag would have been the better option. This is especially true because users that hit the issue kind of mis-used the eBPF map. I've found that most of the map types are good for the userspace -> kernel direction, but most of the times not the other way around.
In the example, sending timing samples to userspace should be performed with a ringbuf map. Alas, those did not exist in 2018, and the perf event array map type had its own drawbacks that pushed people (ab)using array maps. The only times the usual maps are fine for kernel -> userspace is for some non-streaming data (e.g. accumulated packet count in network programs); streaming should be left to ringbuf.
Why not? And I don't mean this in tongue-in-cheek, but as a genuine interrogation: why not go the macOS/systemd route?
DNS is a complex topic. Much more complex than people admit it is, and that can definitely not be expressed fully with resolv.conf. I do agree that it is too late to get rid of it (and was not my concern actually), but it is too limited to be of actual use outside of the simple "I have a single DNS server with a single search domain". IMHO, a dedicated local daemon with its own bespoke config definitely has value, even if it solely provides a local cache for applications that don't have one already (like most of them outside of browsers). And for more complex cases, simple integration with the network configuration daemon provides actual value in e.g. knowing that a specific server is reachable through a specific interface that has a specific search domain. That is, native routing to the correct servers to avoid the timeout dance as soon as you have split networks.
Also, for the local ad-hoc configuration part. We already have nsswitch which is its own can of worms that pretty much nobody have ever heard about let even touched its configuration. Heck, I've written DNS servers but only looked once at nsswitch. resolved's configuration is integrated in the systemd ecosystem, has an approachable and well documented configuration, and is pretty useful in general.
Anyways, the main gripe I had was not really at the mess that is DNS on Linux, but the general stance in the UNIX-like world against anything that's not a lego of shell scripts because "that's not the unix philosophy". Yeah you can write an init system fully with sh, have their "units" also all be written in sh, but oh lord has stuff like systemd improved the situation for the init + service part. Having a raw string from a network packet land in a shell script is a recipe for disaster, seeing how much quoting in scripts is famously difficult.
> The problem with the new, alternative monoliths is they very quickly run off into the weeds with their crazy features and configuration
Agreed for the crazy features. systemd is a godsend for the modern linux world, but I'm skeptical when I see the likes of systemd-home. Yet the configuration is not where I'd pick at those systems though, because they tend to be much more configurable. They are opiniated, yes, but the configuration is an actual configuration and not a patchwork of shell scripts somewhere in /etc, when they're not direct patches to the foundational shell scripts!
> in ways that create barriers for userland applications
How so? In the specific example of resolved, I'd argue it's even less work for applications, because they don't need to query multiple DNS servers at once (it'll handle it for them), don't need to try resolution with and without search domain, etc.
In the end, I find that resolved's approach at symlinking its stub resolv.conf is the most elegant approach with our current setups.
PS: I talk a lot about resolved because that's the one I know best, not the one I think is the best! It has loads of shortcomings too, yet it's still a net improvement to whatever was in place before.
Anyways, this feels like a big issue for "hidden" FreeBSD installs, like pfSense or TrueNAS (if they are still based on it though). Or for servers on hosting providers where they share a LAN with their neighbors in the same rack.
And it's a big win for jailbreaking routers :D
(not that I'm defending it, aside from the more than dubious theme, it's plain illegible)
The formal part resonates, because most non-native english speaker learnt it at school, which teaches you literary english rather than day-to-day english. And this holds for most foreign languages learnt in this context: you write prose, essays, three-part prose with an introduction and a conclusion. I've got the same kind of education in france, though years of working in IT gave me a more "american" english style: straight to the point and short, with a simpler vocabulary for everyday use.
As for whether your writing is ChatGPT: it's definitely not. What those "AI bounty hunters" would miss in such an essay: there is no fluff. Yes, the sentences may use the "three points" classical method, but they don't stick out like a sore thumb - I would not have noticed should the author had not mentioned it. This does not feel like filling. Usually with AI articles, I find myself skipping more than half of each paragraph, due to the information density - just give me the prompt. This article got me reading every single word. Can we call this vibe reading?
Now that you wrote it down, it does actually makes sense.
The downside of IM like Telegram or Matrix or Slack is that it's a broadcast bottle-in-the-sea way of communication. It's everyone's job to answer there, thus it's no one's job to answer there. OTOH contact mail boxes are often direct at people whose job is to read it.
Also, support often are happy to answer general inquiries not related to the product, as long as it's not for outsourcing reasons (not their job to help you set up Apache). They may even get you in touch with someone more technical if needed.
Anyways, feel free to shoot an email yes, username at me dot com.
Folks, when making pixel-art styled stuff, ensure they are actually sharp on bix-pixels screen. It's not pixel-art if it's sharp only on your macbook.
Funny you mention OVH, their direct competitor Scaleway have a public Community slack open to anyone too. Even the engineers directly making the products can be pinged there, so it's great. But re: my comment, AFAIK they receive quite a bit of fake "I lost my account" inquiries.
I've seen the behind the scenes, and in the case of hosting companies, it is self-defense rather than malice. Even some high-stakes SaaS it might be justified too. Though I agree that such restrictions are just user hostile in most cases.
> That literally annoyed me so much even on something like hetzner.
In one word: fraud. I've worked at a company similar to Hetzner, and the "add a credit card first" is the single most effective way to weed out 99% of abusers. People that will each up swaths of compute and mine crypto, ruining the service for everyone. Or hosting CSAM material. Or participating in botnets. Or sending spam. All those makes both the company AND the clients suffer.
You still get the occasional Pakistani bank that allows the emission of unlimited credit cards for fraudsters or the stolen cards (stripe goes a long way for this), but it simply makes the business bearable.
So yeah, we were not thrilled to enforce CC for signup. Believe it or not, even marketing or sales hated it, because it introduces friction in the signup tunnel.
As to re: logged in to open tickets, it is a necessity to avoid customer getting their account stolen. As a customer you receive fake "change your password now!" emails, as a company you receive fake "i've lost my password!" emails. That's the sad way the world is right now. Account theft for hosting providers is a real thing, because the stakes can be very very high.
The only industry that talks in bytes/s is parts of the storage space, because they relate to files, that are measured in bytes/s. And even them use both: the data link is in bits/s (e.g. SATA 6 is 6Gbps, NVMe uses the same bits/s than PCIe (1)) while the drive is usually in bytes/s (µSD cards, NVMe SSDs, etc).
When you look at the industry at large, throughput is virtually always measured in bits/s. HDMI is in bits/s. Video codecs measures bitrates in bits/s. Audio codecs measures bitrates in bits/s. PCIe is in bits/s (1). Ethernet is measured in bits/s. Wifi is measured in bits/s. You get the picture.
The good thing about keeping it consistent is that values are relatable. Streaming services naturally talk in bitrate for the video quality, and your ISP also talks in bits/s. You can compare the two numbers. Bytes/s is only really useful for on the spot jobs that you do once, like transferring photos from an SD card to your computer. Otherwise, it's just a unit.
(1): ackhstually pcie measures speeds in transfers/s because they include the 8b10b/64b66b encoding overhead and TLP overhead but I digress.
Just that I would not really compare the two. The BX500 is the only Crucial SSD I've ever had troubles with and kinda eroded my trust in the brand. My >10 years old M4 is still working like a champ, so does my MX200.
DRAM-less SSDs are a plague that is very hard to avoid, as it's never mentioned in the spec sheets.
basically, the gaming segment is the beta-test ground for the datacenter segment. and you have beta testers eager to pay high prices!
we see the same in CPUs by the way, where the datacenter lineup of both intel and amd lags behind the consumer lineup. gives time to iron out bios, microcode and optimizations.
One of the key points of HBM is that dies are stacked up with many, MANY, more signals and channels. That's how NVIDIA has a memory bandwidth an order of magnitude higher than M4: 550GB/s for the M4 Max, 4.6TB/s for H200. And yes, that's bytes per second, not bits per second.