Earlier quoted context omitted.
Why can email not evolve? Structured data in markup works well on the web. It's open and could be implemented by any client.
It's only "open" in that they detail the spec they've come up with. Email has been so useful and resilient only because it's an open standard which is broadly agreed on and adopted. Once the big players start adding custom features on top of existing protocols we start seeing fragmentation and parts of the market being cornered off. Once people start depending on this custom functionality, the vendor usually starts r…
Email Markup in Gmail
71–80 of 113 posts
Re: Email Markup in Gmail
#72Re: Email Markup in Gmail
#73Earlier quoted context omitted.
ProtonMail may not be the best choice if you're a stickler for standards. Their service unapologetically works only within ProtonMail. Send an e-mail to someone with a different provider and they get a link to a https view of the email.
Thanks, though I set it up yesterday mostly for receiving, I don't plan to send anything from it Is there another email provider that isn't hotmail, gmail or yahoo mail with good prospects at the moment?
Re: Email Markup in Gmail
#74Earlier quoted context omitted.
It's only "open" in that they detail the spec they've come up with. Email has been so useful and resilient only because it's an open standard which is broadly agreed on and adopted. Once the big players start adding custom features on top of existing protocols we start seeing fragmentation and parts of the market being cornered off. Once people start depending on this custom functionality, the vendor usually starts r…
How have the "walls been raised" with Hangouts?
Re: Email Markup in Gmail
#75Earlier quoted context omitted.
How have the "walls been raised" with Hangouts?
You can no longer communicate with Google users with the XMPP client of your choice. They require you to use only their client.
Re: Email Markup in Gmail
#76Note that this only is available to high volume senders ( https://developers.google.com/gmail/markup/registering-with-... ): > Consistent history of sending a high volume of mail from your domain (order of hundred emails a day minimum to Gmail) for a few weeks at least.
I'm disappointed this restriction is still in place (though I understand _why_). My SaaS sends emails on behalf of our customers (using their From address). Individually they don't send 100 email per day to Gmail, but in aggregate our platform does.
Is there a "name" problem faced by email providers?
Re: Email Markup in Gmail
#77Earlier quoted context omitted.
How have the "walls been raised" with Hangouts?
You can no longer communicate with Google users with the XMPP client of your choice. They require you to use only their client.
That's not quite true.
Google Talk is still available, and you can use that in place of Hangouts, and you can use third-party clients with it.
However, you cannot use third-party clients for group chats, and you cannot speak to users on other XMPP servers (there is no true federation).
Re: Email Markup in Gmail
#78Earlier quoted context omitted.
It's only "open" in that they detail the spec they've come up with. Email has been so useful and resilient only because it's an open standard which is broadly agreed on and adopted. Once the big players start adding custom features on top of existing protocols we start seeing fragmentation and parts of the market being cornered off. Once people start depending on this custom functionality, the vendor usually starts r…
It's only "open" in that they detail the spec they've come up with. The spec is schema.org, which is a format defined by multiple parties, not just Google: https://en.wikipedia.org/wiki/Schema.org And it's encoded using JSON-LD, which is also not a Google creation, and it's standardized by the W3C.
[0]: https://developers.google.com/search/docs/guides/intro-struc...
Re: Email Markup in Gmail
#79Earlier quoted context omitted.
You can no longer communicate with Google users with the XMPP client of your choice. They require you to use only their client.
I can still chat with Google users via Adium. I suppose if they're not using XMPP they're doing something else, but if Adium supports it, it's probably in libpurple, which means Pidgin and other OSS clients can do it too.
Why send the rest of the ecosystem scurrying about, chasing their tails?
And if the ecosystem gets the rug abruptly pulled out from under it one time, then how many more times will their efforts get trashed? Probably as many times as is necessary to shake them loose.
No announcements, no roadmap, no communication channel, just a sudden upgrade and everything starts timing out, or throwing errors.
Someone threw the killswitch. And they'll toggle it as often as needed, to cut out whatever the target percentage of attrition is.