HNHacker News
TopNewBestAskShowJobs

theamk

9,701 karma · joined May 4, 2016

submissionscomments
theamk··on A 386 PC for Your RP2350
Either "already" or "not any time soon", depending on how you count.

Already - because you have VMs and backwards compatibility. As long as you keep using Intel x86_64, your apps would run, no emulation needed. Or you can use the VM.

Not any time soon - because the computers are not speeding up that fast. 10 year old computers are still being used today, and even the latest CPUs are not orders of magnitude faster. So for a full-system emulation, the most well-known ones is x86 VM's on Apple Silicon, and according to reports, full-system mode is still not close to regular PCs.

theamk··on From Git to Fossil (2025)
There is something wrong with this explanation.

In the most common git setups, you never force-push to master - so a coworker can't rewrite history of master branch. Forges have protection rules, but even if your hosting does not, then the "git pull" will throw a ton of errors after history rewrites. So both fossil and git are similar in that regards.

On the other hand, unpushed branches can be rewritten any time in git.. but this applies to fossil as well. If you have not pushed your fossil changes, it's just a file on disk - you can delete it without pushing and no one will ever know you had intermediate version. Or work in "git" and only export to fossil (or svn or cvs or whatever) once things work.

theamk··on From Git to Fossil (2025)
This was CVS/SVN approach, and that's the reason git won so quickly (no, it was not github like some people claimed, I've seen git become popular in my circle before github was a thing)

I am not sure if you used CSV/SVN before - I did. It maintained the history of what was done in a very immutable way. The branches were heavy-weight and were only used for Serious Business, we generally had a person responsible for branching/merging. You only committed stuff which was in great shape and passed all the tests, just like Fossil wants you now.

And there were manual source code copying, so much copying.

- You are writing a feature and got interrupted mid-work to work on something else - copy/tar those files and restore from svn (you could also do a second checkout, but that destroys your cache).

- Want to send incomplete changes to friend? run "diff" and send them the patch by email, or place that patch file on shared disk.

- Your check-in failed, you need to merge in in latest changes from master? better tar up your work in case you break stuff.

- Are you doing new feature and want to see if refactor will improve it? don't forget to make a copy of changed files in case it does not.

None of this is worth committing on master. Who would want to share an incomplete feature which does not build / does not pass unit tests? Or an pre-refactor version of code which does not work?

Turns out using "git" covers all those usecases, and that's why it's the greatest thing. Fun fact: we've started using git in our team using git-svn, without central git server - we had mutable and shareable commits until the last moment, when we pushed it to central svn server.

IMHO, if you only want to record the final path code takes, and you plan to use "cp", "tar" and "patch" for throw-away work, then you might as well use a "releases" directory on FTP with timestamped archives. Why bother with VCS then?

theamk··on From Git to Fossil (2025)
14 "mistakes" in the entire 2025. I am probably making that many per week? Not to mention committing the intentionally broken stuff, with the expectation that I'll come back and amend if I decided it should go to main.
theamk··on From Git to Fossil (2025)
"Fossil purposely makes it difficult for users to delete content."

Those operations are explicitly declared special, not something you do many times per day because you had a typo in your print statement. I guess technically you can do it often, but the tooling does not make it easy at all, and you are going against program's recommended best practices.

theamk··on From Git to Fossil (2025)
What happens if you make a mistake while committing - maybe forget the file, or commit wrong one?

Fossil has no way to fix it, by design, and I find it an absolute showstopper. I do stupid mistakes all the time, and I am so glad that gits lets me fix those.

theamk··on Roon: "I think open source will be banned"
This talks about open source _AI models_, not open source software in general
theamk··on A Design Space Exploration of Async/Await
not sure what this has with my point?

I am not talking about "some language", I am talking about specific row in the table, "Python + Trio", which can be ABC or ACB depending on how exactly you implement the code.

For that matter, "Python + Asyncio" is a buggy code as well - if you actually try to run it, you'll get runtime warnings about tasks being garbage collected. Again, ideomatic code would be ACB as well.

theamk··on A Design Space Exploration of Async/Await
Very similar dimensions also apply to threads, the async/await is not really that different there.
theamk··on A Design Space Exploration of Async/Await
Linux has 8MB thread stacks by default, Windows apparently has 1MB ones, and that space is not going anywhere. As long as people are worried about memory, they will need something lighter than threads. (Yes, golang managed to create dynamic stacks, but this required major support from compiler and so unlikely to appear in existing languages).

Also, I think that single-threaded programs, even with co-routines, are just so much nicer than multi-threaded ones. You write "index = last_index++;" and it Just Works (tm), no need to worry about locks or atomics or other thread access.

theamk··on A Design Space Exploration of Async/Await
Great post, but the quiz is unfair - it assumes there is only one "true way", but a lot of frameworks give you options

For example, Trio has no global "spawn" method, by design. Judging by the results, authors assumed "with trio.open_nursery() as n: n.start_soon(write_to_log())", and so they got eager execution, dynamic extent, destructive propagation.

But opening a nursery just to write a single log line is absolutely crazy! The real program would use an appropriately scoped shared nursery: either per-request or global. Later option allows indefinite extent and "never" propagation.

Also, that "()" after write_to_log matters! If one follow trio's own examples, you'd write "n.start_soon(write_to_log)" - note no (). This will switch to lazy execution.

I am not familiar with non-python frameworks listed, but I would not be surprised if they allow for similarly wide range of behaviors.

theamk··on Proof of Capture: Apple Reference Image, but open source and using steganography
EXIF already includes extensive metadata, including phone model and GPS location. For professional cameras, there is often camera and lens serial numbers too.

This has been the case for many years, and so far social media sites never care - they strip that info instead. Why would this change with one more extra piece of metadata?

theamk··on Proof of Capture: Apple Reference Image, but open source and using steganography
If there is signed metadata too, then it's pretty hard. You will need to match focus distance (it will be very small if photographing picture), GPS location, exposure and other settings. If there is a depth map, you'll need to match it too.
theamk··on Proof of Capture: Apple Reference Image, but open source and using steganography
Yep, that breaks this scheme, making it useless. But it's far from the only thing making it useless, and the github page even explicitly lists those:

- "Small content edits slip under the threshold. [...] A localised edit covering ~15%x20% of the frame [...] passes as authentic" - this is the worst part. 15%x20% is huge, for example enough to change the face of the person or the book/text on the image.

- "Cropping is not survivable, at any amount" - given the purported reason for perceptual hashing is surviving light editing, it's pretty disappointing that one of the most common light editing operation is not supported.

Oh, and the whole "cryptographic chip" angle is absolutely bogus from the security perspective. OK, attacker can't extract the private key from chip. But they can simply connect the chip to a different device and have it sign anything! Given that the attacker in this model is device owner, this is absolutely trivial.

theamk··on Don't let anyone take away your big box of cables
Easy! I put exclusions on my labels

"USB cables, standard"

"USB passive/special, except pigtails and USB->AV"

"AV, including USB-AV cables"

theamk··on The Public Suffix List Is a Disaster
TL/DR: Ethereum nameserver provider applied to be in PSL, and had great trouble getting in, as it had dozens of malicious domains. They had to stop serving malicious domains to get in (the horrors!)

I can kinda see where the both parties come from.

On one side, browsers use PSL to harden security - by sandboxing sites, restricting shared cookies, etc.. a.example.com and b.example.com could share SameSite cookies and browser cache, but once added to PSL, they no longer can. Under that interpretation, it's strictly better to have PSL to be as large as possible, because the bigger the list is, the more secure the web is.

On other side, a lot of security-related tools use PSL to attribute bad behavior. For example if a.example.com is found to contain malware, a lot of services would mark entire "example.com" hierarchy as malicious, including "b.example.com"; but with PSL inclusion, it's only "a.example.com" which is suffering, while "example.com" itself and "b.example.com" having clean reputation.

That second use has an opposite effect - it actually decreases security of the web with each PSL entry. Every malware author would love to be on that list - "a123.malware.xyz" is marked malicious? No problem, switch to "a124.malware.xyz" which (thanks to PSL) is not burned yet. I am sure this is why getting on PSL list is so hard, and am I am sure that it's that isolation was the real motivation for author's effort, not "user security".

That said, I agree with author's 1st point - it would be nice to have official charter and governance structure for something as important as PSL.

But the 2nd point, "All PSL submissions are automatically merged after passing linter tests, without justification or further exposition."? Hell no. PSL should embrace being a security privilege it is, and behave accordingly. For example, if a DNS domain provider routinely serves malware and does not respond to the take-down requests, it should be kicked off the list. That one-off "no malware on subdomains" check should be automated and applied periodically to all PSL entries.

theamk··on Understanding the recent DDoS attack against Read the Docs
That's why GP mentioned "Smart TV".

A random Internet-connected smart plug made by KOCKJAKD and sold on Aliexpress? Almost impossible to catch.

A major brand like LG, with US presence and sold in brick-and-mortar stores? Much more possible. It also makes a much juicier target for lawyers, thus making it much more likely to get sued. And once there is a precedent, other manufactures would be in danger too. Hopefully after losing a whole bunch of money, the manufacturers will start cracking down on those residential proxies.

(Except that discovery is going to be painful. "Use discovery to find out what's on the other end" is easy to write, but in practice it means regular people dealing with bailiffs just because they happen to buy wrong brand of smart TV)

theamk··on I resigned from Anthropic today
Those drones can only stay up for a few hours at most. Then they need refueling and relaunch, with plenty of human-only steps.

Even if you have terminator-style AI uprising, all you need to do to be safe from those drones is to wait a day.

(The automated weapons can probably last longer, but they still need electricity, and there are still a lot of human steps there)

theamk··on Slime moulds and the bitter debate over the nature of intelligence
> more and more scientists have argued

> a philosopher at Adelaide University

Ah, philosophers, not scientists. Important not to mix them up. Philosophy is an intellectual wordplay, and it's dealing with word definitions. Science deal with natural world.

In this case, the "nature of intelligence" is only about word definition - while it sounds like it's very important, it does not actually predict anything.

theamk··on Among European Companies That Use a CDN, Nearly 9 in 10 Use Cloudflare
what? their docs explicitly say nosy of them are not going tobe cloudflare-hosted

> Cloudflare does not offer web hosting for most websites

https://developers.cloudflare.com/fundamentals/manage-domain...

theamk··on Our GitHub Actions bill kept climbing, so we moved CI to one box
AI slop is strong with this one... I saw "per-runner swap" and I was wondering how it's implemented, given that Linux did not support swap partitioning last time I've checked

Turns out it's just a lie. The script creates a swapfile per runner, but then merges them all into one big happy system pool, where every swapfile is shared between every runner.

theamk··on The Oldest Architecture in Computing
This is an ad for "an open-source agent workspace" product

There is some talk about how amazing human brains are, and then OP introduces the product when claims to be brain-inspired, but in reality is just another AI orchestrator with data "stored across markdown files, a local vector database, and a key-value index". Yeah, this has nothing to do with human neurons.

theamk··on Forges Shouldn't Have Opinions About Your Code
The author has 3 problems with codeberg + sourcehut specifically:

1. They are limiting resources - no more unlimited storage, no more free CI runners, adding Anubis to protect server load.

2. They have banned cryptocurrencies and blockchains

3. They are banning AI contributions

I think 1 is perfectly reasonable for every service. Machines cost money, and that money needs to come from somewhere. When one donates to a platform like this, the intention is to support open-source code hosting. Wasting this money on cryptospam and badly-coded AI scrapers is a very bad idea.

For 2, there is a general crypto-apologist logic about how crypto-currency is OK while completely ignoring that most of the crypto-currency projects are just grifts to steal money from people. There are real reputation risks in being associated with that stuff, and I can't really blame anyone for wanting to stay away from it.

Point 3, "block AI contribution", is actually the most important one - as author points, even Linux has AI patches, and it would not be acceptable under the new rules. Making a post just about that part could have generated much more interesting discussions, too bad that points 1 and 2 detract from the message.

(And yes, every service has some opinions, including Github which blocks active malware (when discovered) and copyright violations. It's just they don't touch author's areas of interest, so author does not care)

theamk··on How I make games in Batch Script: Multithreading
That's MS Windows .bat files. Not even Powershell.

I was going to say, "Hey, that's some nice retro dedication", but apparently those games are using VT100 control characters, meaning it's Windows 10 or above. So not so retro, I guess...

theamk··on Ask HN: Why is nobody funding Wikipedia with AI based chat with articles
AI and Wikipedia have completely opposite goals

Wikipedia: "Our goal is accurate knowledge. Anyone can fix mistakes, we have processes to make sure articles are as accurate as possible" (you can argue if they are successful or not, but at least it's their goal)

AI: "YOLO! Here are some answers which may or may not be correct, but they sure do look plausible!"

This will be especially bad in Wikipedia's case - a lot of people will will ask questions about stuff _not_ mentioned in articles, and AI, being AI, will hallucinate a lot of plausibly-sounding, but incorrect facts.

theamk··on Playing Sounds in Python
A very verbose wrapper for simple functionality

On windows, uses winsound or windll.winmm.mciSendStringW

On Linux, execs "aplay"

On MacOS, exec "afplay"

theamk··on Come On, Blink, You Can Be Better
you are an outlier - most Blink users use cloud, most Blink users do not insert SD cards, most Blink users power cameras by batteries. Those users have no use for continuous recording.

Could Blink implement it? they sure could. Would the company benefit from this? I am not sure. On the upside, a very small fraction would be happy. On the downside, this is more code to maintain. Plus, regular users who turn this option without understanding what it does will complain (to support and forums) about battery life.

This is where the open-source firmware can be handy BTW.

theamk··on Hang on to Your Firefox
I think it's the specific pages - some Javascript is much more memory hungry that others.

A few hundred HN or Wikipedia tabs work absolutely fine, I've tested. But there are much heavier sites, and only a few of those can cause the machine to start swapping until OOM, especially when left to work in the background.

(And unlike Chrome, Firefox does not seem to throttle/unload background tabs automatically... or if it does, it does it much less aggressively)

theamk··on Hang on to Your Firefox
This is a very good example what I meant when I said "it's designed for a different person"!

For me, it's pretty clear that a much better idea is not to fix the broken concept, but do what the Chrome does, and show the button on every single page. Then users won't have to report the pages where button is missing, and Firefox devs won't have to keep updating that functionality all the time as the new types of pages appear.

Yes, this means that sometimes reader mode might miss some relevant text, but that's OK, reader mode does this occasionally already. And Firefox is supposed to be for power users, right?

theamk··on Why humanoid robots won't catch up to human workers any time soon
Is it?

Bipedal is the easiest one: very few environments require 2 feet in particular. Sure, ability to cross uneven terrain is needed, but this can be done with 3, 4 or 8 feet. But in a lot of places, including most of the retail and a lot of factories, all one needs is an ability to move on flat surface and cross door thresholds (thanks to ADA, no stair climbing required). And than can work just fine with large wheels, or tracks. On the other hand with something like construction, you probably want many appendages with some sort of climbing attachments?

The "top" part of humanoid is more integrated into the world: our human infrastructure is really built for beings just under 2m high, and a many of actions need at least 2 human-like hands, with at least the same reach as humans (~3/8 body height long, attached at ~7/8 body height). But this is just a minimum - a lot of things would work better with 3 hands, or maybe with dissimilar hands - one "strong", one "fine manipulation" and one "misc"? I certainly wished to have a 3rd hand when building something...

← PreviousPage 3 of 34Next →