jan Anja(O_ANTE);
My passion is human culture in all its forms. My worldview is based on humanism.
All my toots are shitposts, unless they aren't.
Fandoms:
- Gentoo
- Self-hosting
- BOINC
- Internet freedom
- Communism (Socialism, Marxism)
- Philosophy
- Culture and Religion
All typos are sponsored by Maliit Keyboard.
This post should be broadcasted daily into every software developer's mind until they unionize.
https://www.baldurbjarnason.com/2024/react-electron-llms-labour-arbitrage/
boymoding should become a women's fashion trend
this would be appropriation in a good sense and trans gals wouldn't feel alone anymore
bunnies are so floofy and cute… wanna pet bunnies :bunhd:
@alex @ben @delta I think we're from the same country :blobcatlul:
-
There are dozens of non-public Chatmail relays that are still available.
-
Delta Chat will work with whitelisted email providers while they allow it. (Disable read receipts, don't join large group chats)
There's no point in using the said providers as transit relays because they are extremely unreliable with Delta Chat. They not only treat incoming messages as spam, preventing reading them, but also actively block sending messages.
It will only make sense if both incoming and outcoming messages to a transit relay are batched and obfuscated to reduce "suspicious" activity - but this also kills real-time messaging.
Looking forward distros to help me draw the best way to ship a separate jsonrpc server
What exactly?
@pancake something like this could work:
- Use find_program in meson.build to locate deltachat-jsonrpc on the system (technically, this check would be excessive because a jsonrpc server is only needed at runtime)
- If deltachat-jsonrpc is not found, build it from a meson subproject ("wrap")
