🆕 Software Suggestion | SimpleLogin #1832
Labels
No Label
🔍🤖 Search Engines
approved
dependencies
duplicate
feedback wanted
high priority
I2P
iOS
low priority
OS
Self-contained networks
Social media
stale
streaming
todo
Tor
WIP
wontfix
XMPP
[m]
₿ cryptocurrency
ℹ️ help wanted
↔️ file sharing
⚙️ web extensions
✨ enhancement
❌ software removal
💬 discussion
🤖 Android
🐛 bug
💢 conflicting
📝 correction
🆘 critical
📧 email
🔒 file encryption
📁 file storage
🦊 Firefox
💻 hardware
🌐 hosting
🏠 housekeeping
🔐 password managers
🧰 productivity tools
🔎 research required
🌐 Social News Aggregators
🆕 software suggestion
👥 team chat
🔒 VPN
🌐 website issue
🚫 Windows
👁️ browsers
🖊️ digital notebooks
🗄️ DNS
🗨️ instant messaging (im)
🇦🇶 translations
No Milestone
No Assignees
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: privacyguides/privacytools.io#1832
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Basic Information
Name: SimpleLogin
Category: Email alias/forwarding and identity provider (SSO) service
URL: https://simplelogin.io and https://github.com/simple-login
Description
SimpleLogin is an open source, can be self-hosted email alias/forwarding service.
It also offers a privacy-focused alternative to the "Sign in with Facebook|Google|Apple" button.
Why I am making the suggestion
The service allows you to not expose your real email address using email alias.
Email aliases can also be used as "business emails", i.e. email addresses like contact@my-domain.com, sales@my-domain.com, etc
A same request has been opened and closed sometimes ago: https://github.com/privacytoolsIO/privacytools.io/issues/1693
Since then we have implemented necessary measures to satisfy criterias on https://www.privacytools.io/providers/email/
Our hardenize and ssllabs scan results:
For the main domain simplelogin.io
https://www.hardenize.com/report/simplelogin.io/1585823060
https://www.ssllabs.com/ssltest/analyze.html?d=simplelogin.io
For the main email domain (simplelogin.co)
https://www.hardenize.com/report/simplelogin.co/1585845645
https://www.ssllabs.com/ssltest/analyze.html?d=simplelogin.co
My connection with the software
I'm the founder of this service.
It would be great if they added your service, I hope someone can look into this.
Thanks for sharing! I see mentioned on the home page:
@nguyenkims I'm wondering if you're familiar with https://anonaddy.com? -- also open-source, MIT-licensed, and self-hostable (and listed here).
Comparing SimpleLogin's privacy policy (not linked anywhere on the main page?) to AnonAddy's, is it possible for you to provide more specific details regarding
@nitrohorse thanks for your message.
As far as I know, the self-hosting instructions on AnonAddy aren't complete:
More instructions to follow soon...
has been there on https://github.com/anonaddy/anonaddy since quite some times. Please don't take this as a critics towards AnonAddy, it is a great service and has a similar mission to SimpleLogin. As we spent a lot of time making SimpleLogin (relatively) easy to be self-hosted and some people have been running their own SimpleLogin instance successfully since several months, we think we can put that statement on our website.SimpleLogin privacy policy is on the website footer on every page. Its link is https://simplelogin.io/privacy
Almost all questions are answered in our privacy policy and terms and condition page (https://simplelogin.io/terms/)
Ah, you're right, it looks like the instructions on their readme aren't fully there yet. 🤔
Apologies, looks like I have a filter list in uBlock Origin which was removing
###footer
elements from the DOM, yikes. I see the footer now with the links.Also, appreciate you taking the steps to have a solid hardenize report. From my perspective I think I'm comfortable with adding SimpleLogin to our cloaking services section. Interested in more feedback from @privacytoolsIO/editorial
Cross-posting a Reddit thread with some discussion.
By the way, SimpleLogin has also fully answered QtASK, I think they are in another issue.
Regarding the jurisdiction, I don't really think that's an issue since they can't see the messages and the things about metadata will not be that interesting, if your threat model is that high you shouldn't even use e-mail.
please take a look at simple-login/app#117
Totally recommend this. They've also added a new security page that I spotted on twitter:
https://simplelogin.io/security/
Good to see; thanks for the headsup!
I'm against the addition.
The website user interface uses poor quality machine translation.
This may be because of a lack of native speakers. @nguyenkims would it be easy for native speakers to submit PRs with native speech corrections?
@dngray Yes! We'd be happy to accept PRs that correct the texts.
We are indeed not native speakers - apologies for any grammar/expression mistakes on the website!
Where can I send a pull request to improve the translation?
@DirkAmiably3829 our website is on https://github.com/simple-login/website, for example here you can see different pages https://github.com/simple-login/website/tree/master/content
The FAQ section is in this file https://github.com/simple-login/website/blob/master/static/custom.js
The main page is in https://github.com/simple-login/website/blob/master/layouts/index.html
The website uses Hugo https://gohugo.io/ to build, you can refer to the README on how to run it locally.
Thanks in advance!
at this point, i believe that simple login does meet our requirements. @dngray are you aware of any real issues left?
No, I'll work on a PR for this.