write code that almost reads like a sentence
You mean COBOL?
The Code is my Bible.
Things I encounter include incomplete documentation, outdated documentation and written process details that have assumed knowledge which makes it difficult for junior Devs to pick up.
Yeah seems about right… off the top of my head:
I’ve been trying syncthing,
It’s what i use but on the phone i only turn it on when i want to sync, otherwise it might drain battery. Always running on the PC.
Mega also works.
two options are responsibly, or anonymously.
Screwing around with big tech i’d go with and, not or.
something end-to-end encrypted.
required SSL certs and I did not have the mood to configure them.
…right…
Did you look into snikket? It’s XMPP-in-a-box.
That’s Wireguard, no?
Should’ve been ‘bunny’.
frustrated debugging log message
Just use porn actresses’ names. Or so a friend told me…
Cryptomator encrypts voulumes you can store/sync anywhere.
In one fell swoop they managed to gobble up quite a lot of FOSS projects, triggering quite a lot of forks…
Oh, that… I think i’m using it but it seems.to expect a response from 80 when all I have there is a redirect to 443.
I thought you meant an nginx plugin.
you can automate the process (e.g. with nginx).
How does nginx automate that?
One of the deep-pocketed founding members of the Rust Foundation says it’s easy. I’m surprised.
Mixing “firmware” with “easy with minimal experience” in the same sentence makes me cringe…
The code is my bible, the grep is my friend.
That and breakpoints.
Some people do complain about it
It’s an Olympic sport nowadays.
since you now often have to implement things at two places at once.
Huh? Header files should only have declarations, unless you’re screwing around with templates.
Of course, you’re right xmpp evolved to get PubSub extension as an “optional feature” but because of its availability (or rather lack) - most servers didn’t support it even the client did support, xmpp didn’t win the acceptance of the end-users. It got some attention in the business world (cisco jabber) but not in the retail.
That XMPP’s extensibility is in itself a strength and a weakness is indeed a valid argument, as you’ve exemplified. I was expecting you’d criticize OMEMO though…
Business cannot work forever without clients willing to pay or at least use, so it died off even in the business.
No, it didn’t die off, it’s still used. IRC is still used as well, probably more or less at the same level. But if you define usage as “used in business” well then probably just a few cases, yes.
I hadn’t heard of Cisco Jabber but i’ve heard of Google and Facebook - both companies’ messengers were, initially, based on XMPP but they EEE’d it once they got enough users and walled their gardens, dealing a major blow to the protocol.
End of story, try not to fighting with the straw men you created.
Can i fight my inner daemons at least? Please?
Not really, just look at any of the Critical Drinker’s takes on the Acolyte.