Not sure about Microsoft solutions, but modern file systems like zfs and btrfs can do this on the filesystem level, no support from the mail server needed.

NTFS and ReFS has both deduplication support (only on Windows Server).

Am I the only one a bit worried about them using a fixed string as a salt? A salt is intended to make it hard to create a rainbow table. I don't know how much entropy is in their 'folderID' variable, but given that it's a 'short string', it seems low-entropy and not random. If so, the current implementation makes it trivial to make a rainbow table. That means that if you can get the passwordtoken and know a folderID, you can create a rainbow table that maps all possible passwordtokens to valid passwords.

BTW: 'worried' as in 'code smell', not 'worried' as in 'the encryption can be easily broken'.

> The string “syncthing” with the folder ID concatenated make up the salt

Meaning its not fixed but every folder has its own salt

The question is how trivial is it to get the folder id. If it's just an incrementing integer, is it really providing a good salt? Im not actually asking that question or asserting that it isnt, just explaining what you missed.

I think you're right. Reported on Syncthing forum. https://forum.syncthing.net/t/entropy-of-untrusted-device-sc...

>> Is it less safe to share the “Default Folder” as encrypted then? Its folder ID is always just 'default'.

> In the sense that someone could easier pre-brute-force all passwords for that specific folder ID, yes.

That's the definition of a rainbow table, and a fixed, known folder ID makes the "salt" effectively worthless.

the folder ID is a (from memory) 6 character random alnum string.

this is more than adequate for a salt.

That would mean each salt is about 36 bits. If you create 2^18=262k folders in your lifetime using the same algorithm and same password, there's a 50% chance one of the salts is dup'd.

Maybe we can wave this as good enough, but cryptography usually has higher standards.

These don’t refer to individual directories, only top level syncthing folders. Nobody in their lifetime is making even 1000 of these.

No, it doesn't. I know with 100% certainty ESP WiFi hardware is developed in-house and not shared. I think BL602 uses CEVA IP, not sure about that, but it certainly is not shared with ESP chips.

Sprite, how will Espressif react to this effort to open-source wifi? Will it help by releasing wifi phy documentation? Will it add DRM to block future efforts?

(sprite_tm works at Espressif)

Espressif dev here. I usually advise people to break out GPIO0 (or GPIO9 for the ESP32Cx series) because 1. if you somehow write firmware that reconfigures the USB pins, there's no way to get the USB connection going via which you can reset the ESP into download mode, and 2. if somehow a firmware upload aborts halfway, the ESP32 can go into a bootloop with the USB device periodically disappearing. In the 2nd scenario, it's not impossible to time your flash so it goes through, but simply pulling GPIO0 low is easier. I don't think having an actual button is needed, but I'd certainly have a test point or another way you can ground that pin when you get yourself in a pickle.

Oh, we absolutely have on our boards. It's just we've had to use it to recover from a borked flash maybe twice, total? We don't have a button, just have to bridge some pads.

There's a directory at https://dads.cool/directory .

Am I the only one who thinks the 'true fan' definition is a bit... icky? If I have a person who buys everything I offer, regardless of if it's a duplicate of something I already offered earlier, regardless of quality, that person sounds like they put me on way too much of a pedestal. I'd rather have fans that go 'nah, this ain't worth it, I ain't buying' when I send out something that's dog shit. The 'true fan' definition on offer sounds a bit too stalker-y to me.

It can bring with it the anxiety of living up to their expectations. This is present for big celebs too, but in this case the pressure is amplified because you are kind of close to these 1000 or so guys, and they pay you.

Not Freak_NL, but in my experience the only people actually good at recognizing the Dutch accent are Dutch people themselves (unless the accent is really bad). So in practice, it's more of a quirk than something practically bad.

Was wondering how these people make money... looks like you can buy 'enterprise plans' where you can have them solve captchas en-masse... Not sure if I agree with whatever people want to make use of that.

Years and years of cat-and-mouse between people wanting to jump the Great Firewall and people maintaining the Great Firewall.

>The reason that environment no longer runs is because the company decides it's no longer profitable to run it. Blockchains build incentives to run that environment into the operation, so as long as there are users willing to pay, and the environment is efficient enough, in theory the environment should never not be running.

So why would that need blockchain? If this is a viable model to run the game, why wouldn't game companies have a direct 'pay us to keep up the servers online' model now?