Hacker News: nebulous1

New comment by nebulous1 in "I found a vulnerability. they found a lawyer"

nebulous1 — Sat, 21 Feb 2026 16:31:58 +0000

Blackmail to gain what? Speedy update to the site? The OP is going to disclose the vulnerability. The only matter up for debate is the timing.

New comment by nebulous1 in "I found a vulnerability. they found a lawyer"

nebulous1 — Sat, 21 Feb 2026 15:05:29 +0000

I read that entire article thinking it said driving instructor. Doesn't really change anything but it makes so much more sense that he's a part time diving instructor.

New comment by nebulous1 in "Pebble Index 01 – External memory for your brain"

nebulous1 — Wed, 10 Dec 2025 01:50:58 +0000

Their Oura comparison really didn't sit well with me because of that. The device clearly uses a fraction of the power that the Oura is using. If it had a rechargeable battery you would not have to charge it that frequently.

New comment by nebulous1 in "Pebble Index 01 – External memory for your brain"

nebulous1 — Tue, 09 Dec 2025 15:40:10 +0000

That lifespan is based on the user recording for 12 to 15 hours over those two years. It's a $100 device that can record 12 hours of audio and then you throw it away. You could expend the battery on your first day by holding down the button.

Honestly I can see a niche use but this device strikes me as quite weird and I'm not sure why it isn't a button on their new watch.

New comment by nebulous1 in "Molly: An Improved Signal App"

nebulous1 — Sat, 29 Nov 2025 13:20:37 +0000

You'll need to trawl through the actual commits it appears: https://github.com/signalapp/Signal-Android/commits/main/

New comment by nebulous1 in "Ireland is making basic income for artists program permanent"

nebulous1 — Wed, 15 Oct 2025 13:17:01 +0000

How come?

New comment by nebulous1 in "Show HN: Shoggoth Mini – A soft tentacle robot powered by GPT-4o and RL"

nebulous1 — Wed, 16 Jul 2025 01:53:08 +0000

> "ah, you hesitated" no more so than on every single other question.

It was longer. I think almost twice as long. Took about 2 seconds to respond generally, 4 seconds for that one.

New comment by nebulous1 in "Stop killing games and the industry response"

nebulous1 — Sun, 06 Jul 2025 15:12:19 +0000

The issue with most of what you're saying here is that all of that works the way it does because it can, not because it has to. Code libraries, for example, may essentially prohibit what is being requested by SKG because they can. However, if they couldn't then they wouldn't. The companies selling the libraries aren't going to simply shut up shop.

Which is just to say, if there's money to be made then businesses will do so within the regulatory framework.

New comment by nebulous1 in "Experimental release of GrapheneOS for Pixel 9a"

nebulous1 — Sun, 13 Apr 2025 12:50:16 +0000

I agree, but in this banking apps (around me) use the Integrity API anyway.

New comment by nebulous1 in "NixOS and reproducible builds could have detected the xz backdoor"

nebulous1 — Sun, 23 Mar 2025 03:03:35 +0000

> showdead enabled

Thanks, I didn't know this was something we could turn off. Although it does feel like they could just default to collapsed too.

New comment by nebulous1 in "NixOS and reproducible builds could have detected the xz backdoor"

nebulous1 — Sun, 23 Mar 2025 02:44:28 +0000

Right. The title seemed to be suggesting that the Nix way of doing things might have detected the backdoor. It's actually intending to suggest ways that Nix could be changed in order to detect the backdoor.

New comment by nebulous1 in "Two new PebbleOS watches"

nebulous1 — Tue, 18 Mar 2025 17:02:17 +0000

$100 profit on a $150 watch would be crazy. Rest of the post seems made up too. I don't know where these numbers are coming from. I'm genuinely confused.

New comment by nebulous1 in "DiceDB"

nebulous1 — Mon, 17 Mar 2025 21:15:25 +0000

Thanks!

New comment by nebulous1 in "DiceDB"

nebulous1 — Mon, 17 Mar 2025 18:58:18 +0000

So, in the situation in the comment OP, with sychronized writes and and unsynchronized reads, what is this "happens before" stipulation prohibiting?

New comment by nebulous1 in "DiceDB"

nebulous1 — Mon, 17 Mar 2025 18:54:22 +0000

Thanks. So the structure in the OP is an array of uint32s.

> that unsynchronized reads of a uint64 will return some previous valid write, it doesn't guarantee anything about which value is returned

Your the second person saying this, so is my interpretation that this is dissallowed by the part that you quoted incorrect?

> must observe some write w such that r does not happen before w and there is no write w' such that w happens before w' and w' happens before r

edit: somebody is answering this below by the way

New comment by nebulous1 in "DiceDB"

nebulous1 — Mon, 17 Mar 2025 18:38:02 +0000

I don't disagree, but that's not the claim I was replying to. The question I was asking about was

> I understand the need for correct lock-free impls: Given OP's description, simply avoiding read mutexes can't be the way to go about it?

I did note that the documentation recommends a lock.

> read the first value ever set to the variable for the entire lifetime of the program

That is not my reading of the current memory model? It seems to specifically prohibit this behaviour in requirement 3:

> 2. w does not happen before any other write w' (to x) that happens before r.

New comment by nebulous1 in "DiceDB"

nebulous1 — Mon, 17 Mar 2025 13:13:41 +0000

I don't use Go.

https://go.dev/ref/mem

If I'm reading this correctly, they are recommending a lock in this situation. However, they are saying the implementations has two options, either raise an error reporting the race (if the implementation is told to do so), or, because the value being read is not larger than a machine word, reply to the read with a correct value from a previous write. If true then it cannot reply with corrupted data.

New comment by nebulous1 in "DiceDB"

nebulous1 — Sun, 16 Mar 2025 15:30:32 +0000

Would "key-value" not have a place in the description?

This application may be very capable, but I agree with the person saying that its use-case isn't clear on the home page, you have to go deeper into the docs. "Smarter than a database" also seems kind of debatable.

New comment by nebulous1 in "Sidekick: Local-first native macOS LLM app"

nebulous1 — Tue, 11 Mar 2025 18:19:34 +0000

That's the one. Nifty little program.

New comment by nebulous1 in "Sidekick: Local-first native macOS LLM app"

nebulous1 — Tue, 11 Mar 2025 12:49:44 +0000

The name gave me a flashback to Borland Sidekick