fluffySo, to me it seems like the big problem is an impedance mismatch between ActivityPub (which is, at least from my POV, mostly just "here's a big blob of text") and my heterogenous long-form content website, which has structure like title, intro, body text, etc.
fluffyWhat I'd like out of this is the ability to simply specify what things map to what in the ActivityPub item stream, ideally with the ability to provide optional stuff to pave over some of the bigger UX issues.
fluffyLike, CW text is probably the wrong mental model for it, but like, APub doesn't seem particularly suited to long-form text in general, and CW text is just the generic approach taken by a bunch of Mastodon instances.
fluffyIncidentally, as a result of this experiment I am adding actual summary functionality to Publ, and this has been the impetus for me to finally fix the microformats in my templates, which was clearly wrong on my end.
fluffyalso, neat, mastodon doesn't seem to be able to talk to publ.beesbuzz.biz via fed.brid.gy because it's not SSL-enabled (because I'm running it on Heroku free tier)
snarfedheh, let me walk that back a bit, those examples are just granary's test suite for the mappings i made up. they're not necessarily "official" in any way. just pretty mature and battle tested over time
fluffyYeah I'm not expecting them to be official, but sticking to someone else's convention is better than making up my own from whole cloth as I'd been doing before.
fluffyI wasn't really familiar with IndieWeb at all before I started implementing Publ, and I just had my own notions of how to modernize web publishing based on how things were in 2003. :)
fluffyAnd I'm very grateful that there's already an ecosystem of people who have been working on the hard parts of it, and that it just happened to work well with the model I was going with.
fluffylike going into it I knew I'd be integrating with PubSubHubBub because I didn't know it had changed names, and I wasn't expecting Webmention to be a thing *at all* but I'm glad it is and it's learned a lot of lessons from pingback.
fluffyAnd developing Pushl as a Publ companion has been great since it also works with a lot of other stuff. Because I love things being modular and UNIXy.
fluffyAnyway. I'm glad to be able to support ActivityPub but not having to implement that support myself, since when I started work on Publ the most frequent question I got was "are you going to support ActivityPub?" which I'm doing sort of begrudgingly because I still think there's a pretty big impedance mismatch for what I'm trying to do.
fluffyyeah, and I'm also not a fan of how following works in ActivityPub; having to be aware of everyone following, and sending out a notification, and dealing with failures when they disappear. WebSub is great because it's an optional extension, and it specifies how to handle failures, and how to deal with backfilling during a client outage.
fluffyThat's fair. But I still like supporting the use case of people who don't have the know-how/ability/access to getting their own domain and hosting thereof.
fluffyI guess it's nice that you don't have to declare the <link rel> on every page where it might need to be looked up, too. But on the other hand it feels a *lot* like favicon.ico to me :P
LoqiIt looks like we don't have a page for "bad with the favicon rule" yet. Would you like to create it? (Or just say "bad with the favicon rule is ____", a sentence describing the term)
[kevinmarks]I'm a big fan of you writing out your thoughts on this stuff on your blog in longform, fluffy. I am realising how much I have lost since I gave into the tweet length approach
Loqi[kevinmarks]: [tantek] left you a message 5 days, 4 hours ago: the marginalia page needs your help. It still shows / uses the ## syntax of Fragmentions - could you update it to the latest best practice for Fragmentions (and update any Marginalia implementation documentation accordingly — assuming your implementations support the single # syntax) https://indieweb.org/marginalia Thanks!
[jgmac1106], EmreSokullu, ingoogni and [Rose] joined the channel
LoqiHow does it work?
Login with IndieAuth on this site to create an account
Open settings in Indigenous app and look for 'Push notifications'
Use the API token on your account page to send a push notification manually
Services integrating with thi...
swentelGWG, well, I use the pushy to register the device, the site stores the token. Anyone can send a push notifiation then, and I forward it to pushy
swentelGWG, e.g. when a webmention comes in, send a notification. That's what the Drupal plugin allows you to configure now (since webmentions are send to the internal microsub channel)
doubleloopSo was thinking that it might be better to use Micropub to create follow posts (https://indieweb.org/follow), and then have my server do the Microsub API call
doubleloopWhat got me thinking about it was I have an additional and (possibly?) niche use-case to simply subscribing to a feed, in that I like to use Microsub to follow individuals on Twitter, going via granary
doubleloopGiven the extra logic for that (if it's a Twitter user, do this extra stuff, which also involves my twitter access token for granary...) it feels like it makes sense to have that on the server
doubleloopAnd then it'd be nice to tie that in to doing a follow post, so it could all be triggered from any Micropub client that allows me to do a follow post
snarfed, swentel, EmreSokullu, [eddie] and EmreSoku_ joined the channel
snarfedi'd also recommend managing your twitter following in a twitter list, and then subscribing to that list via granary just once, instead of each user's granary feed separately
doubleloopsnarfed: I do kind of like managing the follows in Microsub, partly so I can put differently themed Twitter accounts in different channels, and also partly a bit philosophically/stubbornly I want to try to avoid using Twitter as my list management tool.. (I mention it a little in my post)
snarfedin the past, when people have done this and subscribed to enough individual users, eg hundreds or more, we've eventually asked them to switch to a list, because fetching a feed per followee doesn't scale and gets too heavy
doubleloopRe: the Microsub server, I guess the same issue would hold regardless of the feed type? e.g. if I ever subscribed to >100s individual feeds, I should start thinking about either paying someone for hosting me (if that's an option), or hosting myself
doubleloopAnd I guess really if I have a philosophical issue with Twitter it'd be more useful to address it at source and help persuade the people I want to follow that they should move to indieweb..
doubleloopIs export/import currently a thing with Microsub? Say I build up lots of subscriptions in Aperture, but then decide I'd like to move to Yarns. Would it be a case of scripting it?
[tantek]In particular lots TODO in https://htmlparser.info/microsyntaxes - I was particularly looking forward to his time and date microsyntaxes summary only to find ... it's missing (not even a TODO about it!) so I imagine there's still lots of work for this be a "ready to read and use book"
mblaneyone other thought: Microsub doesn't really need export/import. A Microsub client could let you specify a second server, and then use the API to read your follow list from one server and subscribe on the other.