![]() ![]() ![]() Or, rather, a few people who I know are starting to help, and I want to keep it small for now since Iâve never done this before. I posted this because Iâd like to have people help me with the app â but Iâm not ready yet. I published the first draft of Evergreenâs Coding Guidelines yesterday. My default position now is: if a format or API or syncing service makes sense for a feed reader, then Iâll (at least try to) support it. Thatâs just for starters: I also decided to look into everything else and see what makes sense to support. I may have a difference of opinion when it comes to feeds, but who the hell cares when thereâs so much good stuff to do? (Theyâre not holding my opinion against me why should I hold theirs against them?)Īnd so I decided to support the h-feed format in Evergreen (hopefully in 1.0). It took me a while, but I realized that I was acting like a Clinton or Sanders supporter still arguing with the other side about the 2016 primaries â after losing the general election to a monster, after the point where those small differences matter at all.Īnd then I started to get excited about IndieWeb. In the last couple years Iâve been chatting with Manton Reece, Micro.blog creator, a bit â and Manton agrees with me about feeds.īut Manton also works with IndieWeb, and has mentioned any number of good ideas they have that I should look into. (Iâm telling you about this so you can learn from my mistake.) Fast-forward Hereâs the thing, though: that was me being a total jerk. And, while I understand the elegance of microformats, side feeds have critical advantages that microformat-feeds donât. Feeds have been and remain tremendously successful â see podcasting, for one thing â and the way forward is to build on that success. ![]() I took it personally, since Iâd spent much of my career working with feeds, and I took this as a suggestion that my career was all wrong and they wouldnât be interested in someone like me, someone who would be an ally in their committment to the open web. I donât know which thought occurred to me first: The argument (I think I hope Iâm not misrepresenting anyone) was that microformats are simpler than mantaining a separate file. Their idea was that the data a reader might collect should be encoded in the page itself, using microformats. When IndieWeb started, some years back, the first thing I noticed was that they appeared to be against the idea of feeds â or, at least, what they called side feeds: RSS and similar. I wonder if more and more companies will find value in having a podcast too. (Though, of course, people can decline: itâs not required!)Īnyway: there was a time before companies had blogs, and now they have blogs. And itâs small enough to still be intimate â my goal is to eventually interview every single person who works here. It may be that Omniâs size is somewhat unique in the Mac and iOS world: itâs big enough that we wonât run out of people to interview and topics to talk about, which could be tricky for a 5- or 10-person company. And there are much larger companies (such as Microsoft) who create videos and podcasts. There is the Supertop Podcast from our friends who make Castro. Iâve been wondering if other companies in our world are doing similar podcasts. You can subscribe to the podcast or just listen to this episode â thereâs a player on the page. There will be new releases of OmniOutliner, OmniPlan, and OmniGraffle â plus a whole bunch of great stuff for OmniFocus 3.0 for Mac and iOS, including tags, JavaScript scripting, and OmniFocus for the web. Check out episode #7 (I wish we had called it 007) where Ken Case talks about all the good stuff coming up in 2018.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |