"Getting people to value privacy is like trying to get somebody raised on Burger King to value their heath. They won't know how important it is until they have that first stroke."
Possibly the best thing to come out of #lounge:privacytools.io
If you're an Android user, I recommend installing F-Droid so you don't depend on Google Play. https://f-droid.org/
– Where’s your easy-to-use, plug-and-play, ethical alternative to these toxic trillion-dollar products?
– Thanks for asking. We’ve been paying out of pocket for years to work on it. Fancy giving us a few million to speed it up?
– No.
– How about a few thousand so we don’t starve?
– No.
– So, is it ready yet?
Rofl look at this fool
Mastodon, we have a solution? YouTube link: https://www.youtube.com/watch?v=WZjA5d_buNo
After reflecting at 80C; my near future plan is to keep running this indeterminately
Socialmedia is at dire times, I don't want to dump this cosy spot until we've better solutions
I strongly encourage ppl who can, run their own instances & just connect to us
NOT YOUR INSTANCE
NOT YOUR DATA
I will keep signups closed, maybe invite only later
Moderation rules will remain the same w/ the exception of being less understanding w/ ppl being dicks, that includes bitching about BH on Twitter
Zoom security issues: Here's everything that's gone wrong (so far) https://www.tomsguide.com/uk/news/zoom-security-privacy-woes
@karozagorus @karozagorus @btcdragonlord Which is the real dragon?
Huh, how come @[email protected] says "account suspended"?
Would require protocol extensions though, and I have no idea how easy those are to write. @jb55 you were working on your own activitypub implementation - any insights?
But now that this instance might be shutting down sometime in the future, it also made me realize you could have something between the Local and Federated timelines - like the Local timeline but only of instances that are trusted by and trust your instance (there needs to be some reciprocity there, as the other server needs to forward all its interactions to your server, and your server needs to accept that content into the "Trusted" timeline).
Been thinking for a while now (months) about ways to improve #mastodon or more generally #fediverse UX. One key thought I've had is the idea of not only having instance blocklists, but also having instance trustlists. This would allow several UX improvements, such as setting the privacy of your post to the server you are on + the ones it trusts.
Bitcoin Core 0.21.0 was released
It is available from https://bitcoincore.org/bin/bitcoin-core-0.21.0/
Release mail: https://lists.linuxfoundation.org/pipermail/bitcoin-core-dev/2021-January/000097.html
Centralized blocklists (as anything centralized) are inherently susceptible to corruption of its maintainers (in any form, and whether they are aware of it or not). Already fediblock.org doesn't enforce its own rules (receipts of all claims made).
I can see the reason for why it exists. Freedom of association ie. the freedom to filter out bad actors is an important right, and the decentralized approach is hard to scale and hard to bootstrap as a new admin. But this isn't the solution.
Bitcoin nihilist