GWGI custom coded a few composite streams, but not the firehose one I wanted. I had a little trouble because the main feed is so hard to relocate from the default location, and I didn't pursue it too much
[tantek][jeremycherfas] I wonder how useful that Known actually is (what use-case(s) is it solving?), in contrast to approaching a paradox of choice UX problems, and maintenance of such a feature over time.
jeremycherfasOne use-case, for me: I can create a feed for syndication to micro.blog that does not include, for example, simple Likes. I see no point cluttering up micro.blog with those.
Loqijamietanna: jacky left you a message 1 week, 3 days ago: noticing that you have a scope of 'notify' - how do you implement that? UnifiedPush? MQTT?
jamietannajacky ah I've not yet done it as an arbitrary "send a request here and notify me of an arbitrary thing", but I do have Pushover set up for push notifications, and that sends me notifications if i.e. I get a webmention
jarkad, jarkad1, jarkad2, mro, kloenk, tetov-irc and jacky joined the channel
[tantek]that said, (switching to #indieweb-dev from #indieweb re: Tumblr & IndieWeb adoption), Tumblr adopting of Webmention will paint a bigger target and likely require stepping various Allowlist / moderation / nicknamescache / Vouch efforts to make Webmentions "work smoothly" (i.e. to not have to moderate every single interaction the way WordPress often does), and still block bad actors
[tantek]part of the reasons I haven't pushed for Webmention in WordPress core is, there's kind of an expectation / responsibility to demonstrate in a plugin that Webmentions *can* "work smoothly", which is not the case right now (it's still too awkward to setup, moderate etc.)
[fluffy]But yeah there’s definitely some rough edges on Webmention that need to be addressed. There’s a reason I don’t actually use webmention.js as a primary interaction mode on my site, despite most of my comments etc. coming in via webmentions via bridgy
[fluffy]Some of it could be fixed by improvements to webmention.js, some of it could be addressed with things like salmention, but much of it I feel is hugely difficult in terms of community expectations and also the sharp corners of protocol when it comes to things like private entries.
[fluffy]As it is, it’s unfortunate that a lot of responses to my private entries come in the form of public mentions on Mastodon (again via bridgy). I don’t know why it’s so much easier for people to reply on Mastodon than to post a comment on my own friggin’ site, when Mastodon doesn’t even see the actual page content or even the title.
[fluffy]To actually read the entry they have to click through, sign in, discover whether they even have access to it (because everyone sees that there is *a* restricted entry but not whether they themselves can see it, because that’s the piecemeal world we’re in right now), then read it on my site, and then for them to go back to Mastodon to respond there feels weird.
[fluffy]Like even in a perfect world where we’re all using TicketAuth-enabled feed readers for content discovery, posting a public Webmention to a private entry is a huge problem.
[tantek]maybe "posting on Mastodon" means they have a greater sense of owning their words, like they have a permalink that they think they control of their comment, as opposed to commenting directly on your site?
sknebel(going back to UI: e.g. if you put a link in quill for reply-to it tries to load the title etc to show you a small preview. it should probably also show a big warning if it gets an auth-related 4xx error)
[fluffy]yeah ticketauth is a very good fit for how Publ works, which is why it was so easy for me to add support to it in Publ. and I really like its overall design.
[fluffy]since in Publ-land, auth tokens are granted based on a user identity, and content filters are based on the user identity. I’m not granting access to a resource directly.
[fluffy]meanwhile, the only bridgy responses I’ve found to private items so far have been likes, rather than replies, but I’m pretty sure I’ve gotten replies in the past. Nothing substantive, at least.
GWG[fluffy]: Maybe after a few other things I'll work on the infrastructure to support private posts, I only built consuming other people's private stuff
[fluffy]My original prototype for this stuff was a bunch of godawful hacks I’d put into my Movable Type templates back in the day, where it integrated iwth my phpBB forum to let people log in through that and I could add folks to a “private posts” group. it was awful to maintain, but it gave me a good idea of how things could work.