145 Followers
76 Following
127 Posts
Privacy and censorship resistance
PGP: 5372 5900 B2E0 45B4 C7F0 BE91 F11D FBDD C863 E2EE
Blog Sitehttps://diverter.hostyourown.tools
Matrix Instancehttps://usethe.tools
Matrix Community Entrancehttps://matrix.to/#/+freedomtech:usethe.tools

The need for censorship resistant digital cash grows by the day.

Satoshi, and those who came before him, paved the way for a technology that could change the course of history. If you stand on their shoulders and contribute to the cause, I salute you.

👊

🔵 New releases: Tor 0.3.5.14, 0.4.4.8, and 0.4.5.7.
These releases fix a pair of denial-of-service issues. We recommend that everybody upgrade to one of the releases (0.3.5.14, 0.4.4.8, or 0.4.5.7) as they become available to you.
Full log: https://blog.torproject.org/node/2009
New releases (with security fixes): Tor 0.3.5.14, 0.4.4.8, and 0.4.5.7 | Tor Blog

We have a new stable release today. If you build Tor from source, you can download the source code for 0.4.5.7 on the download page. Packages should be available within the next several weeks, with a new Tor Browser coming next week. Also today, Tor 0.3.5.14 (changelog) and Tor 0.4.4.8 (changelog) have also been released; you can find them (and source for older Tor releases) at https://dist.torproject.org. These releases fix a pair of denial-of-service issues, described below. One of these issues is authority-only.  The other issue affects all Tor instances, and is most damaging on directory authorities and relays.  We recommend that everybody should upgrade to one of these versions once packages are available. Tor 0.4.5.7 fixes two important denial-of-service bugs in earlier versions of Tor. One of these vulnerabilities (TROVE-2021-001) would allow an attacker who can send directory data to a Tor instance to force that Tor instance to consume huge amounts of CPU. This is easiest to exploit against authorities, since anybody can upload to them, but directory caches could also exploit this vulnerability against relays or clients when they download. The other vulnerability (TROVE-2021-002) only affects directory authorities, and would allow an attacker to remotely crash the authority with an assertion failure. Patches have already been provided to the authority operators, to help ensure network stability. We recommend that everybody upgrade to one of the releases that fixes these issues (0.3.5.14, 0.4.4.8, or 0.4.5.7) as they become available to you. This release also updates our GeoIP data source, and fixes a few smaller bugs in earlier releases. Changes in version 0.4.5.7 - 2021-03-16 Major bugfixes (security, denial of service): Disable the dump_desc() function that we used to dump unparseable information to disk. It was called incorrectly in several places, in a way that could lead to excessive CPU usage. Fixes bug 40286; bugfix on 0.2.2.1-alpha. This bug is also tracked as TROVE-2021- 001 and CVE-2021-28089. Fix a bug in appending detached signatures to a pending consensus document that could be used to crash a directory authority. Fixes bug 40316; bugfix on 0.2.2.6-alpha. Tracked as TROVE-2021-002 and CVE-2021-28090. Minor features (geoip data): We have switched geoip data sources. Previously we shipped IP-to- country mappings from Maxmind's GeoLite2, but in 2019 they changed their licensing terms, so we were unable to update them after that point. We now ship geoip files based on the IPFire Location Database instead. (See https://location.ipfire.org/ for more information). This release updates our geoip files to match the IPFire Location Database as retrieved on 2021/03/12. Closes ticket 40224.  

Becoming Uncle Jim

This is part one of a series discussing ways in which a single motivated individual can provide tools to those around them in defense of privacy and security. Personal responsibility does not scale; but Uncle Jim can show the way.

There is no good reason for apps to collect and sell location data, especially when users have no way of knowing how that data will be used.
https://www.eff.org/deeplinks/2021/03/apple-and-google-kicked-two-location-data-brokers-out-their-app-stores-good-now
App Stores Have Kicked Out Some Location Data Brokers. Good, Now Kick Them All Out.

Last fall, reports revealed the location data broker X-Mode’s ties to several U.S. defense contractors. Shortly after, both Apple and Google banned the X-Mode SDK from their app stores, essentially shutting off X-Mode’s pipeline of location data. In February, Google kicked another location data...

Electronic Frontier Foundation

Encrypt it.
FOSS it.
Host it.
And most importantly, don't Google it.

http://bitcoiner.guide/swaps.pdf

http://bitcoiner.guide/calyxos

https://youtu.be/oO0UFZjuotg

RT @miguelM_9_
WARNING: you're being conditioned to see your freedom as selfish.

RT @getongab
I’ll go 100% bitcoin if I have to.

You won’t stop us. https://twitter.com/getongab/status/1370383776740560896

Gab.com on Twitter

“Gab was just banned from our 5th bank in 5 weeks. This is Operation Chokepoint under the Biden administration. We literally can't have a basic business checking account to store our money. https://t.co/oBr69xeB2u”

Twitter

RT @Ragnarly
Bitcoin's subversive potential only occurs in smallish, circular Bitcoin economies whose participants avoid KYC & 3rd party services, practice privacy best practices and are idealogically driven.

The best examples are darknet markets and agorist groups.

RT @evoskuil
Cryptoeconomics was first printed for #CryptoEcon2020 in Hanoi, one year ago today. In honor of this unlikely event, I've made the 2nd edition available as a free PDF.
https://voskuil.org/cryptoeconomics
Cryoptoeconomics

Fundamental Principles of Bitcoin

RT @TiKawamoto
Overall bitcoin twitter is very bad at discerning profound from platitudes