Just Use Email – How to Use Email for Everything
231–240 of 310 posts
Re: Just Use Email – How to Use Email for Everything
#232Earlier quoted context omitted.
As SPF, DKIM and DMARC have become more widely implemented, is IP reputation less of a factor than it used to be in spam detection algorithms? This is just my speculation, but it seems plausible.
Why would it be less of a factor? These things don't prevent spam. I can create a proper mail server with all these and send billion messages from it wherever I like. These technologies prevent various kinds of forgeries. Quick look at my archive, of 37k spams only 7k fails SPF. (I accept all email no matter what.) So it's some signal, but not nearly enough.
Look for DKIM. Either it's signed and pass. Or spam if DKIM is missing. You can filter a lot more this way.
Re: Just Use Email – How to Use Email for Everything
#233I'm on the exact opposite end of the spectrum. I haven't used email outside of work for many years now, and don't miss it one bit. And even at work most communication now happens on Slack. The digital world has evolved since 1997, and email simply hasn't kept up. I skimmed a couple articles on the blog and my biggest problem with it is that the author is making a social rather than technological argument (which are a…
It has nothing to do with hating or not, it just depends on the number of friends and the intensity of incoming communication - not all people are the same. After you cross certain threshold synchronous communication becomes unmanageable and basically prevents you from doing your daily activities as you'd want.
Re: Just Use Email – How to Use Email for Everything
#234Earlier quoted context omitted.
If you want clean IPs for self-hosting a mail server, you can use a service we created called Hoppy Network: https://hoppy.network Our IP addresses are not on any blacklists, and we don't block SMTP or mail ports.
I also just found out about a service called Tailscale (maybe 30 mins ago). It's not a field I have investigated but both your services and theirs sounded vaguely useful for some problems I'm having. Are they somewhat similar? It sounds like I could solve the same problems in perhaps two different ways.
Tailscale (which we have been using to great effect over the last year or so) provides effectively a 'LAN' where the devices can be anywhere. It provides you with a second interface in the 100.x.x.x range. You can trust that any traffic from that range has been authenticated to connect to your Tailscale network.
Hoppy (as I understand it, I've never used it) is more solving the issue of getting a static IP assigned, with the advantage of it following your device if it moves between networks. You get a second interface that is publicly visible, but can't trust traffic coming in from it.
Re: Just Use Email – How to Use Email for Everything
#235Earlier quoted context omitted.
> Worst of all, Gmail especially isn't great about tagging messages as spam My experience is the exact opposite of yours - I find Gmail's spam detection absolutely amazing. I get essentially zero spam in my inbox, and perhaps 4-6 false positives in the spam folder a month. >As a Gmail user, there is nothing you can do to verify that you're getting all of the legitimate mail traffic that is being sent to you. What oth…
> 4-6 false positives in the spam folder a month. That seems like a lot; with FastMail I get basically 0. The last time this happened was years ago. I do get the very occasional spam, maybe 5 messages/month or so. Most of them are from marketing agencies that want to "collaborate" on my website or some such and have a spam score of 0 or close to it, and arguably isn't "spam" in the same way as "grow a bigger dick!"-s…
Re: Just Use Email – How to Use Email for Everything
#236Re: Just Use Email – How to Use Email for Everything
#237Earlier quoted context omitted.
> However, I'm not sure if it will ever be the popular thing even among the free software options. I'm one of the many people actively working on XMPP projects. Is there something in particular that makes you think this? People often talk about XMPP in the past tense on HN. It's understandable, XMPP had a peak of popularity with the adoption of Google Talk, but Google being Google and shutting that down did not end X…
Check out Google Trends with XMPP
I feel it's right that a protocol doesn't need to be in the general consciousness. See the even worse Google trend for SMTP, for example, despite email still being considered a growing network.
I wrote a bit about protocols being for developers and not users at https://snikket.org/blog/products-vs-protocols/
Re: Just Use Email – How to Use Email for Everything
#238I'm on the exact opposite end of the spectrum. I haven't used email outside of work for many years now, and don't miss it one bit. And even at work most communication now happens on Slack. The digital world has evolved since 1997, and email simply hasn't kept up. I skimmed a couple articles on the blog and my biggest problem with it is that the author is making a social rather than technological argument (which are a…
I'm with you, I absolutely cannot stand using email unless I absolutely have to, which is mostly just at work. And it's a fine way for government or businesses to contact me, just like mail was. But just like mail letter writing declined after the invention of the telephone, e-mail has declined after the invention of IM
Re: Just Use Email – How to Use Email for Everything
#239Earlier quoted context omitted.
When you move to a new country that has a dominant messaging app, you can't avoid installing it without making your life a lot more difficult. And moving already makes your life difficult enough.
The real question though is how you determine the “dominant app”, that’s really not that obvious, especially when you don’t speak the local language. Long term you might be right, installing an app would be beneficial, but in the short term it’s a lot safer to just use email.
Re: Just Use Email – How to Use Email for Everything
#240Earlier quoted context omitted.
Then should we not amend the protocol to define these things? Why reinvent the wheel, when we could improve it?
> Then should we not amend the protocol to define these things? Most of the OP list of things they don't like are about client UI presentation. Inherently unrelated to the protocol itself. I don't have any of those issues because I use a client that does the interaction and presentation exactly how I like it.