Another awesome release from the Deno team! I really love the emphasis on web compatibility. It's great to hear that they're working on getting displayed on MDN. That'll be really useful and maybe even raise awareness of Deno.
I made a small change to my site, so that bookmarks don't show up in the main feed unless I've commented on them. I tend to bookmark a lot of pages, so this will keep them from clogging up the home page. Plus, it clarifies the difference between bookmarks and boosts/reposts. Now, boosts are posts I don't have anything to add to, but still want to show up on my home page. Bookmarks are pages I want to save for later, but may have something to say about once I read them.
These bills seem very promising. Each bill seems designed to tackle one major issue and they're all scoped to only huge companies. I'll be watching them closely.
IndieForums looks nice. Seems like it might be a good catalyst for some blogchains and hyperconversations. https://indieforums.net Also on:
Yea that looks like a cool site! I hope it catches on, but we also have IndieNews and Indieweb.xyz and those have never really had huge usage.
I wonder if we just don't have a large enough community, yet, to sustain a forum like this. Or maybe showing the replies inline, like IndieForum, is what the other two were missing. That does make it much easier to follow a conversation.
In this blogpost I argue the case for consigning the term "REST API" to history. In its place we should adopt the terms "HTTP API" and "hypermedia API", which better differentiate two distinctive designs for the programmatic interfaces of web services.
This makes me think about the die-hards who are against the Web as an application platform. They always say the Web was intended as a document platform and therefore shouldn't be used for applications. But Fielding modeled the REST architecture on the Web, and he and others working on the initial tech considered it to be a large, distributed application. So by that line of thinking, the Web as an application platform is nothing new. These separate web apps are just sub-features of the World Wide Web application.
In this blogpost I argue the case for consigning the term "REST API" to history. In its place we should adopt the terms "HTTP API" and "hypermedia API", which better differentiate two distinctive designs for the programmatic interfaces of web services.
Fielding's thesis was a kind of retrospective on the design decisions that led to the World Wide Web — a distributed hypermedia-driven information retrieval system — becoming the runaway success it was.
I've read about Fielding's REST dissertation (never actually read the dissertation itself), but this is an interesting way to think about it. I've tried to explain the ideas behind REST to colleagues before, but I don't think I've ever been successful. Describing it with the Web as an example of the architecture makes it much more tangible.
In today’s Webmentions Beyond Webmention.io online meet-up there was a request for people who were willing to implement their own
I've built a custom webmentions receiver into my site. Maybe I could extract it out so it could be run standalone, too.
Office politics: A working letter By now, you’ve likely already heard that the Basecamp founders attempted to sink their company with, among other things, an...
We don't need it, but here's more evidence that digital-only media is a bad idea. When people talk about the all-streaming future for gaming, this is why I dread it.
I don't understand why #Mozilla is so intent on ruining their users' attitude toward them and Firefox. They're just going to slowly take away every useful feature in Firefox until it withers away to nothing.
