@zakkain at the moment everything I post is a note or an article, both of which get POSSEd to twitter automatically by my server and then to Facebook manually if I want. Delegating to an external service, even if it’s one I manage, is probably a good long term solution, but I always want to get the syndicated URL back on my site which complicates things a little more.
I know others are having success using IFTTT for POSSE.
I’m beginning to think that I want to store two broad categories of content on my #indieweb site, content which is defined by the time it occurred/is published and content which is primarily defined by some other attribute.
Examples of content defined by time, which at the moment I’m using notes for:
Examples of content primarily defined by things other than time:
Can’t particularly recommend the soup at Fish and More (Reykjavik) — expensive but didn’t taste of much. You’re better off going to bergsson.is
The #randomchilies are growing super-fast in the eternal sunlight:
@sandeepshetty that’s the reason for reply contexts — dealing with content which changes or goes away. If you store the reply/like context then your copy of the data is always the most valuable, most complete. Otherwise it’s the copy shown on the remote site.
@benwerd “barnabywalters, international man of mystery. What is his real name? The microformats parser just can’t tell!”
Checked into Vísar for the second day of #indiewebcamp Reykjavik Remote party
“So easy is it, though many housekeepers doubt it, to establish new and better customs in the place of the old.”
— Walden, Henry David Thoreau
Talking about peer-to-peer federated file sharing at #indiewebcamp Reykjavik remote party:
@sandeepshetty footnotes in a note?! Preposterous! :D
@packagist feature request: ID attrs on each version element on package pages so we can link to individual versions