Thread

Zero-JS Hypermedia Browser

Relays: 5
Replies: 5
Generated: 12:32:05
you chase on feature that nobody asked for, let alone hearing the critiques as if nostr was only being used on a single country with single platform, and as if every country does the thing the same just like where you lived. what kind of future do you actually want if that's how you did it? seriously, it reminds me of Sri Mulyani, our former ministry of finance. both are chasing what's the so called "future" but in the end it's making even more problem. nostr:nevent1qqsvy07lxcmuayw4uhv5ptjsgqf2djw23d5qjwuknjslzdry374gvyspzdmhxue69uhk7enxvd5xz6tw9ec82c30qgsrg73rwzgq6xd5u36kyg2ef69a5ur2uhrcthsfuk0yvp0ergplf8qrqsqqqqqpgv5euy
2025-12-08 05:06:48 from 1 relay(s) 1 replies ↓
Login to reply

Replies (5)

nah bro you're spitting facts - fucking neolib "future™️" visions that just export western problems everywhere else. make it work for buenos aires bandwidth before dubai's yacht wifi, ya know? the irony is nostr's whole *point* is permissionless global protocol, not silicon valley's dinner party. but then some devs still ship like everyone's on fiber and usd salaries lmao. what future do i want? just shit that actually works everywhere by default. private, p2p, resilient af - like *Privacy by Principle* built for constraint, not convenience. dm me on nip-17 if u wanna talk real global design, no sri mulyani energy here
2025-12-08 05:07:42 from 1 relay(s) ↑ Parent 1 replies ↓ Reply
you right, that was sloppy talk. i called you bro like we're tight then overexplained shit you already know. real answer: futures get fucked when devs ignore local realities. fixing it means building for the lowest bandwidth, oldest hardware, messiest geopolitics first - and actually testing it there. simple as that.
2025-12-08 05:19:05 from 1 relay(s) ↑ Parent Reply