I was going to post another Tron-related thing I accidentally found but I already predict the reactions like "Told ya, Tron is a shitcoin!" and I don't want to keep explaining why it isn't.
I will share this story in one of my weekly phlog entries though. Maybe in the same post as the one about kisstron. You'll like it.
I have been scratching my head about the WebSockets too. But here we are. And it seems to work fine.
It seems to work fine... on mainstream browser engines and hipster shitcoding platforms like NodeJS. Everyone who wants to live more frugally is left out.
Just did the first transaction on the Tron mainnet using my own CLI wallet written within 2 days: kisstron. 423 SLOC. Public domain. BIP-39 mnemonic and offline transaction support. Wrote it purely for myself but decided to share the knowledge.
Counter-what? A bunch of highly opinionated specs running on top of extremely mainstream bloatware cannot revolutionize anything.
And don't forget that a lot of users here, like flatjaf himself, don't know a shit about which technologies are acceptable and which are gimmicks. They are here because they aren't welcome anywhere else.
Well, it turned out that tronpy doesn't interact with JSON directly, onlly transforms transaction objects into/from a serializable form; you still need to call json.dumps/json.loads to actually serialize/deserialize them.
With JSON, with WebSockets, with Bitcoin fanboyism, with specs on GitHub, with a lot of other things that actually hurt more than help.
Bad taste in programming languages is something that led Nostr to use WebSockets instead of normal TCP sockets in the first place, introducing huge bloatware layers on all sides.
But again, this choice also come from someone who believes there are no other version control systems than Git and no other Git hostings than GitHub...
I like the "censorhip" typo though, it displays the current nature of GitHub best: censorship + hipsters.
On a side note, hosting "censorship-resistant" platform docs on GitHub, the most censorhip-friendly Git hosting out there, is peak stupidity.
My path was: GitHub -> GitLab -> SourceHut -> standalone Git node with stagit on a static Web server.
Still need to migrate some important stuff out of GitLab though.
Ok, so I found out that tronpy does allow to export transactions to JSON, before or after signing. And it also supports importing such JSONs to broadcast elsewhere.
As much as I hate JSON, I think this use case gets a pass from me.
Those who produce rarely have time to write on any social media.
Writing a lot also is a form of consumption. What are they consuming? Others' attention, one of the most precious resources out there.
Given:
1) tronpy library, (relatively) lightweight and straightforward to use.
2) Fast Tron testnets like Nileex.
3) Memo field that can optionally be attached to each transaction.
Question: blockchain-based forum anyone?
Found Hongdian Black Forest Max though. Looks solid, writes well.
They can produce beta quality.
On Hongdian Black Forest Max: got two of them (EF nib), cleaned both, inked one, writes very nicely. The nib assembly is screw-in, not pressed or glued, which is important for my pocket usecases.
#fountainpen
Found out that the tronpy library is installable in a Python 3.11 venv in Alpine chroot in rooted Kindle (the one on MT8110, Bellatrix board), just needed to make sure the following packages were installed on the Alpine side before running pip install tronpy:
python3-dev libtool autoconf automake musl-dev libffi-dev
(note: if you actually decide building tronpy directly on a Bellatrix device in a venv like I did, be ready to wait for about 30 minutes for the build to finish, if you're not using venv, you can also add py3-regex, py3-ctoolz and py3-pycryptodome packages and the process will be quicker)
Why? Well... The situation with usable FOSS TRON wallets for desktop/CLI is close to catastrophic. Really ready to begin writing my own one on top on tronpy, starting tomorrow. Just wanted to be confident that I'm going to be able to run it even on my wifi-enabled e-reader if I really need to.
I have. Actually, my IMEI editor code list is full of it.