d4
Luxferre
d451865ead7381ba902a27a34a2f8587b3a08b60fe3f10f8fbf33745241ecc8b
Yes, that one. A voice from outside the echo chambers. If you like my projects and ideas you can donate me with Monero (XMR): 86neopbgniu1bQ4EXL7oU6V6nFQE8VGebBpNbUVHWzPuFG1LH2Ca84eHFkqgNnEkC7ERrf4uXV2PXeMGREKXPYrb8qBFjzR

OK, now to the main topic. What I'm about to post probably won't be useful for USonians or anyone else with LTE/5G-only, but for the rest 3/4 of the globe, I hope it might be useful. Essentially, I'm gonna talk about featurephones that are true featurephones, i.e. not Androids in disguise (like KaiOS ones) and are now completely built upon non-smartphone hardware like MediaTek MT62xx or Unisoc (ex-Spreadtrum) SC6531x/SC770x/UMS9117(L). The UMS9117, btw, supports LTE, so chances are something like CAT B40 may work in 'murica too. Anyway, modern true featurephones are based on low-end MediaTeks/Unisocs, their firmware may contain some trojans (although I hadn't caught Nokia, Alcatel or CAT doing this) but also may contain an autonomous IMEI editor among their secret codes. So lemme repost my codelist and see how censorship-resistant this network truly is.

Well, satellite.earth looks dope while not slow in any way (for a bloated modern web client), the only inability being to edit relay list.

And yes, please stop telling me that extensions (which, by design, can read any contents of any opened webpage) are more secure than pasting nsec. I won't buy this crap.

Not with the bandwidth I have with Starlink (which is, btw, registered on a different person in a different country).

I do use them when absolutely necessary though.

Bare naked IP in both cases. Fine on Android (FF Focus, Mulch), problems on Arch (FireDragon, LibreWolf).

CloudFlare must die.

Whenever I access sites "protected" by them with FireDragon/LibreWolf, I have a good chance of being stuck in a neverending loop of "are you human" verification.

Whom are you really protecting?

...as if gawk must not die...

POSIX or nothing

Well, after some time of lurking around, I still don't seem to grasp the concept or Nostr.

If notes and other events aren't automatically propagated across all known relays, how exactly is this "censorship-resistant"?

If I need to run my own relay to make sure not to be censored, how is this different from running a Gopherhole and its web mirror (which I already do) on my own VPS or even an onion service? How can I make sure the relay server I run cannot be traced back to me?

Why Lightning (essentially a crutch on top of BTC) and not e.g. Monero? Why integrate any opinionated cryptocurrency here at all?

Why websockets, of all things? Why build it on top of bloated protocols and tooling? Sure, one can audit the NIPs, but can anyone audit modern browsers or standalone websocket and crypto libraries that they use?

Overall, the goal looks noble, the high-level proto looks simple enough, but the underlying implementation introduces too much unnecessary complexity. A protocol that cannot run on a featurephone with 128K RAM is flawed by design IMO.

OK folks, so what are my options to use Nostr on a purely non-GUI Alpine Linux installation, besides algia?

Because nostui gets compiled for ages and then errors out.

Also, any normal C (or Nim) clients out there?

tomo misikeke / tomo pi moku misikeke