No kidding, now I really think of setting up a hook to pack tgz snapshots on each push to git.luxferre.top and offering the recent snapshot downloads somewhere on a new subdomain for those who might end up in the same situation.
OpenBSD folks promise to fix everything by May when 7.5 is fully released, but the real issue is that Git is never gonna be fixed anymore.
Almost 3 hours to build Git and one of its critical dependencies from ports on an ARM64 VPS with #OpenBSD (because the package dependencies are still broken in 7.5-beta).
The dependencies that could be installed from packages pulled the entire XML parser stack and two text-mode Web browsers I don't need there (lynx and w3m).
This is an example of FUBAR at its finest.
I think the practice to distribute source code in .tar.gz (or, even better, .shar.gz) first must return, and for pretty good reasons.
People must not depend on a bloated VCS that takes 3 hours to build.
OK, it took a very long time (over 2.5 hours, I think) but I managed to build and install got+git from ports (also had to install gettext-tools, xmlto and asciidoc from packages first). Thanks for the tip.
BTW, all this shows that Git also became bloated beyond repair.
The xmlto dependency also pulled lynx, and asciidoc pulled w3m. Now I have two text-mode Web browsers I won't use anyway on my aarch64 VPS.
I mean, yes, "Nostr is just a set of overcomplicated glorified mailing lists that only distribute messages signed with a single algorithm and formatted in a limited way between their subscribers" may be too cold of a shower for someone.
Which cryptocurrency requires the least amount of SLOC to implement a fully functional (non-custodial) wallet, including all the required cryptographic primitives, marshalling and network protocol calls?
I agree. My proposals then would be:
- switch to RSA or allow external utilities like GPG generate and verify message signatures;
- relax the transport requirements (websockets => normal TCP sockets, HTTP POST, scp, rsync etc), ideally by storing the notes as (signed) plain text files on the relay;
- allow to substitute JSON with a Recutil-like or MIME-like format that would preserve the plaintext but let us specify some metadata.
Hold on, I think I have seen all this somewhere already... It probably starts with "e" and ends with "mail".
Whatever happened to that famous 3-line RSA implementation in Perl?
I mean, why is modern asymmetric cryptography so damn huge and inaccessible?
Exactly. I also mentioned this in my phlog post (https://hoi.st/posts/2024-02-12-cosa-nostra.txt):
> Another huge problem is implementation bloat. I haven't been able to find a
> single Nostr client in plain C or Nim. The closest to that was Algia written
> in Go. Requiring EC cryptography, JSON *and* websockets to write a minimum
> viable client is just too much. Not to mention that even web-based clients
> are naturally heavy and don't work in non-JS browsers like Links or NetSurf.
> A lot of these clients also integrate "zap" functionality, which is a word
> for giving tips via... Bitcoin Lightning network. And on top of it all, to
> do zaps, they promote custodial (!) wallets which are implemented as browser
> extensions, as well as some extensions to store Nostr private keys... I lost
> count how many security antipatterns were involved in the implementation of
> all this.
From ports? Because I can't install it from packages either.
To put more context, the VM is on arm64.
What a good time to install #OpenBSD -current and break gitwrapper, lol:
https://undeadly.org/cgi?action=article;sid=20240218142251
I won't revert to 7.4 though. Life exists without git.
OK, those VPS providers that do offer OpenBSD and full VNC control over its manual setup are allowed to not have Alpine, I guess.
But in case you need Docker, Alpine would be much easier for both human and silicon brains. Because Docker inside Alpine inside VMD inside OpenBSD inside KVM... Not sure about the performance of all that.
Those who know, don't talk.
Those who talk, don't know.
Snowden is gonna be replaced with Rainden soon, and then with Sunden. But remember that in 10 months, Snowden returns. Always.
Want a decent DNS and maintain your privacy and control what is blocked? Highly recommend https://nextdns.io/ as an easy and good solution. I know that running your own DNS is for everyone, and it’s not going to keep you private since your own has to go out and query in the clear. I think NextDNS is the best compromise you have and you pay not much. 🐶🐾🫡
How is it better than e.g. RadicalDNS?
Reminds me of twtxt (https://github.com/buckket/twtxt), the idea of the format is similar except the date format is less ambiguous in terms of timezones.
(quoting the docs: "Don’t like the official client? Tweet using echo -e "`date -Im`\tHello world!" >> twtxt.txt!")
Just tested this: alias n='echo -e "$(date -Im)\t$*" >> ~/n'
They should learn from POSIX AWK then.
Reminds me of twtxt (https://github.com/buckket/twtxt), the idea of the format is similar except the date format is less ambiguous in terms of timezones.
(quoting the docs: "Don’t like the official client? Tweet using echo -e "`date -Im`\tHello world!" >> twtxt.txt!")
Good they are too north-korean to find out about Monero.