Felz
Joined 9 years ago
Karma
849
Submissions
237
Member since
Mar 4
Working on Purelymail, a cheap no-nonsense web host.
View on Hacker NewsRecent submissions
Comment · 5 years ago
You're not adjusting for inflation, which they are. Still, I have no idea where they're getting their numbers, which seem comically wrong.
> Accounting for inflation, house prices have soared by 118% since 1965, despite the fact that income has only increased by 15%.
They use the median for that, which seems to have actually increased by 60%:
https://web.stanford.edu/class/polisci120a/immigration/Media...
I'm not sure why nobody else seems to have brought this up- it's a serious flaw in the article.
Comment · 5 years ago
It sounds like a more realistic motivation for that would be to reduce the risk of failure- if the primary team flubbed the project, the secondary team would still be an option. (Such a system would also give you an opportunity to judge how effective either team was.)
Awful thing to do to engineers, but you can understand why management would do it and why they wouldn't want to demoralize the secondary team by telling them.
Comment · 5 years ago
Just me- check the about page. (It is registered as a company too.)
Comment · 5 years ago
They are still useful. One of DKIM or SPF is required to send emails on a custom domain. Both are recommended.
Comment · 5 years ago
https://purelymail.com/docs/companyPolicy#bus
Also, I generally don't stop the service for maintenance, unless I need to upgrade the database engine.
Comment · 5 years ago
Yes.
Comment · 5 years ago
Yea, this to an extent. Honestly I thought people wouldn't need more than $50 too, maybe I was wrong there.
Comment · 5 years ago
Rate limits, feedback loops, and we scan outgoing mail through SpamAssassin. In practice we've only had password breaches causing spam, nothing intentional.
Comment · 5 years ago
Long run it'd probably get deprecated, short to medium run it'd be fine: https://purelymail.com/docs/companyPolicy#bus
Comment · 5 years ago
> 1. I don't know if it's the social media kiss of death at work, but I'm getting lots of SSL errors trying to load your site. It's a crap-shoot whether it works or not right now.
Hard to say for sure. None of the servers really went above 15% average CPU and I don't think they maxed out net, and the health checker for HTTPS didn't have any problems. I'll doublecheck.
On the subject of migration, I'll make a note to add a FAQ for that, thanks.
Comment · 5 years ago
Hm, no idea what would've gone wrong in your case. It sounds like something kept closing the websocket used to provide page interactivity or something?
Comment · 5 years ago
For the trial hashwall, the browser just does some heavy computations. I guess I should add a warning there, it's probably does have battery impact if you're using a phone for whatever reason.
I'll make a note on the UI elements. Honestly hadn't thought about the punycode usecase, good catch.
Comment · 5 years ago
That's partly intentional! Hopefully it scares away the users who expect perfection, and they can be better handled by a glossier service.
(Also I'm just genuinely mediocre at design, and kind of personally prefer less frills anyway.)
Comment · 5 years ago
The E2E will help so long as you're sending email to other users of the same service, yeah. For most cases, it's probably not a huge upgrade from stored encrypted; the bulk of damage in email leaks would be from accumulated emails from the past.
The reason I don't recommend using it if you're super paranoid is because it'd be easy to mess up, and it comes with quite significant holes- e.g. subjects aren't E2E in Protonmail. Best to use a protocol designed for E2E from the ground up.
https://protonmail.com/support/knowledge-base/does-protonmai...
Comment · 5 years ago
No, but I will. Thanks for giving me a term to research!