I've been moving more and more away from terminal and IDEs, and I've been exploring how I could move to a flip phone / table + compact keyboard as most of my development time is now possible to be done via just using TTS.

I'd be interested in exploring if something like this could remove the need for a mouse or touching the screen as well.

Some alternatives that are not bound to the meta glasses: Mudra Link (USD 299), Mudra Band for Apple Watch (USD 350), MindRove Armband (USD 800, wow), SiFi Labs SiFi Band (no price), OYMotion gForce Pro+ (USD 1250, ok this side project is starting to look expensive)

---

There are at least three parts that you'd need to solve:

1. AFAIK there is no single globally canonical Firehose. Different relays aggregate different sets of PDSes, and some might decide not to include your PDS if they don't like your content. The Firehose also isn't really the authority here. It transports signed updates from account repositories.

2. In theory you could make up a new kind of DNS record instead of NS, called PDS, PLC, or something. You'd ask your TLD registry to publish something like `PLC ` instead of the NS records for your DNS server.

The value should probably be the account DID (that's the PLC mentioned above), rather than the address of its PDS. The account DID is the stable identity that signs the repository updates. The PDS is just the server currently hosting that account's repository, and its address can change.

3. You then have a bootstrap problem. To get from an account DID to its PDS, you resolve the DID document and look for its `#atproto_pds` service entry. But `did:web` resolution uses HTTPS and therefore DNS. `did:plc` uses the PLC directory, but reaching that directory and then reaching the PDS URL also normally requires DNS.

So the DNS replacement would depend on the old DNS system to discover the server containing its DNS records.

---

Then, as an example, Google's DNS resolver at 8.8.8.8 would subscribe to one or more Firehoses, index DNS records from account repositories, and verify that their updates were signed by the DID named in the registry record.

Querying would then be something like: you look at the top-level record for the domain, see that there is no NS entry, find the PDS or DID entry, and look in your local Firehose-derived database for DNS entries signed by that account.

If the records aren't there, you might resolve the DID, find the current PDS, and fetch the repository directly. But that brings you back to the bootstrap problem.

Maybe the registry record would need to include both the DID and some kind of glue-like PDS address. Or perhaps the new system would need an independent way of resolving DIDs and locating PDSes without using DNS. I'm not sure what that would look like, especially once you include PDS migration and key rotation, but I think this is an additional part the proposal would need to solve.

/shrug

Comments URL: https://news.ycombinator.com/item?id=46995027

Points: 2

# Comments: 0

> Your fight or flight is stuck on ON mode. Total sympathetic nervous system dominance.

> You can’t just snap out of it, you blew your dopaminergic load and are literally burning neurons.

> No parallel processing, your brain cant’t handle it.

> Productivity plummets, meaning evaporates, creativity disappears…

> Direct correlation between IQ and noise tolerance.

> Our GABA system can’t keep up with modern demands for inhibition.

The overall style is also very much to my personal liking.

Unabomber picture with an edited quote was my first issue.

> Now you’re marinating in auditory AIDS 24/7.

> Cognitive goonery.

Whatsapp mentions don’t work (just show the name of the mention to the other users), and polls or albums don’t work.

Messenger disconnects every couple of days at this point.

Pasting links won’t always expand.

Attachments are always hit or miss.

So many small other things. Still love it.

UK's emergency alert system [1] is based on SMS-CB [2] so it's just test based.

1. https://en.wikipedia.org/wiki/UK_Emergency_Alert_System

2. https://en.wikipedia.org/wiki/Cell_Broadcast

Some very first thoughts on the landing page from someone who probably is in the target audience as I’ve used quite a few similar apps so far. (I did not get to actually try the service due to the lack of integration with bank data)

There is little of substance on the landing page. As a user who is interested in using this, I’d want to learn what features the app has, what is different and better than the competitors, and at the very least see what the app looks like.

Video guide of the features would also be very interesting.

You mention it doesn’t integrate with banks. That is unfortunate. Any thoughts or supporting csv imports or an api to allow users to diy?

Good luck and I’ll keep an eye out :)