more domestic production is great

that’s so cool, llms seem like they’ll be more useful in a couple years

they change to symbols when hovering, i don’t think they have a a11y setting for them :/

welcome to the linux side :3

not with trollstore

this is so cool :0

i like how the function section is the only part with FIXMEs, functions are black magic

Blocking known IPFS gateways is cool and all, but what about the legitimate traffic that goes through?

There’s an open tracker at w7tpbzncbcocrqtwwm3nezhnnsw4ozadvi2hmvzdhrqzfxfum7wa.b32.i2p, the announce endpoint is /a

postman still works if you visit and most torrents are on both trackers

blocking the intermediate domain works for me with twitter, it fails the first time and gives up trying to rewrite.

finally, some sanity

Any non-custodial wallet will work tbh. The best wallet would be a desktop one that is solely used for your chosen network and gives you total control over your funds, like Electrum (https://electrum.org) for bitcoin. Ideally it would also let you connect to your own node, although that could be used to trace transaction origins. Your wallet is only as private as you are :3

It sounds overcomplicated, is there really a need for the blockchain aspect? Could the same security be provided by a simpler method (like how keybase has their identity proofs?) but better to have it and not need it than need it and not have it ig

ser the word “they” exists 😂

glad you think so!

theres a few who do, the activity is centered around irc and the forums.

i wonder if we’ll see a move to tor…

yeah, i agree with the OP. decentralized networks have a hump thats hard to smooth out, and activitypub isnt the best protocol in the furst place.

wait, the battery is behind the screen?

1: not very hard actually, the hardest part is gettin the cert onto your other devices x3
all you need to do is add each subdomain to the cert, add ssl_certificate and ssl_certificate_key to the http block, then enable ssl for each subdomain, like so:

http {
    # cert
    ssl_certificate /etc/nginx/public.crt;
    ssl_certificate_key /etc/nginx/private.key;
    server {
        listen       12345:443 ssl;
        server_name  pi.hole;

        location / {
                proxy_pass http://localhost:80;
        }
    }
    server {
        listen       12345:443 ssl;
        server_name  fox.hole;

        location / {
                proxy_pass http://localhost:621;
        }
    }
}

2: correct, all traffic goes through nginx.