#fluffyI'm also assuming that this nickname is registered and I'm going to get kicked relatively shortly.
#fluffyAnyway! Back to the conversation from github.
#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.
cweiske joined the channel
#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.
#snarfedAS2 definitely has those fields and structure, eg content, summary, and name
#jalcineIIRC CW is a hijacking/unintended use of the subject field in AS2
#fluffyOkay, interesting. What does Mastodon do with them? Or is that a gigantic It Depends™?
#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.
#fluffyok cool, that'll be a great resource for me to at least see what other people expect out of the fields.
#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)
#fluffyI could just move that site to my own dang server, but I like having at least one thing hosted on heroku for the sake of ensuring that works.
#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.
#snarfedheh yup, lots of us came up with our own half baked versions of indieweb before we found it
#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.
#jalcinelol like that's been the biggest thing me trying to make a desktop client for AS2 stuff
#jalcineI have to make so many requests _just_ to get a profile
#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.
#fluffy(thankfully fed.brid.gy handles that stuff for me!)
#fluffyand I mean it's not like I'm implementing my own WebSub hub either, but superfeedr was way easier to integrate ;)
#fluffynot to mention adding WebSub support to Feed-On-Feeds.
#cweiskere well-known: Its big plus is that it does not put a HTML parser requirement into software
#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.
ingoogni and snarfed joined the channel
#fluffyWhich is probably quixotic on my part because nearly everything gives everyone their own personal subdomain at this point.
#fluffyhuh, that's quite a lot more diversity than I was aware of.
#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
#cweiskewell, you can define your own favicon url via a <link>
#fluffyWell yeah, but my point is that favicon.ico is to me the canonical example of an ad-hoc standard that's taken way too long to get rid of.
#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)
#fluffyMostly that browsers look it up and generate a lot of 404 traffic unnecessarily, and that it's stuck to a proprietary content-type.
#fluffyI mean I know browsers will happily accept icons in other formats other than Windows application icons, but still.
#fluffyI have a lot of curmudgeonly opinions, apparently :)
snarfed, jonnybarnes, [fluffy], [Rose] and [tantek] joined the channel
[Zegnat], gRegorLove, [Rose], mblaney1, jonnybarnes, jeremych_, [kevinmarks] and swentel joined the channel
#[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
#Loqiswentel: GWG left you a message 5 days, 17 hours ago: Explain this indiepush thing to me?
#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...
#GWGIt is subscribing to topics from one, excuse me?
#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
#swentelZegnat, the official build yes. You're free to to compile the app yourself with a custom endpoint of course :)
#swentelwell, you can send any type of push notification atm, I don't really care there :)
#Zegnatwould run his entire life based on notifications, but doesn’t really like existing solutions for it
#swentelto be fair, this feature I guess is more for non technical people, especially if cms plugins integrate with it.
#GWGswentel: What are you imagining WordPress would integrate it to do?
#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)
#doubleloopBut then I thought I'd probably want to do it via mobile too
#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
#doubleloopWith that though I'm not sure how I'd choose which channel to send the follow to
#doubleloopAny thoughts about it? The only client I've seen for following a feed so far is in Indigenous, that acts directly against the Microsub API
#snarfedhmm, tying follow/unfollow posts to microsub subscriptions definitely is interesting
ingoogni and [cleverdevil] joined the channel
#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
#doubleloopSo I wanted to make something that would just take a Twitter handle and do the finagling behind the scenes for me
[kenbauer] joined the channel
#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
snarfed joined the channel
#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
#Loqidoubleloop has 1 karma in this channel over the last year (4 in all channels)
#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
#snarfedlighter in a few ways and easier to add/remove individual people
#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
#doubleloopIn that case I'd be totally happy to use Twitter lists
#snarfedthanks! and sorry for making you need twitter more
#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
#doubleloopsnarfed: thanks for making me need it less, with all the various awesome tools!
#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]KartikPrabhu interesting link. The author has been involved in WHATWG / HTML spec work for years so they're a good source.
#[tantek]I clicked around and found lots of TODO - it's definitely a WIP
#[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"
#KartikPrabhuyeah it is WIP, but that is one advantage of publishing a wook
#KartikPrabhuwook = web book (I think adactio made that word up)
#[tantek]I see where that is going and I'm not going to fall for that Ackbar.
mblaney and EmreSokullu joined the channel
#mblaneyinteresting Microsub discussion, doubleloop I have tried to do something similar with my twitter feed.
#mblaneyso it's like twitter lists but I can manage it within my own reader
#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.