what if we just took all the ai data centers and put them to work cracking firmware signing keys instead
@esoteric_programmer @libreleah It’s not the complexity of setting it up that’s the issue, it’s the resource usage.
RocksDB, the database used by conduit and forks (such as continuwuity and grapevine) likes to use up all available memory, so it needs to be restricted by cgroups if you want to run anything else on your system. I initially used used a lower limit (first 1GB, then 1.5GB) and it would after a few days use it all up and become unusably slow (>10 minutes to respond to an HTTP request, at which point nginx would time it out) and had to be restarted. With a 4GB memory limit it runs relatively fine (still much slower than XMPP or IRC but that’s to be expected of a Matrix server), but that’s way more memory than it should need to use.
Compare the resource usage of my conduit server:
● conduit.service - Conduit Matrix homeserver
Loaded: loaded (/etc/systemd/system/conduit.service; enabled; preset: enabled)
Active: active (running) since Thu 2025-08-21 22:51:49 BST; 1 month 28 days ago
Main PID: 638 (matrix-conduit)
Tasks: 12 (limit: 9481)
Memory: 1.6G (high: 4.0G max: 4.5G available: 2.3G)
CPU: 6h 1min 42.506s
with prosody, an XMPP server:
● prosody.service - Prosody XMPP Server
Loaded: loaded (/lib/systemd/system/prosody.service; enabled; preset: enabled)
Active: active (running) since Thu 2025-08-21 22:52:04 BST; 1 month 28 days ago
Docs: https://prosody.im/doc
Process: 3296124 ExecReload=/bin/kill -HUP $MAINPID (code=exited, status=0/SUCCESS)
Main PID: 1590 (lua5.4)
Tasks: 2 (limit: 9481)
Memory: 20.1M
CPU: 1h 3min 32.677s
or unrealircd, an IRC server:
● unrealircd.service - UnrealIRCd
Loaded: loaded (/etc/systemd/system/unrealircd.service; enabled; preset: enabled)
Active: active (running) since Thu 2025-08-21 22:52:05 BST; 1 month 28 days ago
Docs: https://www.unrealircd.org/docs/
Main PID: 1605 (unrealircd)
Tasks: 1 (limit: 9481)
Memory: 28.8M
CPU: 1h 49min 14.019s
Trying to summarise my thoughts on what it takes to build an alternative mobile OS. There's some very important and imho rarely discussed reasons why using anything that depends on AOSP is fundamentally a bad idea.
It basically boils down to culture and politics. The way Android is built and maintained is so fundamentally anti-free-software and anti-community.
1/8
@BluRaf As far as I know, three reasons: