21–30 of 165 posts
Self-ejecting panels on three sides of the website are a horrible user experience. Other than that... The most important thing is not the protocol, it's the gui. At the moment email's gui is horrible on all platforms without exception. If/when a decent gui appears, protocols will follow. Also, JMAP did reading can probably be just WebDAV?
Self-ejecting panels on three sides of the website are a horrible user experience. Other than that... The most important thing is not the protocol, it's the gui. At the moment email's gui is horrible on all platforms without exception. If/when a decent gui appears, protocols will follow. Also, JMAP did reading can probably be just WebDAV?
> First-contact consent: an unknown sender doesn't get into the mailbox; they land in a "requests" box with their first message visible (like Signal's message requests). You accept, and the thread opens forever. A stranger can knock on your door, which is the essential property of mail, but they can't fill up your living room. I like this. Question: can this e-mail specification/implementation also replace direct-mes…
And I do not want an infinite thread conversation. I want to be able to split off - and perhaps archive and export - different conversations by topic.
I recently had to some legal things, which included forwarding copies of a certain conversation to a lawyer. This turns out to be unreasonably difficult because email clients quote previous conversations. You want a clean thread of comment and reply about a specific topic. You don't get that.
You do get it on chat services, but there's no option there to create sub-conversations.
If I was redesigning email I would think long and hard about different use cases and workflows and start with an RFC. Protocols are far downstream of that.
Self-ejecting panels on three sides of the website are a horrible user experience. Other than that... The most important thing is not the protocol, it's the gui. At the moment email's gui is horrible on all platforms without exception. If/when a decent gui appears, protocols will follow. Also, JMAP did reading can probably be just WebDAV?
How can you say that when it's one of the benefits of email that it's an open protocol and there's thousands of different apps built on top of it. Terminal UIs, web interfaces, chat interfaces etc. - that should be one of the cases where there's a GUI for anyone.
Unfortunately, stopped reading at one moment, because though the idea might be interesting, the packaging was unbearable. The obnoxious real time visitors counter seriously screws with my screen reader. I don't care how many people are reading this every 3 seconds updated not only with numbers, but with randomly chosen emois in my speech stream. If you have a website, please, don't subject your visitors to something…
I'm sorry to hear about your bad experience. I've hidden the counter for screen readers. Please try again when you're ready.
> Let's design the successor to email on top of HTTP You can stop there, I've heard enough. Not everything is hypertext.
* DNS lookup for MX record
New version
* DNS lookup for A record
* HTTP request for .wellknown/htmp/known_hosts
Not sure why this is being considered as an improvement?
> each mailbox of a domain on a different provider
Why is this useful/necessary or even 'good'?
Earlier quoted context omitted.
Believe it or don't, most mailservers actually are set up this way, but it's completely invisible to the user: https://en.wikipedia.org/wiki/Greylisting_(email) Greylisting is not perfect, not even close, but it allows servers to reject huge amounts of garbage mail while allowing new mail from unexpected parties without user intervention.
It is similar but not the same thing. It does not have anything to do with the email being legit (non spam) or not. It only catches emails that do not do what they supposed to do when they are deferred for a little bit. They are supposed to try again later. (A super nice feature of email which protects you from losing all incoming emails when your server is down for a short time). The reasoning here is hopefully a sp…
Self-ejecting panels on three sides of the website are a horrible user experience. Other than that... The most important thing is not the protocol, it's the gui. At the moment email's gui is horrible on all platforms without exception. If/when a decent gui appears, protocols will follow. Also, JMAP did reading can probably be just WebDAV?
This is obviously a matter of opinion. Of course there are endless different email GUIs, on all the platforms; if you don't like one, there are many alternatives.
I cannot imagine that a "decent GUI" by modern web-development standards could be anything I'd prefer to what already exists. Email works and generally doesn't let designer ego get in the way.
> Optional postage for strangers: the server can answer a first contact with a 402. Configurable per mailbox; the cost of cold spamming stops being zero. Interesting take re putting a cost on spam. Perhaps another take would be functionally implementing introductions. > First-contact consent: an unknown sender doesn't get into the mailbox; they land in a "requests" box with their first message visible (like Signal's…
Email clients already highlight/filter people in your contacts