samuelgoto/sms-receiver: phone number verification
An interesting proposal to allow websites to detect certain SMS messages. The UX implications are fascinating.
#standards
-
On AMP for Email by Jason Rodriguez
Philosophically, I’m completely against Google’s AMP project and AMP for Email, too. I will always side with the open web and the standards that power it, and AMP is actively working against both. I’m all-in on a faster web for everyone, but I just can’t get behind Google’s self-serving method for providing that faster web.
-
How not to replace email (jamey.thesharps.us)
I’d say the single most important lesson to take away here, for a technology project at least, is that interoperability is key.
- Assume that no matter how amazing your new tech is, people are going to adopt it slowly.
- Give your early adopters every chance you can to use your offering together with the existing tools that they will continue to need in order to work with people who haven’t caught up yet.
- And if you’re building a communication tool, make it as simple as possible for others to build compatible tools, because they will expand the network of people your users can communicate with to populations you haven’t thought of and probably don’t understand.
-
WebSub and IndieAuth Published on w3.org!
Today, we published the last of the two W3C specs I am editing! WebSub was published as a W3C Recommendation, and IndieAuth was published as a Working Group Note.continue reading... -
Your friendly reminder that without open standards, you're not "buying" smarthome hardware, you're renting it. http://www.businessinsider.com/googles-nest-closing-smart-home-company-revolv-bricking-devices-2016-4 -
Just used an Apple USB-C/HDMI adapter to connect a Windows laptop to a projector. #standards #ftw
-
A short note about web standards from your friends at Known (stream.withknown.com)
Any new web standard must be easy enough to understand and implement that a developer can get something up and running in an afternoon. HTML, HTTP and RSS all adhere to these principles. So do the indieweb protocols, which is why we support them and think they are likely to succeed.
-
Talking to DC | Adam Bosworth's Weblog (adambosworth.net)
Standards work best when they are focused. Don’t build an 18 wheeler to drive a city block. Standards often fail because committees with very different complex goals come together without actual working implementations to sanity check both the complexity (see point 1 above) and the intelligibility (see point 2 above).
-
So you implemented an OAuth 2.0 API...
While OAuth 2.0 is a good framework for building an API, the spec itself leaves many things un-specified, and it's up to the implementer to make a decision based on their own security requirements. As such, most OAuth 2.0 implementations are not interoperable, which is often cited as a failure of OAuth 2.0. On the other hand, the current state of OAuth 2.0 implementations is that they are often similar enough that developers don't need to learn too many new concepts when dealing with them.continue reading... -
OAuth 2 Simplified
This post describes OAuth 2 in a simplified format to help developers and service providers implement the protocol.continue reading... -
Introducing IndieAuth
IndieAuth is a service that implements RelMeAuth, originally proposed by Tantek Çelik in February 2010. The original algorithm was described in a short text update on Tantek's website. Later that evening, Jeff Lindsay and Paul Tarjan implemented RelMeAuth in an open source Python library at Hacker Dojo and discussed/tested it in IRC. Tantek later launched a RelMeAuth prototype on his domain, which you can try out at tantek.com/relmeauth.continue reading...
