lemmeBe

joined 2 years ago
[–] lemmeBe 6 points 1 day ago

Even with all their flaws... EU ❤

[–] lemmeBe 2 points 3 days ago

Then I was obviously checking it a bit before that. Thanks for the update!

[–] lemmeBe 3 points 3 days ago

Well said.

Seems that 2 of those entitled ones are following you on Lemmy. 😄

[–] lemmeBe 2 points 3 days ago

Same impression that I got and therefore decided to skip it.

[–] lemmeBe 12 points 3 days ago* (last edited 3 days ago) (2 children)

Here are my Filen testing notes from a couple of months ago. It's a habit of mine so I don't forget why I discarded some options.

  • It's impossible to upload anything through the Win app. You can only set up sync folders where you need to place files. Through the web app, however, you can upload both folders and files.
  • The desktop app disappears as soon as you switch to another app, and you have to launch it again by clicking on the shortcut.
  • You can't access data in the cloud via a virtual drive or anything similar.
  • In short, it's unusable for my use case.

Edit: Be aware that according to [email protected], the above issues have been rectified in the meantime, so you should give it a go before deciding.

[–] lemmeBe 10 points 6 days ago

Hopefully, I can shed some light because I'm in the process of looking for a new email provider so I've been researching extensively for the past few days.

Firstly, despite their strong marketing about privacy and encryption, ALL the privacy-focused email providers face the same fundamental limitation when it comes to incoming emails from external sources:

  • They can read incoming external emails upon arrival.
  • They process these emails (for spam filtering, etc.) before encryption.
  • Only after this processing do they encrypt the emails for storage.

It's a limitation inherent to the current email infrastructure and affects virtually all email providers as far as I'm aware.

So, marketing claims about "zero-access encryption" often refer to emails at rest (in storage), not during transit or initial processing. For truly private communication, end-to-end encryption (like PGP) needs to be implemented by the sender before the email reaches any server.

That being said, Mailbox provides E2E encryption through standard PGP and S/MIME protocols, allowing users to encrypt both incoming and outgoing emails with their own encryption keys that can be generated or imported into the system. Beyond email encryption, they implement domain security and server-side encryption of all stored data, with the option to create secure aliases that only communicate over encrypted connections.

For Mailbox users communicating with other Mailbox users, there isn't an automatic E2E system in place by default (like Proton has). Doesn't matter to me because very little people I communicate with use Mailbox (it's currently the same situation with Proton for me).

You could register anonymously, use a VPN, and encrypt your messages with PGP and be safe that way. I, however, consider emails inherently unsafe means of communication and use them for registrations and meaningless communication only.

Also, Mailbox has Guard feature that creates a temporary mailbox for recipients without PGP. The recipient receives two emails - one with a link to the temporary mailbox and another with the password. You can also add an additional PIN for extra security that you communicate through another channel.

P. S. Their servers are powered by 100% renewable energy, if that carries any weight.

[–] lemmeBe 1 points 1 week ago

Sure, applies to getting to any level of profitability.

[–] lemmeBe 3 points 1 week ago* (last edited 1 week ago) (2 children)

Independently of the Mozilla team, yes.

However, my understanding is that, if Thunderbird were to become ~~hugely~~ profitable, the Mozilla Foundation would benefit financially, though indirectly.

The organizational structure:

  • Mozilla Foundation = parent organization
  • MZLA Technologies Corporation (which owns Thunderbird) is a wholly owned subsidiary of the Mozilla Foundation
  • Mozilla Corporation (which produces Firefox) is also a subsidiary of the Foundation

When Thunderbird moved to MZLA Technologies Corporation in January 2020, this was specifically done to allow Thunderbird to "collect revenue through partnerships and non-charitable donations".

As a wholly owned subsidiary, any profits generated by MZLA would ultimately flow back to its parent organization, the Mozilla Foundation.

In the end, that revenue would probably go to all the smart investments we've seen the Mozilla Foundation make over the previous years. 🙄

[–] lemmeBe 17 points 1 week ago (1 children)

I use Librewolf. The comment was meant as info for those who think that having uBlock as a base still holds significance in light of Manifest v3.

[–] lemmeBe 2 points 1 week ago

And none of these will stick it to you on multiple fronts if it ever comes down to it.

You want safety, diversify. You want convenience, go all in.

[–] lemmeBe 48 points 1 week ago* (last edited 1 week ago) (10 children)

Has the same limitations as uBlock Origin with Manifest v3 and won't work in Chrome.

[–] lemmeBe 1 points 1 week ago

Yeah, that scenario sounds awfully familiar to me as well. 😅

 

First off, I've been loving vanilla-extract for the past 10 months. 😊

The only thing I really missed was the ability to sort CSS properties. Since there wasn't an ESLint plugin for that, I decided to create my own.

@antebudimir/eslint-plugin-vanilla-extract offers CSS property ordering (alphabetical, concentric, and custom), auto-fix capabilities, and supports multiple Vanilla Extract APIs.

If anyone wants to give it a shot, you can find more details in the readme. Looking forward to hearing your feedback.

 

First off, I've been loving vanilla-extract for the past 10 months. 😊

The only thing I really missed was the ability to sort CSS properties. Since there wasn't an ESLint plugin for that, I decided to create my own.

@antebudimir/eslint-plugin-vanilla-extract offers CSS property ordering (alphabetical, concentric, and custom), auto-fix capabilities, and supports multiple Vanilla Extract APIs.

If anyone wants to give it a shot, you can find more details in the readme. Looking forward to hearing your feedback.

 

First off, I've been loving vanilla-extract for the past 10 months. 😊

The only thing I really missed was the ability to sort CSS properties. Since there wasn't an ESLint plugin for that, I decided to create my own.

@antebudimir/eslint-plugin-vanilla-extract offers CSS property ordering (alphabetical, concentric, and custom), auto-fix capabilities, and supports multiple Vanilla Extract APIs.

If anyone wants to give it a shot, you can find more details in the readme. Looking forward to hearing your feedback.

 

First off, I've been loving vanilla-extract for the past 10 months. 😊

The only thing I really missed was the ability to sort CSS properties. Since there wasn't an ESLint plugin for that, I decided to create my own.

@antebudimir/eslint-plugin-vanilla-extract offers CSS property ordering (alphabetical, concentric, and custom), auto-fix capabilities, and supports multiple Vanilla Extract APIs.

If anyone wants to give it a shot, you can find more details in the readme. Looking forward to hearing your feedback.

 

First off, I've been loving vanilla-extract for the past 10 months. 😊

The only thing I really missed was the ability to sort CSS properties. Since there wasn't an ESLint plugin for that, I decided to create my own.

@antebudimir/eslint-plugin-vanilla-extract offers CSS property ordering (alphabetical, concentric, and custom), auto-fix capabilities, and supports multiple Vanilla Extract APIs.

If anyone wants to give it a shot, you can find more details in the readme. Looking forward to hearing your feedback.

 

First off, I've been loving vanilla-extract for the past 10 months. 😊

The only thing I really missed was the ability to sort CSS properties. Since there wasn't an ESLint plugin for that, I decided to create my own.

@antebudimir/eslint-plugin-vanilla-extract offers CSS property ordering (alphabetical, concentric, and custom), auto-fix capabilities, and supports multiple Vanilla Extract APIs.

If anyone wants to give it a shot, you can find more details in the readme. Looking forward to hearing your feedback.

view more: next ›