dbushell

Bluesky status is down https://status.bsky.app edit: back up?

or post comments on HN

Dead internet theory.

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.

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!

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.

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.

Yep, definitely "trusted third party". For example:

https://blog.mozilla.org/en/mozilla/mozilla-anonym-raising-t...

Owned by Mozilla, ran by ex-Facebook employees. I'm sure it's entirely coincidentally this W3C draft was written by Mozilla and Facebook employees.

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.

Yes, all of the criticism in my post is entirely invalidated.

No, the Deno runtime gets regular updates. I don’t think you read the article lol.

Would such versions be much slimmer? Most of the binary is the V8 engine. The compatibility layers are largely thin wrappers around APIs.

Anyway, it does strike me as an odd pursuit regardless. Obviously they're seeing compatibility as opening the door for more potential customers. But as a dev, if I wanted Node compat I'd just use Node.

Dahl doesn't strike me as a business or product person. He's a genius when left to tinker. I get the impression Deno is floundering because of business/VC pressure. I see the original promise of Deno being compromised in an effort to increase users/customers. The project is no longer focused on just making a good JS runtime.

The "rug pull" I was referring to is more about the general Deno philosophy. It's gone from being a modern forward-thinking JS runtime, to being just a Node/NPM copycat with its own half-baked packaging system.

In regards to Deno Deploy I agree that scaling down is nicer, but they're extremely hush about it. Using Deploy for anything beyond a hobby project is a business risk.

I hear that often, unfortunately it's just my name and I have too much equity in the domain!

My original view on Deno and JSR was positive and optimistic (it's all there on my blog). I've been using it for years and I still use Deno because it has more convenient/ergonomic APIs than Node.

If Deno halving the Deploy regions twice from 35 to 12, and 12 to 6 doesn't convince you then I don't know what will

The "replacement" is already being penned: https://www.w3.org/TR/privacy-preserving-attribution/

Which is just going to be in additional to 3rd-party cookies. Google's own study concluded removing 3rd-party cookies loses revenue and "privacy-preserving" tracking increases revenue: https://support.google.com/admanager/answer/15189422 So they'll just do both: https://privacysandbox.com/news/privacy-sandbox-next-steps/

This API collates information about people from multiple web origins, which could be a significant risk to their privacy. To manage this risk, the information that is gathered is aggregated using an aggregation service that is trusted by the user-agent to perform aggregation within strict limits. Noise is added to the aggregates produced by this service to provide differential privacy. Websites may select an aggregation service from the list of approved aggregation services provided by the user-agent.

Now that Google have back-tracked on removing 3rd-party cookies[1] I can't help but think any attempts to standardise tracking APIs is only going to add more data to the mix. This seems like yet another source to abuse.

[1] https://privacysandbox.com/news/privacy-sandbox-next-steps/