>>2562
>no progress on moving from the EOL'd python 2 so far as I know.
This is true and Surda says python3 dev is paused currently, because:
>I'm looking for new developers that can move it forward faster.
It's not ideal, but I don't know of a better option. Dchan for instance, requires payment in persistent-ledger crypto that allows for in-principle traceable transactions/posts. They also probably won't tolerate a /pol/-like board. Fchan is another option, but unless you host your own public instance, you can be censored on any federated instance. IMO running bitchan locally over tor is the best option for paranoid anons who want to securely post about politically sensitive issues.
>The NSA doesn't care about skiddies ripping off small businesses, but they might care about internet nazis when the new domestic war on white terror begins in earnest.
True, but I think BitChan -> Tor -> VPN is a fine way of making this difficult for them, though of course you still shouldn't trust it, but BitChan does have additional methods for protecting communications:
- if run locally (in the next release) users can send PGP encrypted messages and decrypt messages all automated in-thread
- if run locally and if users all know a unique password, comms can happen in a parallel steganography thread
- if run locally and if users know a unique password, each thread can be protected from others' view so that parallel threads can exist without anyone else knowing.
>Relying on a centralized instance that you have no control over or knowledge about is a bad idea.
Absolutely true and like I said, if you want any guidance on making your own instance, just ask. I can share my PGP public key and talk with you that way on bitchan/pol/ if you want.