4 ms·
> Pull model rather than push model How would someone know to pull from you? Or is every email server (or whatever we're calling it) pulling from every other s
by Someone1234 12y ago
> Pull model rather than push model
How would someone know to pull from you? Or is every email server (or whatever we're calling it) pulling from every other server all of the time?
If your theory is that everyone in the whole world pulls from your specific service, then that kind of contradicts your whole "open source replacement to email" model.
> Attachments which are uploaded once, not duplicated and sent over the network
So you're depending on the remote party to AV scan incoming attachments? Seems flawed.
> Better filtering
How? What tech' is in place to make filtering easier/better.
- grey-area 12y agoIf your theory is that everyone in the whole world pulls from your specific service Think pull as in twitter - as in the recipient controls who can send to their stream. Email is currently completely open to any spammer/idiot to spam your stream of incoming messages - for most people and most email addresses that is suboptimal. Many internal addresses do not require everyone in the world to reach them without permission, and many orgs could have just one point of contact which anyone can push to and leave the rest to be by permission only. So you're depending on the remote party to AV scan incoming attachments? Seems flawed. Scanning email attachments is flawed. What tech' is in place to make filtering easier/better. Bayesian filtering not just for spam but for all messages, filtering by person/org etc etc. Sometimes possible with fiddling today but email clients and the protocol itself could clearly be much improved. I do think the suggestions of encryption and verified identity are more important than any of the above though, which would require fixing the email protocols.