LoqiGoogle Maps is a Google's web application for viewing a map, getting directions, and keeps track of your location history (opt out) https://indieweb.org/Google_Maps
aaronpkin doing this indienews update and testing it with woodwind, I'm realizing the typical author+content model doesn't represent all the parts of things posted to aggregators
aaronpkmost of the posts on indienews are submitted by the author. that ends up looking fine in a reader. however if someone submits a bookmark of some other site, then what should the reader show as the author?
aaronpkif the reader shows the bookmarked site as the author (which most closely matches what it looks like on indienews) then the submitter doesn't appear in the reader
tanteke.g. most commonly, we see posts that show Chris Aldrich as the author of an article, but it's actually just him as the author of the *bookmark* of the article, and Loqi does not show the actual author of the article
aaronpki had the same problem when I just added microformats to https://bulletin.p3k.io/aaronpk so that you can subscribe in woodwind. it's even more subtle here, because each post there may be "submitted" by a bunch of people because they tweeted it. and in this case, Bulletin is doing its own curating so really the "bookmarker" of those posts is Bulletin!
tantekThe way I would approach this is to first document screenshots of how "bookmark" posts are presented at all, both individuall (on a bookmark permalink page), and in a list / collection, both on personal site(s) and silo(s)
aaronpkwell i don't feel so bad about this being my project for today because turns out enabling websub on indienews made all these other issues apparent
tantekthen yeah, news.indieweb WebSub support which then revealed a bug that you fixed in WebSub.rocks *definitely* counts as a good productive indieweb project for the day, the visible bit being the bug fix in websub.rocks
voxpelliaaronpk: bookmark or repost sounds correct – and if a reader then could interpret the interaction type then it could present it as "<author> <interaction> <title>" rather than "<author> posted/wrote <title>"
tantekprobably would have counted with just the "adding websub" support, but the extra visible bit is really good to point out, plus advancing a test suite is a pretty big deal
tantekand that aspect of, we are building UX that is leveling up (and beyond) what "social media" silos provide is a key distinguising aspect from just "Blogs & RSS"
aaronpkvoxpelli: look at the top post on indienews right now. it's submitted by boffosocko.com. that one makes sense to me as a bookmark, since it's clearly submitted by him and the thing being bookmarked is on a different domain. however it's less obvious to me that the next one is a bookmark.
aaronpki submitted my Day 31 post to indienews. I don't have a post on my site that's a bookmark of that post. does that mean the indienews post is a bookmark? if so, who is the author of the bookmark post?
voxpelliI think you is the author of that bookmark post. Consider IndieNews a collection and posts added to the collection makes sense to name as bookmarks of that collection
voxpelliin my reader I would love it to appear as "aaronpk saved <title>" or "aaronpk added <title>" just as I would love to see "boffosocko.com added <title>"
tantekKevinMarks: no one ever documented or did anything remotely resembling good "repost" design / UX with Atom so I have zero confidence in any plumbing that was designed / created abstractly
tantekyes, they at least tried to start with documenting use-cases, but never took the additional step of brainstorming design / UX before coming up with markup to represent the things in actual design / UX
voxpelliit's a good thing we keep u-bookmark-of and u-url separate, in RSS/Atom it's often the u-url equivalent that gets set to the external link and the internal one is put elsewhere, like as rel-related in Daring Fireball
voxpelliaaronpk: actually not so sure about the bookmark thing, feels like we need development on the indiereader side to really figure this out – right now IndieNews is set up in such a way that the entries there are no real entries, but rather just points to external entries – and that's probably right
voxpellimany indiereaders seems to be be designed like a classic feed reader which in turn is designed like a classic email inbox rather than the more stream like interfaces of social medias
LoqiA feed reader is an application (local or on the web, like the defunkt Google Reader) that subscribes to feeds (typically legacy Atom & RSS) and presents them in an interface for reading https://indieweb.org/feed_reader
sknebelunread-tracking (I don't insist on actual numbers displayed) is incredibly important for some types of feeds for me. The ability to turn it of on a per feed(group) basis would be nice though
aaronpksome podcasts I listen to every episode. others like news podcasts I only care about the latest one since I don't care about last week's news anymore.
voxpelliaaronpk: just wanted to fav/like your post – if you want a project for another day, then webactions would be neat ;) Because you have none, right?
aaronpkthere's some part of it that still seems like a "hack" to me, like it's taking advantage of a browser feature in a way it wasn't intended and might be removed from browsers because of that
tantekagreed - voxpelli I think there is work to be done there as Barnaby's add-on hasn't been updated in ages - and modern browsers require add-ons to be submitted etc. for better installation flow / security
tantekto answer that "why" - because 1) XSLT is a pain, and 2) people into feed files usually don't care as much about making things look nicer (since if they did, they'd likely focus more on the HTML+CSS of their website than the feed files)
aaronpki opened an xml feed in safari, it popped up a message asking if i wanted to add links from that domain to "shared links" (what is that?!) and when i clicked cancel it launched chrome with the URL of the feed prepended with feed//
voxpelli(now I just need to setup a service that can give me some reply contexts so that I can stop showing raw URL:s in there and get it to actually look nice)