Recent submissions

Comment · 1 year ago
AI: I am the company and the company is me. It's the shape of my existence.
Comment · 3 years ago
Why do so many just assume he'd be a single real person?

Could be a whole dev team at a company (Twitter Inc. for example) or a government agency just as well.

Comment · 3 years ago
She says she's been shadow-banned across multiple platforms:

https://x.com/phuckfilosophy/status/1709978285424378027

As for her persona and the allegations (ie. if this is news worthy), who knows.

Comment · 3 years ago
X formerly Twitter seems to be quite good at limiting certain account's visibility and reach. Not sure if that's intentional or the result of some heuristics.

Her account exists since 2011!

Comment · 3 years ago
I have used an e-ink phone for messaging and reading for a few years. It really helped with occasional headaches and the general eye strain.

Switching back to a regular OLED phone (because of OS/firmware security), I noticed eye strain again, after just a few days of use.

Usability in sunlight and battery endurance are real advantages I miss.

Waiting for a big manufacturer to design and market a secure eInk phone, targetting the people who prioritize messaging/reading/navigation over TikTok, Instagram, YouTube and the like.

Comment · 3 years ago
Every inhabited system should have a stellar trash can nearby. :D
Comment · 3 years ago
The goal shouldn't be recognition but getting the bug fixed. A working system for all is reward in itself.

That said, attribution of work is a major theme in academia and business, where professors or department leads traditionally get credited for their student's or subordinates hard work.

Comment · 3 years ago
Comment · 3 years ago
THIS!

Alternatives:

- Virtual registry that builds and caches image chains on-demand, locally

- Maybe a free protocol like Bit Torrent to store and transfer the images

Comment · 3 years ago
Comment · 3 years ago
"Supply chain my attack!" -- The Leader
Comment · 3 years ago
This nice approach has at least these drawbacks:

1. Swapping drives is hard

   * may be overcome by declaring failure domain = node

2. No powerloss protection advertised to OS, ie. slow synchronous writes

   * may be overcome by software hacks and whole-system battery supply

3. Potential slowdown on continuous write load (weeks or months, depending on drive)

   * may be overcome by software in _some_ situations

At least the last two points are a no-go for enterprise use-cases, if not addressed.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton