WeChat ID
aaronpk_tv
-
@leoville.net oh good, it looks like it worked! :-D -
@kenichi_pdx @donpdonp @pdxmele This is super cool! See: https://twitter.com/pkoonce/status/446135974813130754
-
Spotify Introduces Video Clips, Podcasts, And Activity-Based Playlists | TechCrunch (techcrunch.com)
Spotify is also creating a new format of music, wherein the composition actually changes and rearranges based on your pace.
-
Jᵾlien Genestoux
https://twitter.com/julien51
•
May 19
Spend years ignoring other people's work, then, change your mind, and tell them how they're wrong.
@julien51 I certainly didn't mean to come across that way! The reason I haven't contributed to PuSH until now is because I still had a lot of catching up to do myself, making better publishing and consuming tools for myself. Now that I'm actively publishing short notes on my site, and reading others' posts in my reader that supports PuSH, it's suddenly extremely relevant! I hope the takeaway would be that there is now a renewed interest in PuSH which should help make it better and be adopted by more people! -
@julien51 this makes me :( you do amazing work making the open web fast (so many other services are choose one or the other). very grateful!
-
The new custom domain feature means @Medium looks more like a great web host rather than a content silo! https://medium.com/the-story/custom-domains-for-publications-8cb161d9651 #indieweb
-
This really is just pointing back to the question of what is the original goal of this spec. If the goal is to describe a way for consumers to subscribe to content, then yes, publisher->hub is not needed as part of the spec. Since that's what @julien51 described, then it sounds like the best course of action is to document the publisher->hub interaction separately, with the goal being to make it possible for publishers to use generic hubs.
