Oddbean new post about | logout
 My domain is blacklisted again.

We’re talking about error messages in both browsers and anti-virus software to purposely prevent people from visiting my site, and this time they went for RebelNet.me

But today, I change it up, and respond with uploading my past content to Arweave, for an archive.
Arweave is cloud storage directly on the blockchain, it’s like Bitcoin Ordinals, but it scales.
It’s permanent, you can’t undo it.  That’s good because its censorship resistant, but potentially bad if its evidence used against me.  (for example: Samurai wallet’s tweets)

I was on the fence about uploading controversial evasion techniques that I can never undo before, but now again being on the DNS blacklist, I have decided I will never let the knowledge die.

They can scar my name.
They can hunt me down and murder me.
They can pry my encryption keys from my cold dead hands.
But my words will live on.  Now burned directly on the blockchain, and through your memory.

I love you.  And no adversity will ever talk me out of it.

Fire off!

DeGoogled Alternatives:
gTyRNgFo8hUuGRgUsro1e4D1PcEakjBsqkTXmwB8soc

Crypto-Anarchy:
nGsvBWBuiOXaPM6FGtYN-7eRAWjk3WtTqwmzsVuc9lQ

Privacy Checklist:
zT6x-hUmd4WKJ2f9UPXpw2auWvvCLEmzM0KvHiHEfD0

Linux distros:
jZuvwhkTfEMFhvOPhhPUelLUBCvo4Hube0-KNHvfyZ0

And a dozen more.  For the most important part, the Wallet that has it all:
zwYLgYCdECfO4S62oBMJXhvkVFL—24qJCa5E_-BnGM

You can view the wallet’s posts through a gateway or even a block explorer.  For example:
https://pvcsk5frxfyostm75nhyjneotxwpuldjy5ptdip24ut7w6lfgwha.arweave.net/fUUldLG5cOlNn-tPhLSOnez6LGnHXzGh-uUn-3llNY4/profile/zwYLgYCdECfO4S62oBMJXhvkVFL--24qJCa5E_-BnGM 
 .onion 
 Yes we got that too

privacypkybrxebcjicfhgwsb3coatqechwnc5xow4udxwa6jemylmyd.onion 
 how is it blacklisted? I'm able to resolve the domains and access the web servers over IP 
 He mentioned anti-virus blacklists, so if you are not running an anti-virus program that subscribes to those lists, everything will work as expected with no errors or warning. 

That's my guess. 
 yeah, first step in not getting into nonsense with windows shit, is not to run windows 
 That's great man! It depends on your DNS, browser, and OS.   Avast Anti-virus flags it, and these security vendors have it as flagged:

Fortinet
Seclookup
CRDF

We put in requests to them to have it removed. 
 Interesting - coming up on safari for iOS just fine. 
 Good to hear, we submitted appeals to 3 security firms to ask for removal 
 no problems accessing it here 
 haha... i have a project coming up for these guys

it's still only in testnet and i have yet to hear or read a credible model for actually immutable permanent storage without an absurd price due to the clear actuarial risk of it

i think they need to bulid a system that opportunistically cashes and replicates frequently requested data and gradually trims back the replication rate as data gets less attention

the very exact same problem exists with Internet Computer Protocol which is an earlier, and similar sort of blockchain project, and my current project is using IC as an event store (has a basic filter search functionality bulit into it)

i dunno what is in the mind of the guys who build these things exactly, i've done zoom meetings with several of them and honestly they seem spaced out to me

and i get into frequent debates with my colleague over issues of architecture and engineering even though i'm 8 years into actually working in this field and he's fresh out of a B.Sc in CS

don't count on that data sticking around forever

i think a dynamic, automatic archival storage economizing protocol is coming in the future but arweave is not it, not yet 
 Yes I agree.  I think Arweave's true weakness is that the gateways are socialist.  So to store the data you get paid, but there's no motivation to deliver it like you said.  So the bulk of the gateways are cloudflare 
 Cloudflare is a bad idea if you want DNS. Use something else like Quad9 instead. 
 I'm not sure if you meant us or the visitors.  We don't use Cloudflare.  The issue was external third party vendors flagging us.

Fortinet
Seclookup
CRDF

We put in requests to them to have it removed.