dbushell
dbushell on Hacker News
I'm looking forward to the Gamers Nexus exposé
Posted by
dbushell on Sunday February 22, 2026 @03:50AM
from the conesible.de dept.
I realised I wasn't Tailscale's target customer when I reported a 100% reproducible iOS bug/regression over a year ago. It was confirmed, logged, and forgotten.
Jurassic Park III (2001) has a 3D printer that’s central to a plot line. I know they have a long history but I remember thinking that was more sci-fi than the dinosaurs.
Posted by
dbushell on Friday January 23, 2026 @02:01AM
from the dbushell.com dept.
Posted by
dbushell on Tuesday January 20, 2026 @02:35AM
from the paulmakeswebsites.com dept.
Posted by
dbushell on Sunday January 11, 2026 @02:46AM
from the weblog.rogueamoeba.com dept.
Posted by
dbushell on Friday December 05, 2025 @06:25AM
from the github.com dept.
it costs money to send a lot of emails that aren't immediately blocked or sent to the junk folder
yep! I decided to repurpose the pikaday.com domain because it was still seeing a lot of traffic despite the project being unmaintained for years.
those dithering perverts how dare they try to educate us with their fancy graphics!
Posted by
dbushell on Tuesday October 28, 2025 @12:18PM
from the groups.google.com dept.
A big misconception I've seen is the assumption that Nostr relays are federated and share messages between one another. This is not how it works. So if you're building a "Twitter clone" the client app must search multiple relays and post to multiple relays. If clients are not using a relay in common they cannot see one another.
The end result is a bad experience for both user and developer. Using a single relay is centralised and defeats the point. Using multiple relays is slow and cumbersome and requires the user to know/care which relays they are connecting to.
When I played with Nostr a couple years ago the "NIPs" were already a complete mess. Later NIPs supersede earlier NIPs changing how clients are supposed to interpret messages. At least some are flagged as "unrecommended: deprecated" now.
Posted by
dbushell on Monday September 15, 2025 @01:46PM
from the lorenstew.art dept.
> Delete old emails and pictures as data centres require vast amounts of water to cool their systems.
Also the UK government:
> Taken together, the 50 measures will make the UK irresistible to AI firms looking to start, scale, or grow their business. It builds on recent progress in AI that saw £25 billion of new investment in data centres announced since the government took office last July.
https://www.gov.uk/government/news/prime-minister-sets-out-b...
it's concerning these vibe coding tools must be coerced into semantic markup
could that be solved by prefixing every prompt with a reminder?
would have been fun to see how conference wifi handled that :)
The web app makes 176 requests and downloads 130 megabytes.
It's also <div> soup and largely inaccessible.
These and other issues could be fixed fairly quickly with a little care (if anyone cares).
Do developers not see the irony of publishing AI generated code with a LICENSE?
at least this one does:
> Postscriptum: Yes, I did slap an Apache 2 license on it. Is that even valid when there's barely a human in the loop? A fascinating question but not one I'm not eager to figure out myself. It is however certainly something we'll all have to confront sooner or later.
It makes it easier for users to enable permissions, accidentally too, and thus lower security and privacy. Google products are designed to exploit that. Google probably has data showing a large number of users have disabled such permissions globally, with no easy path to trick them into opting back in. That would be the cynical view!
edit: also one can never be too paranoid around Google.
Yes your example is exactly the same and yet I fear you're missing the point entirely.
It’ll run via an ESM import of an NPM dependency, Deno just doesn’t allow commonjs at the top level
Doesn't inspire confidence.
I guess we’ll see soon enough what Deploy will become since that's "imminent".
KV is dead if they've no desire to develop it out of beta and are working on something new. No reason to ever use it for a new project now.
Fresh is being refactored with an alpha in "late Q3 2025 (likely September)". It was a fairly basic framework to being with. The no compilation/build step was the only interesting idea and that's going away.
The runtime is actively developed but I find this statement amusing:
> We’re not chasing feature parity with other runtimes.
The release notes on Node/NPM compatibility would suggest otherwise.
Seems like the CMA are concerned for other advertisers who profit from 3rd-party cookies, no concern for user's privacy. That poor billion dollar industry, how will it cope?
I think that’s still a win for Deno. Even using all but one flag is better than carte blanche. That said I often —allow-all because Im lazy. Containerising stuff helps.
Node’s progress to modern stuff like ES modules has been glacial. Probably the primary reason Bun/Deno have any success. It is speeding up though, seems a fire was lit by competition.