#dev 2022-12-12

2022-12-12 UTC
mlncn, gRegor, oodani, GWG, gRegorLove_, mro, gRegorLove__, [chrisaldrich] and tiim joined the channel; polezaivsani left the channel
#
@mauricerenck The IndieConnector plugin for @getkirby@mastodon.social now talks activityPub which means you can follow sites with this activated feature for example on mastodon. It's not a full implementation, it uses http://brid.gy for that. https://github.com/mauricerenck/indieConnector/blob/main/docs/activitypub.md (twitter.com/_/status/1602252684240748544)
mlncn, [pfefferle], geoffo and mro joined the channel
#
[jacky] do we have a note about the kind of information that might be useful for a Microsub server/service and a Webmention server/service to share?
#
[jacky] for example; if I muted something from my Microsub server, I do see the expectation of _not_ seeing any more content from that source in my Webmention feeds
#
[jacky] (though the Microsub server could filter it out, if the Webmention server is used elsewhere, that wouldn't be possible unless they shared info)
#
aaronpk Ideally it's all just one thing that does both protocols so it's all internal logic
#
aaronpk but for the cases where they are separate components, yeah they should be able to share that somehow
#
@matsuu_zatsu Webmention https://www.w3.org/TR/webmention/ (twitter.com/_/status/1602346896307195906)
#
[jacky] I don't know if we have affordances for that (but it could be something out of spec?)
#
[jacky] I do try to see if it's something we can do within spec b/c I wouldn't want to make it a implementation-specific feature (would that be the case for a sub-spec like AutoAuth or TicketAuth?) but it's easier to tinker on a singular implementation
#
[snarfed]2 right. it's useful to standardize some protocols, but not all of them need to be standardized, esp since that's a very big heavyweight hammer
#
[snarfed]2 well, somewhat big. this community has done good work on experimenting with lighter smaller standards, eg mf2 and algorithms like PTD, authorship, representative h-card, etc
#
[snarfed]2 still though
#
[jacky] yeah I think there's a chance (at least) for some docs (I might write up) about sharing some bits of info to help the experience (but only after I can prove it, heh)
mro joined the channel
#
aaronpk even before getting to the point of writing the protocol, you need to know what data you're actually sharing, so i'd want to see at least internal implementations of that first
#
[snarfed]2 yup, good point, the paving the cowpaths idea implies that people should get this kind of thing working *before* standards, ideally multiple ways, and share and compare how those experiments go
#
aaronpk 👍
#
[snarfed]2 just like I often tell people with Bridgy feature requests that I want it to follow new mf2, silos, etc, not lead them
paulrobertlloyd and gRegorLove__ joined the channel
#
[tantek] snarfed++ experience before standardization, empirical rather than aspirational, descriptive rather than prescriptive. also aaronpk++
#
Loqi aaronpk has 32 karma in this channel over the last year (107 in all channels)
#
Loqi snarfed has 49 karma in this channel over the last year (93 in all channels)
#
gRegor Re: https://chat.indieweb.org/microformats/2022-12-11#t1670800680004400 maybe docs could recommend a u-bridgy-federate property on the link?
#
Loqi [preview] [[tantek]] thanks snarfed. I think the workaround (and maybe longer term solution) for this (and perhaps other Bridgy uses of Webmention as an API) would be to add a special classname to such "bridgy-only" webmention links, similar to the use of Bridgy classnam...
#
gRegor I like the addition of "[preview]" on these btw^
#
[tantek] docs?
#
gRegor sorry, Bridgy Fed's docs for how to post/how to reply
#
gRegor in absence of a u-url in the h-entry, adding u-something on the fed.brid.gy link
#
[tantek] or just always putting a special classname on links intended as Bridgy triggers
#
[snarfed]2 I'd hate to bake a "bridgy" anything into the mf2 parsing spec
#
gRegor Not parsing spec
#
gRegor adding any u-* will prevent the implied u-url parsing
#
gRegor e.g. http://php.microformats.io/?id=20221212181534123
#
[snarfed]2 ohhh ok
#
[snarfed]2 makes much more sense now, thanks, I've added that to the docs, https://fed.brid.gy/docs#how-post
#
gRegor nice!
#
gRegor Also I just actually read the text of that sample note, lol
#
[snarfed]2 😎
gxt__, mro, [benatwork], [schmarty] and mlncn joined the channel
#
[schmarty] hmmm, yes i think i like this. https://werd.io/2022/building-an-open-share-button-for-the-distributed-social-web
#
[tantek] except we did work on this in Web Actions and get prototypes working which somehow missed [benatwork]'s attention or memory?
#
[tantek] what is a webaction
#
Loqi A web action is the interface and user experience of taking a specific discrete action, across the web, from one site to another site or application, like a reply button on a post, which when activated, allows you to reply using your own site instead of the site you are viewing https://indieweb.org/webaction
#
[tantek] [benatwork] can you help work on Web Actions rather than brainstorming something new? We had/have a lot of prototypes working and would appreciate the collaboration!
#
[schmarty] ah bummer, looks like only native apps can be protocol handlers on iOS. 😩
#
[tantek] like we have web+action URL handling as a proposal, rather than being limited to "share" or "social"
#
[jacky] schmarty: that'd be a ripe chance for readers on iOS to make a bridge of sorts!
#
[schmarty] jacky: i agree! i wonder how i can convince someone to pick up active development of iOS indieweb tools. :}
tbbrown and nedzadhrnjica joined the channel