#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://indiewebcamp.com/aggregator
#tantekgyuumaou: ^^^ check that for rss aggregators that people may be using!
#gyuumaouthank you; i tend to forget this is built around a wiki so i dont think to search.
#acegiakOK my friend's coworkers are being targeted by Gamergate for daring to put a transwoman in a popular franchise. Time to start removing personal information from my blog
#snarfed!tell tantek just fyi, i haven't fully figured out why your other IG responses haven't backfed, but it may not end up a high priority. accounts switching back and forth btw public/private definitely isn't a case that bridgy sees much or has much practice with, especially applying to older responses. (it stores and reuses most of the post/response data internally, eg public/private.)
#aaronpkso should I be sending webmentions to URLs of the people who leave comments on my post? now that I re-read /salmention it doesn't actually say to do that
snarfed joined the channel
#tantekalways design it from the UI down to the protocols, so in this case, what are the notifications those commenters should see?
#Loqitantek: snarfed left you a message 45 minutes ago: just fyi, i haven't fully figured out why your other IG responses haven't backfed, but it may not end up a high priority. accounts switching back and forth btw public/private definitely isn't a case that bridgy sees much or has much practice with, especially applying to older responses. (it stores and reuses most of the post/response data internally, eg public/private.) http://indiewebcamp.com/irc/2016-04-05/line/1459867365008
#aaronpkin this case it indicates that their comment was accepted/approved and is now displayed on my site
#aaronpki don't actually moderate comments, but many people do, and it would indicate that the comment passed the moderation step
#tanteksnarfed: definitely not a high priority for Bridgy. Was hoping you could use the data to perhaps find other bugs as I think many of those cases should have worked (e.g. before I flipped my account to private 2015-02-??, but after the nested h-feed bugfix on 2015-12-31)
#tantekaaronpk: interesting. in that case, first document that as a /notification use-case, and then link from there to /Salmention as the mechanism for enabling it
#tantekbasically, we should stick to a pretty strict practice of not "just" implementing protocols for protocols sake, but rather first requiring ourselves to explicitly document the desired UI effects, and precisely how those require what protocol interactions, and then and only then actually implement those protocol interactions
#tantekit will force us to only implement plumbing when necessary for specific UX, rather than getting lost in the classic dev-centric plumbing implementation for plumbing's sake trap
#tantekinvited ~140 people to HWC SF - let's see if the Bridgy webmentions show up here ;)
#aaronpkyes that makes sense. I think I implemented this without thinking about it because it wasn't a huge leap from how I am sending webmentions for links in my posts.
#aaronpkbut then snarfed pointed out he was surprised to see a webmention sent from my page immediately after he sent one to me
#aaronpki'm going to remove it since there isn't a good reason to have it, but the "u-like" bug in semantic-linkbacks that tantek fixed is still definitely necessary
#tantekaaronpk: the use-case for resending webmentions to earlier comments, when someone makes a new comment, is the notification "So-and-so also commented on a post by Aaron Parecki"
#aaronpkSalmention says "then resend Webmentions to everything the original post sent webmentions to" which is not the same as sending webmentions to URLs in comments
#sknebelGitLab pages seems interesting for people running static site generators
#sknebelif I understand correctly, Github pages requires an external build service if you want more than stock Jekyll, GitLab integrates with their own, so you can run whatever SSG you want
#voxpelli+1 on aaronpk interpretation on Salmentions
#aaronpkvoxpelli: i don't even know how i'm voting on this :P what do you mean?
#voxpellisknebel: yes, it requires that you push the HTML then, but one can make eg. Travis do the build for you
#voxpelliaaronpk: the "not sending mentions to comments"
#aaronpkyou think we should *not* send webmentions to comments?
#sknebelvoxpelli: ok, then I remembered that right. Readymade examples + not having to link 2 services hopefully makes it even easier for people to get started
snarfed joined the channel
#voxpelliaaronpk: I think of Salmentions as purely upstream
#aaronpktantek's example is interesting, is there a different way of accomplishing this?
#voxpelliprobably, it's at least distinct from the upstream flow
#GWGI've decided to table the Indieweb plugin for a bit, since I feel stuck on that, and switch over to a PR for the Webmention plugin that brings it closer to the specification
#Loqinotifications in the context of the IndieWeb refer to all forms and ways that an independent web site can receive a message indicating something of interest (server notifications), and potentially relay that information (preferably in realtime) to one or more devices used by the owner of that site (client notifications) https://indiewebcamp.com/notification
#[kevinmarks]Right, but that is an out of band email notification
#[kevinmarks]Known emails you when it receives webmentions by default
#aaronpkevery notification is out of band, by definition :P
#gRegorLoveI like the idea of subscribing in a reader
#[kevinmarks]Well, it's different when the comment is in a silo. It can't ping the comment url
#gRegorLoveFB auto-subscribes you to notifications when you interact with a status. I often will immediately unsubscribe after I comment because I don't need to hear that all these people I don't know also commented.
#bearI was waiting for a concrete reason to move the raw data into something more searchable - this sounds like a good reason
#bearoh, don't look to close - it was my first flask api
#snarfedbasically my hope was that it indexed crawled pages by mf2 class, e.g. h-entry, p-content, u-like-of, so that i could give it one of those and it would give me back all pages/sites that use it
#bearI also store the html returned in case we ever need to regenerate that mf2 blob
#snarfedcool. but no search functionality like this yet?
#KevinMarksthe mf2 blob loses p- vs e- distinction though
#bearno, I was waiting for a reason so I had something real to target
#snarfedKevinMarks: exactly, hence indexing by html class
bengo joined the channel
#snarfedbear: ok! feature request then. :P i have a question like this once a month or so. more examples in the first paragraph on http://snarfed.org/indie-stats
#bearcan you file a ticket for me (in a work meeting)
#tantekyeah, no one POSSEs to Path or Slack AFAIK (other silos with reacji)
#snarfedppl manually posse to github a bit, but no backfeed afaik yet
#tantekinteresting - Swarm does not give you "coins" credit for photos posted via IG, only on photos posted directly as part of a checkin on Swarm
#tantekthus lending more credence to the theory that photos (in general) on Swarm are treated like comments unless they are literally attached at the precisely moment of checkin directly using the app
#gRegorLoveI thought Path had died, but apparently not
#[shaners]Looks like 1.1.2 - August 17, 2013 (7 KB) was the first of the renamed one.
#aaronpki've been moving things around on my servers, and tried to bundle install my twitter search code which used that gem, and it said it was disappeared
#snarfedKevinMarks: oh if it's indiewebcamp's, and the event is on your site, you also need to add your domain to indiewebcamp's fb profile and re-sign up w/bridgy