endiPardon my ignorance of on-going projects and ideas but is anyone working on or talking about something resembling an aggregator for content originating on indieweb sites?
endiyeah, I was aware of Woodwind, what I was thinking was somewhere between Medium and Reddit. You'd register your site and it would automatically aggregate/categorize and perhaps surface individual posts based on activity
voxpelliat the more general level, with POSSE and everything, the more IndieWebby idea would be to mix indieweb-content with silo-content if one wanted to do a more generic aggregator
endiI think it would be really interesting to see people utilizing all the powerful tools I've been discovering and playing with sort of, in action, on a more general scale not necessarily feeding back into indieweb
endiwhat I was thinking would be a way to aggregate and surface posts from indieweb people that would help discovery of sites and ultimately promote the idea that your content or posts can be discovered outside your personal network
endithat's kind of why I say somewhere between a reddit and medium because I see posts on medium from people I don't follow, perhaps wouldn't follow, but it gets surfaced and that's kind of a cool aspect of medium
endiso if I used indieweb tools and platforms let's say Known to make a 'chemistry-of-cooking' or 'sous-vide' style blog I could register it at indiewebaggregator.com/food and when I make posts it might pull it into the /food stream and perhaps surface it more based on activity
endiI can see where someone would have to ban/moderate the included sites and that could smell of centralization, but I'm sure a reporting system with loose moderation could be effective. at least a 'hide posts from this domain'
endiso if I as a user were interested in Maker/DIY I could go to indiewebstream.com/maker and see posts people who have registered with the site and have tagged as 'maker' or 'diy' and see all the hardware projects etc that indieweb users are posting about, even if I don't know them or none of my friends know them
voxpellibut just for regular blogs, not enhanced with any extra IndieWeb stuff, but from a perspective of Medium the IndieWeb stuff doesn't add that much – it's more when one try to duplicate Twitter/Facebook that IndieWeb does
voxpelliright now not that many tools in the reader/aggregator space has been built – but since the IndieWeb is an evolution of eg. blogs, many tools that has long worked for blogs can easily be upgraded to make use of IndieWeb tech
endiI was just thinking "I wonder what 'indieweb' people use these tools/formats/etc to do" and from that came what if there was a place it was all aggregated based on the use of those tools rather than determined by my social media network or any other existing structure
endiI like and appreciate the power of aggregators I use daily for content and sources I've curated. I just wonder sometimes what I'm missing because I haven't yet found that person/source
Loqiaaronpk: tantek left you a message on 11/20 at 12:49pm: remember how we used to have the bright orange banner at the top of IndieWebCamp.com when there was an imminent upcoming IndieWebCamp (e.g. "IndieWebCamp 2015: July 11-12 in Portland, Oregon and Brighton, UK!"), could you flip that on for IWC SF? http://indiewebcamp.com/irc/2015-11-20/line/1448052538602
cleverdevilthey do say, on one of the (many) calypso sites - "We're excited about the REST scaffolding going in WordPress 4.4, but the endpoints in the latest version don't cover a huge part of what we're doing. Automattic contributors to core have been heavily involved in the core API work so far, and we expect that to continue and increase in 2016, hopefully completely harmonizing the different APIs in one of the core releases next year."
tantekdoes the API between Calypso and the WordPress PHP backend require sending username/password? Or does it use OAuth to authenticate the front-end?
snarfedthey've been pretty clearly that self hosted wp shouldn't require wp.com, jetpack, etc. so calypso could require it if calypso itself is optional, but otherwise doubtful
aaronpk"If you run your own self-hosted WordPress site, you can install the Jetpack plugin to use the Calypso-based editing and management tools. Your site will be ready to go once you log in to WordPress.com or download the Mac desktop app."
bengo(in the indieweb of microservices, should everyone have a personal Authorization server that is complementary to their personal www site? I think so, even if it delegates authentication to something like indieauth or wp.com or webid or something)
aaronpkexcept you should have said "delegates to something like indieauth.com" instead of "indieauth" since indieauth is the protocol and indieauth.com is the service
gRegorLoveLooks like it does. "Why do I need a WordPress.com account? Many of our core features (like Photon, Stats, and Protect) make use of the WordPress.com cloud. For this to happen Jetpack requires a (free) WordPress.com account. If you don't have one already you can easily create one during Jetpack's connection process." https://wordpress.org/plugins/jetpack/faq/
rhiaroHey everybody! This is a call for you to add yourself to indiewebcamp.com/mentions if you have a page displaying your mentions/replies/etc. If you have a private one/behind auth just for yourself, also note that
voxpellikevinmarks: give me a shout or add an issue on the project if you start feeling the need for some pagination – you will probably be the first one ;)
tantek.comedited /h-entry (+1619) "move why to top, expand for publish/consume, expand how to for publish / consume, indieweb examples, requests" (view diff)
LoqiIndieWebCamps are brainstorming and building events where IndieWeb creators gather semi-regularly to meet in person, share ideas, and collaborate on IndieWeb design, UX, & code for their own sites http://indiewebcamp.com/IWC
tantekbasically if you have a question about something, like IWC, you can usually just ask "what is" to get the overview of it and likely the answers you're looking for
voxpelliwell, that's only for simple shares + it requires at least two-three taps per publish rather than just having it as a maybe default on share option in the posting ui
voxpellihard to argue with those independent app creators today that they should learn indieauth, micropub etc – too much effort for too little gain for them
voxpellithat's why eg. http://pragmaticcode.com/linky/ is used by some social media people rather than just doing multiple individual sharings – that + some better options
Loqishare is a watered down verb that's used on the "social web" (and other platforms like Google's Android) to mean pretty much any action https://indiewebcamp.com/share
tantekbasically, if you want vagueness in your UI, or you're not sure what to call an action, call it "share", because that's what (nearly) everyone else does when they don't have a precise name for something
kylewmgRegorLove: this may already be resolved, but bridgy used to have h-as-repost but I (sort of unilaterally) changed it recently to h-as-share since "repost" wasn't in AS1
voxpelliI think 403 makes sense for the case of unaccepted source / vouch – makes it clear that it's not anything about the format of the reuqest that isn't accept but rather the actual content
voxpellia 401 would convey that the password is wrong, a 403 conveys that the permission of the requester to perform the action has for some reason been denied
voxpelliben_thatmustbeme: well, right now allmost all errors in Vouch uses 400 so to have two errors both use 403 wouldn't be that bad – after all, detail error information should be delivered in addition to HTTP code
tantekthe days of overly precise error messages in protocols are long past - those days when everyone developing protocols assumed people were "nice" on the internet
voxpellitantek: it was in response to ben_thatmustbeme's feedback that using the same code for two things would be bad, with that thinking one should specifically avoid using a code for just that purpose
voxpelli(eg. http://jsonapi.org/format/ also lists lots of 403 uses that are not directly linked to authentication but rather just refusals of different kind)
voxpellia 400 is actually documented as "something that is perceived to be a client error" – and a denied vouch isn't really that, but I can see a reason to disguise as it
voxpelliben_thatmustbeme: well, /mentions refers to both post mentions and homepage mentions – but mostly for having a separate page for mentions I guess now when I reread so you don't fit that
voxpellione can consider a mention of a post to be a mention of a person to mimick behavior of Twitter – I guess that's what the three of us has currently done