Avatar
Scoundrel
a87b402ac081c8849b9d5bd4e39f2287f25709d3e3f79e784af1e8b38fefbdf1
I don't care what you think of me, only how you came to think it.

I'm still not buying. I don't care how low it gets, I'm a fiat hodler

If the fediverse is like trash, why don't you try drinking out of the toilet? Er, I mean, joining Nostr?

This IS my Reddit alternative.

Well, technically it's my Funnyjunk alternative, but whatever.

UPDATE: according to my research, a minimum security maximum speed digital signature takes on the order of 100,000 clock cycles to complete. Given that a peak human being can compute a 20 digit multiplication in somewhere on the order of 100 seconds, unlocking a computer in this way would take many days.

nostr:nevent1qqsp0yzyxdzrxnh3m65e8xj3agtkyeht2qdnnyt8zqcn25ckzs8y6wgpzpmhxue69uhkummnw3ezumt0d5hsyg9g0dqz4sypezzfh82m6n3e7g587ftsn5lr7708sjh3azeclmaa7ypsgqqqqqqscunxsp

Yes. I've used both Monero and Bitcoin in the past, but there is nothing I buy with them regularly.

Yes, HODL'ing is nonsense. But no, I would never cash out in order to make a shallow buck. I don't care about profit period; that's my point. I care about buying things. The only valid reason to possess a currency is due to the products and services that the currency can purchase. I insist on taking responsibility for determining the value of my own currency. I refuse to let exchange rates and speculation affect my decisions.

Of course, there is nothing I want to buy with Bitcoin, so I don't actually have any cryptocurrency at the moment. It's a bit of a shame, but I'm not going to pretend to be sorry for my choices.

Anyone who says that is wrong. It definitely counts as censorship. It's just not censorship that's occurring on Nostr.

I don't want to get rich at all. I just want to be free. All of the hodl forever Bitcoiners disgust me.

There are plenty of ways to avoid rape. That's just a natural consequence of violating people's rights. It's still immoral to rape someone, but its undeniable that the ability to actually rape someone relies on that person's choices.

First off, let me just say that the biggest issue people will find with Tor is not necessarily some highly theoretical attack, some vulnerability that can be found by crawling through the source code, or even some issue with the implementation of Tor in practice. What I find that turns people away from Tor is that they want something that will make them feel like they are in control and know what they are doing, but won't require them to put in the work to develop and defend their own understanding of Tor. I hear a lot of people talk about how Tor was originally developed by the US government, or give anecdotes where someone with all around poor op-sec got themselves compromised despite using Tor. If you press these people for a more specific and verifiable issue with Tor, you won't get a real response, because their position is not about whether Tor is actually safe.

But if you ask me? Tor is the best. There are probably a couple obscure mix-networks out there that could theoretically beat Tor if they were anywhere near as mature, but I'm skeptical.

VPN's are based on centralized trust. Tor is based on decentralized trust. But I've been working on a theoretical communication model that can achieve anonymity with zero trust at all. Most of my effort has been going into trying to prove that it's impossible, but no luck so far. I'd love to talk about it if you are interested.

Ugh! I'm tired of people looking over my shoulder when I'm typing my password. I've decided to switch to digital signatures instead. What's easier to do in your head, modular exponentiation, or elliptic curve point multiplication?

Yes, probably so that Firefox can force-update whenever another zero-day is discovered. They've done it to me a few times, but I don't mind.

Replying to unknown

Firefox users, add these entries to /etc/hosts stop stop the Mozilla Telemetry correctly

0.0.0.0 accounts.firefox.com

0.0.0.0 activations.mozilla.com

0.0.0.0 activations.mozilla.org

0.0.0.0 activity-stream-icons.services.mozilla.com

#0.0.0.0 addons.mozilla.org

0.0.0.0 analytics.google.com

0.0.0.0 api.accounts.firefox.com

0.0.0.0 api.getpocket.com

0.0.0.0 auth.mozilla.auth0.com

0.0.0.0 auth.services.mozilla.com

0.0.0.0 autoconfig-live.mozillamessaging.com

0.0.0.0 autoconfig.thunderbird.net

0.0.0.0 autopush.prod.mozaws.net

0.0.0.0 balrog-admin.dev.mozaws.net

0.0.0.0 balrog-admin.stage.mozaws.net

0.0.0.0 balrog-aus5.r53-2.services.mozilla.com

0.0.0.0 balrog-aus5.r53-2.services.mozilla.com

0.0.0.0 blocked.cdn.mozilla.net

0.0.0.0 blocklist.addons.mozilla.org

0.0.0.0 blocklists.settings.services.mozilla.com

0.0.0.0 bouncer-bouncer-elb.prod.mozaws.net

0.0.0.0 broker-live.mozillamessaging.com

0.0.0.0 cdnjs.cloudflare.com

0.0.0.0 ciscobinary.openh264.org

0.0.0.0 code.cdn.mozilla.net

0.0.0.0 content-signature-2.cdn.mozilla.net

0.0.0.0 content-signature.cdn.mozilla.net

0.0.0.0 crash-stats.mozilla.com

0.0.0.0 crash-stats.mozilla.org

0.0.0.0 data.mozilla.com

0.0.0.0 de.malware-error.mozilla.com

0.0.0.0 de.phish-error.mozilla.com

0.0.0.0 de.phish-report.mozilla.com

0.0.0.0 detectportal.firefox.com

0.0.0.0 discovery.addons.mozilla.org

0.0.0.0 dnt.mozilla.org

0.0.0.0 download.cdn.mozilla.net

0.0.0.0 download.mozilla.org

0.0.0.0 dxr.mozilla.org

0.0.0.0 en.malware-error.mozilla.com

0.0.0.0 en.phish-error.mozilla.com

0.0.0.0 en.phish-report.mozilla.com

0.0.0.0 en-us.malware-error.mozilla.com

0.0.0.0 en-us.phish-error.mozilla.com

0.0.0.0 en-us.phish-report.mozilla.com

0.0.0.0 f5f7ln7s.gvtl.com

0.0.0.0 fhr.data.mozilla.com

0.0.0.0 firefox.com

0.0.0.0 firefoxflicks.com

0.0.0.0 firefox.settings.services.mozilla.com

0.0.0.0 ftp.mozilla.org

0.0.0.0 getpocket.cdn.mozilla.net

0.0.0.0 getpocket.com

0.0.0.0 google-analytics.com

0.0.0.0 googletagmanager.com

0.0.0.0 googletagservices.com

0.0.0.0 gvtl.com

0.0.0.0 hello.firefox.com

0.0.0.0 herokuapp.com

0.0.0.0 heroku.com

0.0.0.0 img-getpocket.cdn.mozilla.net

0.0.0.0 incoming.telemetry.mozilla.org

0.0.0.0 input.mozilla.org

0.0.0.0 live.mozillamessaging.com

0.0.0.0 live.thunderbird.net

0.0.0.0 location.services.mozilla.com

0.0.0.0 malware-error.mozilla.com

0.0.0.0 mana.mozilla.org

0.0.0.0 mdn.mozillademos.org

0.0.0.0 monitor.firefox.com

0.0.0.0 mozaws.net

0.0.0.0 mozilla.com

0.0.0.0 mozilla.dorando.at

0.0.0.0 mozilla.net

0.0.0.0 mozilla.org

0.0.0.0 mozsocial.cliqz.com

0.0.0.0 nightly.mozilla.org

0.0.0.0 normandy-cloudfront.cdn.mozilla.net

0.0.0.0 oauth.accounts.firefox.com

0.0.0.0 olympia.prod.mozaws.net

0.0.0.0 phish-error.mozilla.com

0.0.0.0 phish-report.mozilla.com

0.0.0.0 planet.mozilla.org

0.0.0.0 profile.accounts.firefox.com

0.0.0.0 push.services.mozilla.com

0.0.0.0 qsurvey.mozilla.com

0.0.0.0 r4---sn-f5f7ln7s.gvtl.com

0.0.0.0 redirector.gvtl.com

0.0.0.0 reps.mozilla.org

0.0.0.0 safebrowsing-cache.google.com

0.0.0.0 safebrowsing.google.com

0.0.0.0 sb-ssl.google.com

0.0.0.0 search.r53-2.services.mozilla.com

0.0.0.0 search.services.mozilla.com

0.0.0.0 self-repair.mozilla.org

0.0.0.0 services.addons.mozilla.org

0.0.0.0 services.mozilla.com

0.0.0.0 setup.services.mozilla.com

0.0.0.0 shavar.services.mozilla.com

0.0.0.0 snippets.cdn.mozilla.net

0.0.0.0 snippets.mozilla.com

0.0.0.0 ssl.google-analytics.com

0.0.0.0 static.mozilla.com

0.0.0.0 support.live.mozillamessaging.com

0.0.0.0 support.mozillamessaging.com

0.0.0.0 symbols.mozilla.org

0.0.0.0 telemetry.mozilla.org

0.0.0.0 testpilot.firefox.com

0.0.0.0 token.services.mozilla.com

0.0.0.0 tracking-protection.cdn.mozilla.net

0.0.0.0 tracking-protection-issues.herokuapp.com

0.0.0.0 tracking.services.mozilla.com

0.0.0.0 versioncheck.addons.mozilla.org

0.0.0.0 versioncheck-bg.addons.mozilla.org

0.0.0.0 videos-cdn.mozilla.net

0.0.0.0 videos.mozilla.org

0.0.0.0 webextensions.settings.services.mozilla.com

0.0.0.0 www.firefox.com

0.0.0.0 www.google-analytics.com

0.0.0.0 www.googletagmanager.com

0.0.0.0 www.googletagservices.com

0.0.0.0 www.heroku.com

0.0.0.0 www.mozilla.com

0.0.0.0 www.mozilla.org

0.0.0.0 updates.push.services.mozilla.com

0.0.0.0 aus5.mozilla.org

0.0.0.0 docs.telemetry.mozilla.org

0.0.0.0 location.services.mozilla.com

0.0.0.0 location.services.mozilla.com

Are Firefox settings not enough to disable telemetry by themselves?

Replying to f499a2ec...

nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqau5ea8kup6utzyfxqjyh233ndzxzde02wqzcqvagawse3yxszztsz9l9qk So he does not know that it is imprudent to smoke near what is highly flammable?

Jillette should keep quiet, like Penn.

What are you talking about?

Replying to Avatar Backstreetgirl

https://www.pixiv.net/en/artworks/125318319

"You're all just a bunch of disgusting lolicons!"

I think we all knew who took down ATF..

#loli #mesugaki #pregnant

(Attention oomfies: don't click past the content warning.)

WAIT

ATF is down?

Damn, I guess it is.

They pissed me off so I already made them takedown my art, but this is still sad.

This truly is an uohhhh moment 😭

I don't hear a lot of people nowdays talking about the problem with deleting sensitive data on solid state drives. Back when we stored computer data on disks, it was relatively easy to delete sensitive data permanently. Just overwrite the data with all 1's and then all 0's like two times and the data becomes unrecoverable even in laboratory conditions.

However, solid state drives are very different than disks. With solid state drives, the physical storage for the bits of information can wear out, meaning that in order to prevent important info from being lost, it must be transferred before the bits break. And if it's sensitive information that is being stored in those bits, then that means that this sensitive information can stick around at the old location, even after it's deleted at the new location.

I hear that a few solid state drives are supposedly manufactured with the ability to delete information permanently, but it's a hardware feature, meaning it's infeasable for the average perdon to actually test. Not to mention how little software there is that can actually take advantage of this feature.

There are obviously destructive ways to remove data from a solid state drive, and those make sense to use in some circumstances, but nobody wants to buy a new solid state drive every time they delete a file.

So then that begs the question. Why don't we hear people talking about this issue? Well, my guess is because we already have something which can give us almost the exact same result as deleting information from a solid state drive, and that is encryption. Deletion removes 100% of peoples' ability to access the data. And encryption removes 99.999...% of peoples' ability to access the data.

All you have to do is encrypt your hard drive, move the data into RAM when you need to use it, decrypt it in RAM, and then encrypt it again when you need to store it back in the solid state drive. The Linux kernel has a feature I use every day that does exactly this. I also read that VeraCrypt does this. Since RAM is overwritten constantly and loses all data when it's unpowered, the result of these tools is that your data is pretty much inaccessible to everyone except you.

In most cases that's good enough. But in some cases that isn't. You don't have to be a security expert to figure out how to get around encryption: go through the person with the password. That's why when trying to catch a cyber criminal, law enforcement will try to catch them while they are unlocking their computer. That's why your prankster roommate will get on your computer while you're off going to the bathroom. And that's why a violent criminal will buy a $5 wrench from the hardware store and beat you with it until you give up the password.

So long as someone has access to your physical hard drive and your password/encryption key, they will still be able to access and decrypt any deleted sensitive data that was unlucky enough to get caught in your solid state drive's wear leveling.

So is that it? Is there nothing that can be done about this? Well, believe it or not, a solution already exists. Just change your password and re-encrypt your entire solid state drive. Any data you deleted previously that may be hanging around in your solid state drive will be encrypted with a password/encryption key that is no longer being used anywhere.

Unfortunately, this strategy has some problems. First of which is that it only works on data that was deleted before you re-encrypted the solid state drive. For those of us that are so inflexible that we go days (or months...) without restarting our computers, asking us to memorize a new password and drop everything else we were doing to re-encrypt our solid state drive is a huge ask! This means that the amount of sensitive data that is sitting un-deleted on our solid state drives is going to be a lot bigger than we might want it to be.

Secondly, re-encrypting a solid state drive is going to wear it out a little, just because of all the bits you've flipped. And if you re-encrypt your drive every time you delete a piece of sensitive data, that is going to add up!

And thirdly, re-encrypting a solid state drive takes a lot of time. In a world where people like to measure their reboot times in seconds, people aren't likely to be very happy waiting out the minutes and hours it might take to re-encrypt their full solid state drive.

So do we have any other options? The short answer is nope. Not right now at least! But the long answer is yes. There is a way that we could continuously remove access to old copies of our sensitive data without having to expend excessive time, money, or effort in order to do so. The solution is to have different encryption keys for different locations in memory, and then to change those keys every time the data is modified. Imagine having a different key for every individual megabyte in memory, and every time you update a megabyte, you replace the key with a new one.

Of course, this still has an issue to address. How can you manage those keys? If you store them all in one big file then you are going to end up having to re-write that file constantly, which drastically increases the chances that the keys themselves end up being captured by the wear leveling process. And if there is a chance the attacker will have access to your old keys, then that gives them a chance to also access old copies of your sensitive data.

Every megabyte can have its own key. And then every gigabyte can also have it's own key in order to encrypt the file where each of its megabyte's keys are stored. And then every terabytecan have a key in order to encrypt the file where each of its gigabyte's keys are stored. Every time you edit a megabyte, you re-encrypt it with a new key and edit the key's value in the gigabyte's key file. Everytime you edit a gigabyte's key file, you re-encrypt it with a new key and edit the key's value in the terabyte's key file. Every time you edit the terabyte's key file, you re-encrypt it with a new key. For some easy bonus points, you can chain together a few extra keys in order to completely eliminate the ability for a full usable chain of keys to get wear-leveled.

With this, you never have to change your password, you never have to wait for terabytes of data to get encrypted, and you don't have to drop your hard drive into a volcano every time you want to delete some sensitive data.