In some of their blog posts, and their roadmap, it seems like Proton Drive will get an SDK and that will be used for the Linux app. How long until we get it? Probably a while.
On the topic of the Authenticator app, I do think it’s geared more for people currently using Big Tech apps for that end, and that’s a good thing. I am slightly disappointed about the tokens in the logs bug, that shouldn’t have slipped. However, it seems like overall a nice addition for the ones that need it.
Agreed. I’m hopeful we’ll see a flatpak package soon, but at least I can install it on Fedora and give it a try.
Ideally, all of their products should launch with packages but at least they haven’t forgotten us entirely.
Reading reviews from the Google Play Store and the Apple App Store there appear to be a couple of issues/bugs with the app.
Seems like it’s not quite ready and polished.
I hate to be “that person”, but I’ve had zero issues on Linux and Graphene.
I saw an issue where a user was perpetually stuck in the bio-metrics screen, which is pretty bad. But we shouldn’t dive straight into a new critical authentication app without a fallback.
My only problems are design oversights: Swipe to delete, and non-encrypted .json backups, which should be easy for them to correct.
Yes, to give them credit. It seems like they’ve mostly sorted out the larger issues.
I agree though definitely don’t dive in and delete your old authenticator app, leave it around for the time being to be extra sure you won’t lose your data.
Remember to keep backups everyone!
Apologies for the late reply. I respectfully disagree. Malice is the intention to cause harm. I am saying that Proton is being disingenuous, which is very different. Proton is pretending they are the first and only open sourced alternative to Google, Microsoft, and Authy, which is not true. The fact that Notesnook also called them out is telling.
THE PRIVACY COMMUNITY LOVES COMPETITION
I beg to differ. It is extremely common for people in the privacy community to seek better alternatives to the FOSS services they are already using. Plus, Proton Auth is practically a clone of Ente, so to pretend like it doesn’t exist is ridiculous. Moreover, as far as I know, Ente was the only authenticator that showed you the current and next token simultaneously, until Proton copied it.
Proton would have been more subtle and effective with their deception if they had included in their comparison FOSS authenticators that are not as good as theirs. Neither Bitwarden nor Aegis show you the next token in advance.
Instead, they compared themselves to Duo, an authenticator I have never heard of, and I’m confident, most people haven’t either. I highly suspect the only reason they added them is because Duo has ads and Proton authenticator looks so much better by comparison. It’s lame.
PROTON RELIES HEAVILY ON THE PRIVACY COMMUNITY
I don’t think Proton’s target audience is necessarily outside the privacy community. Especially when they are launching a new product. I think they are trying to reach people both inside and outside, and they rely heavily on the privacy community to do the marketing for them.
I personally hate it when companies say their primary audience is newbies when they rely heavily on dedicated users to do their marketing. This happens a lot in Hollywood every time a popular intellectual property like a video game or novel is adapted to the screen. Let’s take Game of Thrones as an example.
The writers and studio said that they are primarily targeting people who didn’t read the novels. But the popularity of the show is in great part due to all the book fans creating content about the story that newbies are consuming. A whole economy was built around it.
The final season of Game of Thrones was universally disliked, especially by the book fans. After it ended, James Hibbert, an insider journalist who worked for Entertainment Weekly (owned by Warner Media at the time, i.e., the same parent company that owns HBO), wrote a book about the show. And when he promoted his book he hosted an AMA on r/ASOIAF, the Reddit sub for the Game of Thrones novels, which at that time had less than 500 K followers. He chose to host an AMA on the book sub, instead of the show sub, r/GameOfThrones, which had almost 2 millions followers at the time. That makes no sense.
Why did he do that? His book was about the TV show, not the novels. And although both fan communities (readers and non readers) were upset about the show, there was definitely more anger in the reader community.
My guess is, he did it because the book fan community perhaps takes the story more seriously than show-only fans, and perhaps have more cultural cachet. I also suspect he was afraid of the level of hate he might get in the show sub, which is now more than 2 million strong. IMO, he should have gone to the show sub because that is the topic of his boo, and the show clearly didn’t care about book fans.
All this is to say, Proton knows that they rely heavily on the privacy community to promote their services, and to pretend otherwise is dishonest. Various services like Alias Vault and Mailfence have asked PG to add them to their recommendation list. Also, various privacy companies like Proton have an official presence on PG. That suggests that the privacy community is a huge part of the equation.
I agree 1000%. But there’s no need to be deceptive about it.
First of all, there’s no such thing as Proton photos. There’s only Proton Drive, which is not that special, for which backing up photos is a feature.
Secondly, and more importantly, Ente is in a league of their own.
As far as E2EE cloud back up services are concerned, absolutely no one is doing what they are doing. Not Proton, Not Mega, Not Syn.com, etc…
Ente is the only E2EE service dedicated to photos, and to creating a superior experience for it.
Ente is innovating. No one in the FOSS market is comparable to them. So it makes sense that they are comparing themselves to Google Photos and not Proton.
Aegis does, in fact, have an option to show the next token in advance. Not enabled by default, AFAIK.
I didn’t know that. Thanks for correcting me.