Replace Gmail

"..and this, ladies and gentlemen, boys and girls, is how you make lots and lots and lots of friends.." 🙃 🤣
..Thinking about it for the duration of my laugh, I realized that this is actually really easy. Just combine the captcha with an iq test. The captcha tests for human, the iq, for the moron. ..the hardest part, actually, will be coding the site so that those who fail.. let's say: "won't have legal grounds for suing you for damage to their self-esteem"..
 
The level of paranoia and innuendo that are used by anti-tech-company luddites continues to amaze me.
..I wouldn't be quite so harsh. Your average joe has no idea how they work, and even switching to using something like bsd as your operating system isn't simple. Conspiracy theories come into existence when there is a lack of real information. The open-source community exists because so few people trust proprietary software. Be completely transparent. Make such a huge effort to explain to people what you are actually doing that it becomes easy to understand. Fund proper educational programs so that children learn these things in school. Do all that, and the paranoia will dissipate. All these things -would- be easy if there was no such thing as competition in society.
 
I ran a web dev company for over 20 years. If you need further information on web standards, please feel free to ask.
but you don't know how to use keygen?

I may be new to FreeBSD but web development is my territory. I'll swing my bats at anyone's 20 years of web development. Get in the ring chump :-) I have 26 years of coding experience. Running a company usually means telling others what to do and swiping the smart phone all day at the desk. Bosses crack me up.

Keygen is obsolete. Nowadays we have Web Cryptography API (supported by major browsers):

you combine this with JavaScript for end-to-end encryption. Don't forget about csrf tokens either.

certain JavaScript (client-side) tools still exist, although crypto.js is deprecated.

just a notice on the serious side of this conversation:
I have tinkered around with introductory cryptography (like switching letters to numbers) and it is a complex subject (trying to outsmart the world). One thing is for sure: leave cryptography to the experts. Never try to roll your own cryptographic-cigars, at least until you reach the same level of cryptographic genius as the mathematical minds that offer leading algorithms.

I've even invented my own language but i am certain that someone could figure it out fast enough to break my sweat :-)

The point is that encryption is difficult. The 1% can and will crack it eventually. The best defense of privacy is to stay offline.

And, by the way, when the government gets involved with an app, then run far away from that (now sponsored) app. C'mon. See the light, or in this case the signal.

I like to mess with the spions: use php to hash gibberish and send it to your pals :-) That should keep them busy for awhile.
 
My 2 cents into this email discussion.

Firstly, I don't know of ANY email service/server (SMTPD) forwarder and receiver that provides anonymity - as of this writing they cannot encrypt your email address :-) But, the servers can communicate using secured and encrypted protocols when configured with SSL/TLS.

Secondly, an email messages can be encrypted, but the encryption only works if a client on each end uses the same encryption/decryption mechanism

Thirdly, There are 3 major security schemes to route email messages:
1) S/MIME: Secure/Multipurpose Internet Mail Extensions based on a set of public and private keys and asynchronous encryption.
2) PGP: since 1990s, Pretty Good Privacy - user creates a pair of public and private keys) before they can send messages, or the secure message provider does that for the user.
3) Bitmessage: users must create a Bitmessage address (a pair of public and private keys) before they can send messages, or the secure message provider does that for the user.

End-to-end encryption improves delivery of your emails and stops spoofing of your communications.

SPF, DKIM, and DMARC are the most widely used techniques. SPF uses the IP addresses to send emails on behalf of a particular domain, allowing recipients to identify the sender. On the other hand, DKIM is a digital certificate that is attached to emails. It enables the recipient of an email to confirm that the content or headers of the email were not altered (faked) during transmission.

So, if you consider hosting you own email server get familiar with the topics as above :-)
Or, just use any free email service if you don't give a damn about IT bullshit and how things work in the totally unsecured TCP/IP world.
 
There are 3 major security schemes to route email messages:
1) S/MIME: Secure/Multipurpose Internet Mail Extensions based on a set of public and private keys and asynchronous encryption.
2) PGP: since 1990s, Pretty Good Privacy - user creates a pair of public and private keys) before they can send messages, or the secure message provider does that for the user.
You have not explained how these methods differ from the user's point of view, what are their advantages and disadvantages compared to each other. In my mind (although I would appreciate your correction), S/MIME is designed to reinforce monopolism, centralise the internet, while PGP is intended to provide direct private communication through personal responsibility, which was the original idea of the internet, and remains as W3C recommendation WoT so far.
Edited: W3C maintains WebAuthn recommendation, sorry for the confusion.
3) Bitmessage: users must create a Bitmessage address (a pair of public and private keys) before they can send messages, or the secure message provider does that for the user.
What is the name of the FreeBSD package for Bitmessage (PyBitmessage)? And how is this Bitmessage better than other F2F protocols and direct communication apps like net-p2p/retroshare?
 
You have not explained how these methods differ from the user's point of view, what are their advantages and disadvantages compared to each other. In my mind (although I would appreciate your correction), S/MIME is designed to reinforce monopolism, centralise the internet, while PGP is intended to provide direct private communication through personal responsibility, which was the original idea of the internet, and remains as W3C recommendation WoT so far.

What is the name of the FreeBSD package for Bitmessage (PyBitmessage)? And how is this Bitmessage better than other F2F protocols and direct communication apps like net-p2p/retroshare?
I'd think that the point of this thread is to explain that if you mis-characterize an issue, and don't understand the technical points of how it works, it's kind of difficult to come up with a solution that actually solves the problem.

If users are not vigilant about details and cannot tell if a message is legitimate or a phish, switching the user to an alternate email service is not gonna solve the problem of user's lack of attention.

This is a bit of a herd mentality thing, unfortunately.
 
Yes, astyle, I agree. However, I have no remorse for unconditionally condemning or ridiculing the youth, the elderly, the women, the sick… I would like to take care of them, too. In my experience, the centralisation of the internet is a precondition for phishing, spam, and other means of fraud and pollution by email. PGP encryption and signing, P2P (or at least an old good UUCP) communication with people you know and trust could avoid most of the risks.
 
Back
Top