News for hackers. Stuff that matters.
Re:Sendgrid under siege from hacked accounts by smnplk on Saturday August 29, 2020 @05:43PM (#24319633)
`We need more self hosted email and less centralized control`

We need to start over and build a truly open internet.

Re:Sendgrid under siege from hacked accounts by Reelin on Saturday August 29, 2020 @06:06PM (#24319752)
> We need to start over and build a truly open internet.

I want to agree, but email is actually an example of an open and federated protocol achieving success. It's pretty much everything that could have been hoped for as far as openness and interoperability go at the protocol level. Unfortunately, balkanization still occurs at the social (ie network) level.

Re:Sendgrid under siege from hacked accounts by dredmorbius on Saturday August 29, 2020 @07:07PM (#24320055)
The open email Internet was buried in an avalanche of spam.

Open alone is insufficient.

Re:Sendgrid under siege from hacked accounts by paulryanrogers on Saturday August 29, 2020 @09:12PM (#24320550)
If email were architected to put the cost of storage on senders then I think the spam problem would have been more manageable. Instead it's so closely modeled on physical mail that recipients get overwhelmed quickly.
Re:Sendgrid under siege from hacked accounts by smabie on Saturday August 29, 2020 @09:32PM (#24320631)
Even if email worked like that, I don't think it would solve the spam problem. Spam emails are rarely personalized and the same exact message is sent out to many different addresses.

As such, the spammer would only have to store each unique message and the list of recipients associated with each unique message.

Re:Sendgrid under siege from hacked accounts by dredmorbius on Sunday August 30, 2020 @03:15AM (#24321903)
Even with single copy + list, with a poll-and-request delivery model (sender polls recipient's system, which then requests message on some schedule):

1. Sender canot simply mass-cram messages to recipients, as many spam engines today do. (Qmail for a time was notorious for doing this).

2. There's good chance that any bulk spammer will accrue a negative reputation by the time most recipients bother to request messages. So they won't.

3. Spammer must sustain a stable online presence --- not be knocked offline or blocked by ISP or hosting provider.

4. Spammer has to track successful deliveries vs. messages that are complete.

Upshot: the spammer's workfactor increases.

Re:Sendgrid under siege from hacked accounts by bsder on Saturday August 29, 2020 @11:17PM (#24321095)
Hrm. I wonder if this is an actual use case for blockchain and proof of work.

If you want to send me an email, you have to send me an SMTPCoin. If my user doesn't mark it as spam, I give you the coin back. If my user marks it as spam, I keep the coin.

Re:Sendgrid under siege from hacked accounts by jonas21 on Saturday August 29, 2020 @11:38PM (#24321177)
Preventing email spam was in fact the original use case for proof of work.

https://en.wikipedia.org/wiki/Hashcash

Re:Sendgrid under siege from hacked accounts by _heimdall on Sunday August 30, 2020 @03:36AM (#24321962)
This was the inspirstion for nano's use of proof of work too. They don't use PoW for the chain itself but do require every transaction to include a small proof of work to avoid spamming the network, almost identical to hashcash.