HNHacker News
TopNewBestAskShowJobs

qweqwe14

366 karma · joined July 5, 2023

submissionscomments
qweqwe14··on Mozilla treats Debian devotees to the raw taste of Firefox Nightly
At the most basic level, Linux means "Linux kernel", which you clearly don't have here. You can't run ELF files, you can't create processes, you can't load kernel modules, in fact the only things you can do are those that you directly emulated in JavaScript, which is a very different experience than interacting with a real Linux distro.

Your project has none of the capabilities that are very much expected when someone mentions "Linux", even in a broader sense.

In fact, I'm pretty sure your shell doesn't have some most basic abilities that a POSIX shell has (as another comment mentioned). See the manual page of e.g. dash shell and see what I'm talking about.

Emulating a shell can be fun, but it's clearly not the same as running an operating system. You should probably clarify that in the project README to avoid misinformation. Because otherwise, your project claims to be what it's obviously not.

qweqwe14··on Mozilla treats Debian devotees to the raw taste of Firefox Nightly
Sorry but what I think you've done is just emulating a shell, not an actual Linux system. For that, you need to emulate some architecture that Linux supports, like x86/RISC-V/ARM. With that you should be able to boot a real Linux kernel.

One guy even made a RISC-V emulator inside VRChat using a shader[1]. Doing it in JavaScript will probably be easier, and I wouldn't be surprised if someone has done that already.

Until you emulate a CPU architecture and boot an actual Linux kernel, it isn't quite fair IMO to call it "Linux".

[1] https://blog.pimaker.at/texts/rvc1/

qweqwe14··on Executive Order on Safe, Secure, and Trustworthy Artificial Intelligence
It's free speech until it isn't, the feds went after it because it was used for money laundering. With money laundering issues in particular, this free speech thing gets tossed out of the window.

Tornado's creators should've seen this coming. Thinking that "free speech" would stand in the way of IRS getting mad and shutting it down is delusional.

qweqwe14··on The Grug Brained Developer (2022)
It wouldn't be ad hoc per se, basically you would have a set of guidelines on how to transmit data and that by itself would be a standard.

Something like "use fixed length 8/16/32/64 bit signed/unsigned integers in big endian, length prefix can be 8/16/32 bits, bool is 1 byte (00 = false, 01 = true)" etc, without extra stuff like varints or bit packing, which a lot of current formats are doing.

In short, just use the most straightforward way of encoding while also using the least amount of data. Big endian for ints is very common, simple and relatively compact if you only use the bit width that you need.

qweqwe14··on Can I remove my personal data from GenAI training datasets?
They only get rid of those materials that they can seize. I doubt they will be able to seize a properly hosted onion domain. It's just that most of the actors aren't good enough with technology.

That's the reason you mostly see the pretty dumb guys getting caught. As long as you are smarter and more tech-savvy than 80% of the criminals, you are pretty much out of reach for the feds.

qweqwe14··on Executive Order on Safe, Secure, and Trustworthy Artificial Intelligence
Tornado Cash guys had poor opsec. Pretty obvious that if you are dumb enough the feds will get you.
qweqwe14··on Can I remove my personal data from GenAI training datasets?
I'm not saying that this right is a bad thing, but the reality is that it's rarely enforceable. As soon as you put something on the internet, you have every "right" to expect that it's there forever.

No amount of legislation can outweigh the technical reality.

qweqwe14··on The Grug Brained Developer (2022)
> "Oh, we're slowly building up a custom, buggy, binary framing protocol. Lets just use protobuf/msgpack"

By using protobuf/msgpack you lose the ability to precisely control the layout and encoding of your data on the wire. Most applications don't care, but this results in your wire representation being defined by "whatever protobuf says".

Say I want to transmit an unsigned 16 bit integer with protobuf. How do I do that? The documentation doesn't include 16 bit integers as a datatype, so I'd probably have to wrap it in 32 bits and/or use some varint stuff. It would be simpler to just write a big endian 16 bit int though.

I wish there was a simpler alternative to protobuf that gives more control to end users and doesn't try to be smart. Until then, making your own binary protocol is not over-engineering.

qweqwe14··on Encrypting private data and private communications is now an ethical duty
Privacy for everyone includes privacy for people you don't like. Having literally everyone know about ways to have secure and private communications would actually be a good thing.

Do the bad guys use these technologies? Yes, but so what? It's like saying that we shouldn't educate people about knives because some guy can use it to kill people.

This whole fear of educating people about privacy tools because some criminals will use it is so tired and irrational. Criminals do it already and have done it for a long time. It's inevitable that more people will use them in the future, including the "bad guys". How about we just accelerate it and instead think of why people commit crimes in the first place? Nah, too hard, let's try to ban math instead.

> Fortunately, it seems like most bad actors are idiots who have zero qualms about insecurely broadcasting their thoughts on social media leading up to their committing of despicable acts.

At some point they'll stop doing it and become more aware of their OPSEC. Or they do it intentionally because they want to get caught.

qweqwe14··on Encrypting private data and private communications is now an ethical duty
Lots of comments here mention that the vast majority of people won't use PGP, Linux and other things to protect their privacy, because they don't care/are dumb/have more important things to do/whatever.

The bottom line though is that people that are more tech savvy and more knowledgeable will always have better privacy no matter what, unless you literally enforce Linux and all that on everyone, which is just not gonna work.

And even if it does, you'll then have to ensure they actually use it properly without screwing things up and compromising their privacy, by which point you'd need every person to know a good amount about networks, security, operating systems etc, which is even harder.

The best course of action is making privacy tools easier to use, so that more people can use them. But without some massive change initiated by corporations or governments, it's infeasible that everyone suddenly gains privacy. YOU have to put the work in to protect yourself, not someone else. And most people don't care. And that's fine. Most people suck anyways!

It's easy enough to become aware of privacy issues in the modern world, don't pretend like people don't know about them. If people care about them, they will learn how to solve them for themselves, there's plenty of info. If they don't, there's literally nothing you can do.

qweqwe14··on Invidious – An open source alternative front-end to YouTube
People don't come to YouTube for ads/integrations. When I click on the video, I only want the actual content. Ad segments aren't the only way to monetize anyway.

> Basically you want people creating videos for free?

Noone "wants" anything here. It's just more convenient.

qweqwe14··on Invidious – An open source alternative front-end to YouTube
It is and some projects do it already, it's just that 99% of developers don't have the necessary knowledge to do it properly or don't even care (until they do)

I.e. set up your own git server + web frontend, get a domain name from "DMCA-ignoring" registrar, same with hosting, pay with Monero etc.

...or they know all of this but are reluctant to proceed for some irrational reason, along the lines of "they will get me anyway", "it doesn't matter" and so on

qweqwe14··on FreeTube – The Private YouTube Client
There are, I also forgot to mention general product placement/integrations, sponsorships and stuff like that, although SponsorBlock has put a dent in that (primarily pre-roll type ads)
qweqwe14··on Why Is the Front End Stack So Complicated?
Because using the web as an "app platform" is a hack. Manipulating HTML with JavaScript to achieve app-like functionality is a hack.

JS, along with other things, was bolted on as an afterthought, because HTML had too much momentum for people to stop and consider a proper way to have sandboxed, portable applications, which is what WASM seems to be, after all this time.

And when there's a quirky platform underneath (HTML + JS), people invent a million opinionated ways to achieve the same thing, because there's no single right way to do it. And each comes with it's own quirks.

qweqwe14··on FreeTube – The Private YouTube Client
Regarding ad-blocking: it's pretty simple – no single person in the entire world goes on the internet to view ads. People come to get information/content and just don't really care about other fluff that interferes with that.

As long as it's possible to block ads, people will just do it, because it provides a SUPERIOR browsing experience than otherwise. I sometimes turn uBlock off by accident and instantly get reminded how screwed the browsing experience is without it.

Some people also claim that ad-blocking hurts content creators. This is mostly false. Most content creators have realized by now that relying on ad revenue as a considerable source of income is unsustainable in the long term, due to aformentioned reasons. That's why most have Patreon, Ko-fi, merch shops, donations etc., which is a far more solid business model.

I block all ads everywhere I can, I don't care if they track me or not, if they are "privacy-respecting" or other crap, I simply don't care. And I encourage everyone to do the same.

"I didn't request the ad"

qweqwe14··on Going faster by duplicating code
I was only saying that -O3 enables _even more_ optimizations, which can lead to UB code that works with -O2 but misbehaves on -O3. And because -O3 is seldom used (for reasons other than code breakage), the code patterns that are actually UB but don't get compiled to bad code at -O2 (by e.g. gcc) are lesser known. It all depends on how much a given compiler is willing to make assumptions based on UB and what's permitted by C spec to make optimizations. At -O3 it probably makes a lot more of those assumptions, along the lines of "the spec says this is undefined behavior so I will assume it can never happen and optimize it based on that". The more aggressive inlining in conjunction with that probably exposes more even more UB.

Edit: found example where code works on -O2 but breaks on -O3, related to using abnormal amounts of stack space https://stackoverflow.com/questions/47058978/g-optimization-...

qweqwe14··on Data Processing benchmark featuring Rust, Go, Swift, Zig, Julia etc.
When I see that Zig is slower than Go, I know for a fact that something's off. This benchmark really looks biased.

Rant: As with many benchmarks, this suffers from the fact that there are multiple ways to do the same thing in multiple languages, and the most common one isn't necessarily the best for a particular use case.

In an ideal world, you would have the benchmark in each language written by people that work with that language on daily basis and have all the necessary knowledge to produce a fair benchmark, which is something that a naive implementation often fails to do.

qweqwe14··on Going faster by duplicating code
> Using -O3 was resulting in correctness problems

Likely because your codebase had UB in it that didn't show itself until a certain optimization level. The solution is to fix all instances of UB. See my comment above.

qweqwe14··on Going faster by duplicating code
Because -O3 enables optimizations that break code with some lesser known cases of UB[1]. So people just don't enable -O3 because they can't be bothered to fix UB in their codebase, or because they think it's a "compiler bug".

There are other reasons for not using -O3 which people already mentioned.

As a matter of fact, Gentoo specifically says in their docs that -O3 breaks some packages[2].

[1] https://stackoverflow.com/questions/57889116/different-evalu...

[2] https://wiki.gentoo.org/wiki/GCC_optimization#-O

qweqwe14··on Reversing 'France Identité': The New French Digital ID
Yes, that's pretty much what I meant by "standardized". You'd be able to pick AEAD cipher, KDF, signature algorithm, KEX algorithm etc., while the spec would only describe the protocol itself without enforcing specific algorithms. Noise Protocol pretty much does this already: you provide a string that describes the set of algorithms you will be using, e.g. "Noise_NN_25519_ChaChaPoly_BLAKE2s"
qweqwe14··on Reversing 'France Identité': The New French Digital ID
I've heard about Noise but didn't think to mention it for some reason. Yeah, Noise is basically what I was trying to describe. Such a protocol doesn't necessarily have to use Noise though, however Noise helps avoid some implementation pitfalls that people not very experienced with crypto can make.
qweqwe14··on Reversing 'France Identité': The New French Digital ID
See my comment here: https://news.ycombinator.com/item?id=37790260
qweqwe14··on Reversing 'France Identité': The New French Digital ID
As adev_ mentioned, TLS implicitly requires a lot of things that can be considered expensive for very low power devices (dare I say "bloat"). Examples being things like X509 certificates.

Another thing to consider is that TLS supports multiple use cases and has multiple versions, so it has stuff like algorithm negotiation, version negotiation and some other things that are really unnecessary when you just want a secure channel between two parties with pre-shared keys[1]. If you strip all those extra things from TLS you'll basically end up making your own protocol anyway.

What I'd like to see is a standardized protocol for this exact use case: two parties with pre-shared public keys, no algo negotiation[2], and only sending what's really needed over the wire without extra metadata. TLS is not quite right for this use case IMO.

[1] Yes, TLS-PSK exists but it's largely an afterthought and not always implemented by libraries, because it's considered a niche use case for TLS. To some degree, same thing can be said about client certificates.

[2] I think the article does say that they have algo negotiation in their custom implementation anyway. Personally I'd hardcode something like ChaCha20Poly1305, mainly because it's reasonably fast in software and on low-power devices.

qweqwe14··on How fast are Linux pipes anyway? (2022)
You can probably still make it faster by avoiding libc and using syscalls directly. From looking at the final perf output, it looks like there's some overhead from using libc functions
qweqwe14··on Show HN: Shuttle – Build and ship backends without writing infrastructure files
Yeah, I'd say that if you haven't already planned your application's structure in advance, writing it in Rust would be harder than in e.g. Python. One piece of advice that I can give is to always start with data structures and design stuff around them first. After this it will usually be easier to move forward.
qweqwe14··on Show HN: Shuttle – Build and ship backends without writing infrastructure files
Rust is not a prototyping language. If you need something done quick&dirty, pick e.g. Python. Personally I don't feel like writing something in Rust would take significantly more time than any other language, provided you know Rust pretty well already.
qweqwe14··on LiteFS Cloud: Distributed SQLite with Managed Backups
Not 100% sure if it uses SQLite, but there's an app called "Flaming Durtles" on Android. It's a frontend for WaniKani (Japanese learning app). The app downloads all the lessons from WK's servers, and you can do them even when offline. When you go online, it uploads them to the backend and syncs everything else. In my experience, it works flawlessly.

It's actually a 3rd party app, WK provides an API so that people can make apps that interface with the system.

Forum thread: https://community.wanikani.com/t/android-flaming-durtles-and...

Source code (may be outdated): https://github.com/ejplugge/com.the_tinkering.wk

← PreviousPage 6 of 6