#[fluffy]like I was thinking, source would be http://example.com/foo and target would be /bar, and so the thing pushes a webmention to /bar’s endpoint with those params, and then the endpoint would go “oh target is relative so we’ll treat the destination as http://example.com/bar”
#KartikPrabhuI don't think any POST request does that
#[fluffy]I’m not talking about the POST request though
#[fluffy]like, the endpoint sees a source URL and a target URL, and it does urljoin(source,target) to determine the canonical URL
#[fluffy]I realize that webmentions are POST requests
#[fluffy]I’m not talking about the protocol for sending the webmention
#[fluffy]I’m talking about how to handle the URLs once received
#KartikPrabhuif the URL is not well-formed then ignore it
#[fluffy]Like when you do an <a href> that’s doing a GET request and the GET is bsaed on a fully-realized URL
#[fluffy]like when you do <a href=“foo”>blah</a> when you click on the “blah” you’re not doing a GET to “foo” you’re doing it to the fully resolved URL that was formed by urljoining the source page’s URL with “foo”
#KartikPrabhustill not sure what the use case is. The webmention sender can resolve the relative target URL and then send the webmention
#[fluffy]the use case is having a webmention to a relative URL while providing an exact string match to what the target is specified as
#[fluffy]so like if you do <a href=“/foo/bar” class=“u-in-reply-to”>, the endpoint validates the target parameter by exact match to the <a>’s href attribute
#[fluffy]like the two uses cases for this are 1) webmentions to pages on the same domain (without having to expand them out fully) and 2) webmentions using protocol-relative URIs like //example.com/blah
#[fluffy]so like, there’s the webmention spec, and then there’s what webmention endpoints are allowed to do
#[fluffy]they are supposed to validate the URLs based on the spec but they can *handle* the URLs with relative resolution and chasing redirects and stuff (like consolidating webmention targets and stuff). I don’t believe webmention.io does, it sounds like Kevin’s thingus does some of it
#[fluffy]or I guess the simple test is webmention.rocks’ case doing a relative link back to itself, if you’re just testing a standalone webmention sender (like pushl) as opposed to a publishing system (like a wordpress plugin)
#[fluffy]sorry I’m rambling and up way past my bedtime
#aaronpkSo the flip side to this argument is maybe if you link to your own site you should link to the fully resolved url because that's more likely to actually show up right for people when viewing the post in their readers
#aaronpkbecause it takes extra work for a reader to go to the trouble of resolving every relative url in the html content of an atom or rss or microformats content
#[fluffy]I would think it’s up to the reader to resolve relative links in a feed like that? I know FeedOnFeeds does that (because a lot of feeds broke without it), and meanwhile Publ is friendly and lets you provide fully-resolved links for feeds.
#[fluffy]I mean it could provide fully-resolved links on any template
#[fluffy]but out of a misplaced sense of purity it defaults to relative links where possible
malaclyps[m], [Rose], sfoster, jeremych_, romainbouyeDisco, [jgmac1106], [grantcodes], gRegorLove, vika_nezrimaya, dino and GelvenDiscord[m] joined the channel
#jgmac1106i have an old iframe from a site that went dark and now a domain forward it is making my enitre site redriect to a squatter page…not sure how I can go and in fix
#LoqiA story is a singular (one per profile) time stream collection post, that consists of ephemeral photo and video posts that are shown in sequence one at a time and disappear from the collection 24 hours after being added https://indieweb.org/story
#jgmac1106nvm would putiit there but that definition is basically the definion of Instagram story not stories in the Zeega sense
#jgmac1106wasn’t linear, just a way to layer openly licensed html elements <video><.audio><img><a><span> to make non linear multimodal remixes and stories, nto sure it needs its own page
#jgmac1106I think our definition of story just needs to move past Instagram’s may take a crack at it, but have a work deadline first
#Loqi[RimBune] websites is easy. you wanna make a checkbox? <input type="checkbox">. bam. you wanna make the text pink? css color: pink;. all it takes. you wanna put the thing in the middle of the box vertically? no you don't
#[grantcodes]Ahh, well I would move my feeds to the atom suite but the mf2 feed is so much richer in indie readers
[fluffy] joined the channel
#[snarfed]grantcodes could you elaborate? i know that's the assumption here but i rarely hear specific examples. in-reply-to/repost-of URLs are one. got any others?
#[snarfed]aaronpk, right, they're still missing-to-users in readers, at least indie readers, which is what counts
#[snarfed]whoa photos?! those are definitely in *-atom. videos too
#[grantcodes]Well by that I mean everything is there, but it's all in the content, not in a photo property. If that is to do with the microsub server feed parsing or not I don't know
#[snarfed]it is, since granary is just giving your mf2 reader html
#[snarfed]i can just add mf2 html output to *-atom
#aaronpkok yeah looking at the atom from instagram-atom, i can't make this look right in a reader
#[snarfed]but yeah i'd like to keep enumerating these to see where the actual problems are. so far it's not that data is missing, but that indie readers handle mf2 different (better?) than atom
#[snarfed]aww sad. xml pain? or stuff embedded in CDATA content that's not worth munging?
#aaronpkthe "content" in atom needs to be only the text content of the instagram post, and the photos/videos would need to be "attachments" or whatever atom does
#[snarfed]sigh yeah but then non-indie readers often don't show those nicely
#[snarfed](the bulk of my users use non-indie readers. you all are the vocal minority 😎)
#aaronpkthere is 0 way you can convince me to extract these photos/videos out of the HTML content as is right now lol, i've been down that road before and it was not fun
#[snarfed]oh that's fine, i'm not trying to convince you
#[snarfed]i'll add mf2 output to *-atom. that part is easy. i just dread the rebranding and redesigning
#aaronpkan HTML mf2 output from this service would definitely be the easiest all around i think
#[fluffy]yeah it was hard for me to write `---` on this iPad :)
#[fluffy]In Publ I differentiate between things where order matters and where it doesn’t. If it doesn’t, it’s just, each instance gets its own line. So like `Tag: foo` `Tag: bar` `Tag: baz` for tags.
#aaronpkalso reply context, which ends up being a whole h-entry
#[fluffy]For that kind of stuff I just have a list of microformat stuff to add to the entry.
#aaronpki would store it as JSON but it's harder to write by hand, and I do open up these files and hand edit occasionally
#[fluffy]Like if I’m replying to someone else’s entry I’ll have `In-Reply-To: http://example.com/bad-take` as a header, which will generate `<a class="u-in-reply-to" href="http://example.com/bad-take"></a>` in the entry’s hcard section.
#[fluffy]basically I don’t see the point to doing everything as semantic data structures with specific HTML-generating stuff when the end result is, to users, the same as having it formatted in markdown 🙂
#[jgmac1106]fluffy you should check out the rules and folders built into inoreader pro a lot of UI inspiration for your vision I think
#aaronpk[fluffy]: because the end result is not the same once you want to show it in other places like readers
#[fluffy]I guess I kind of capitulated to the whole “lowest common denominator” thing because I have my feeds set up to support what exists now, rather than what I’d like to see.
#[tantek]missed the Atom argument and is perhaps ok with that
#[fluffy]I had to add soooo much workaround logic in FeedOnFeeds to prevent a badly-formed <link rel=“self”> from borking a subscription.
#[fluffy]like now FoF will follow a rel=“self” link and, if it’s different than the feed URL, will try loading it as a feed, and only if that’s valid will it update the subscription URI.
#[fluffy]a couple of prominent webcomics feeds were breaking the naive “just update to the rel=“self” href without checking” behavior
#[fluffy]oh hey! Questionable Content’s is finally fixed! I was only complaining to the artist for, like, a year about that
#[jgmac1106]fluffy pardon neophyteness but a serial view in a social reader or site be neat. Like drop a url in and be able to jump to 6 out of 7, nav back and forth
#LoqiA collection is a type of post that explicitly lists and/or embeds multiple other posts chosen by the author https://indieweb.org/collection
#[jgmac1106]But if you used a p-category inside a data class, parsed a collection this way, couldn't fluffy build views that allow you to jump issues, see them descending and ascending?
#[fluffy]yeah Jamey is why I support RFC5005 in my feeds, because I want readers to be able to do a full content index of my entire site.
#[fluffy]and I don’t understand the question, jgmac
#[fluffy]Jamey and I both have similar “babies” in terms of what we want out of a reader especially for long-form/serial content.
#[fluffy]The UX for reading comics from feeds is different than reading, say, news updates or blog posts or whatever
#[fluffy]the “show unread only, oldest-to-newest” view happens to work well for me and my reading habits but being able to specify some things as being serial and some things being in-the-now would be good
#[fluffy]like maybe sort order could be based on time-since-posting for serial content and time-before-now for non-serial content.
#[fluffy]like I don’t want to have separate readers for reading all my subscriptions, but I also don’t want to have to worry about which things are oldest-first and which things are newest-first (or at least “it’d be nice to see newer thins first”)
#[fluffy]also inoreader is pretty nice. I’d prefer something self-hostable though.
[asuh] joined the channel
#[asuh]Self-hostable Inoreader would be great, I agree.
#[fluffy]I mean for now I’m pretty happy with FoF as a reader. And I could theoretically add micropub to it. Microsub would be a bit harder but I also don’t see as much of a use case when it’s, like, already an integrated reader and subscriber.
#[fluffy]I think adding Micropub to FoF and making a Micropub endpoint for Publ would get me everything I feel missing from my own indieweb experience.
#[fluffy]But I could also get the Micropub-equivalent stuff by actually getting Reblob working 🙂
[Jamey_Sharp] joined the channel
#[Jamey_Sharp]I can't contribute much to the conversation right now but strong endorse for serial readers 👍
#[fluffy]I also want to add RFC5005 to FoF although that means also trying to square the circle of how FoF is pretty aggressive at trying to purge older content too. Which is configurable at least and RFC5005 backfilling could just be another toggle.
#[fluffy]like I often fiddle with older stuff in my archive, particularly deleting entries which have not aged well 😛
#[Jamey_Sharp]If you're reasonably confident you can get old posts again from the origin server, because it provides metadata per section 2 or 4 of RFC5005, then you can keep just a minimum amount of information for all old posts, with enough to remember which feed document you probably have to re-fetch if the user wants to see it again.
#[fluffy]doing that would require a massive rearchitecture of FoF, probably 🙂
#[fluffy]FoF’s data model is fairly simplistic. It also doesn’t lend itself well to things like feeds with conditionally-visible entries (like multiple subscribers to feeds with private content that differs between the subscribers)
BenLubar_ joined the channel
#[fluffy]not that it has any support for the stuff to make the private content work either, at least in how Publ implements it
#[fluffy]feeds with “magic links” are supported and maybe I should add a thing to express those in Publ. I’m just especially concerned about privacy leakage in that form though.
#[fluffy]it’s very easy to imagine a situation where someone tries sharing a public entry from a “magic link” feed in a way that also exposes said magic link.
#[Jamey_Sharp]Also if you're deleting entries from your archives I'm not certain you've done what you need to for RFC5005 yet 😅
#[fluffy]I use tombstones to mark the dead entries 😛
#[Jamey_Sharp]Ah, okay, if you have the tombstones and you put them in the newest feed when you add them, then you're set, as far as standards conformance goes.
#[fluffy]I put them in the appropriate view for the archive feed.
#[Jamey_Sharp]I think that's probably what I mean.
#[fluffy]I don’t put them in the rel=“current” view unless they happen to also be within that time window.
#[fluffy]oh I bet when I changed a thing in Publ I broke the view.deleted thing
#[grantcodes]Fixed that author issue fluffy. It was automagically caching stuff based on the author url, so it was working in feeds where authors have their own urls.
#[fluffy]I saw. Thanks! And glad it was a straightforward fix.
[schmarty] joined the channel
#[jgmac1106]Never mind Fluffy I forgot you are talking about consuming past serial content rather than thinking about collectiona for future display
#[jgmac1106]I was just brainstorming way serialization could work based on how people are fooling around with collections
#[snarfed]bridgy instagram is back, scraping with a test account's session cookie, from google cloud IPs
#[snarfed]reluctant to keep it this way for long, but here we are
#Loqi[Aaron Parecki] I've reached the point that a day trip to the Bay Area from Portland is effectively the same as a "long commute to work". I'm also pretty sure this is still shorter than some peoples' commutes within the Bay Area. https://aaronparecki.com/2019/08/28/59/photo.jpg
#[snarfed]^ that thread basically describes indieweb
#@mrejfoxThere is no reason that your personal website couldn't ping my personal website when you post an awesome new photo, and yet the entirety of some artists' work is held in an Instagram profile- these are choices we have made as developers, creators, and as a society (twitter.com/_/status/1167181611340849155)
#jgmac1106always hesitant now to @ mention a blue check that doesn’t follow me…think it takes many (2) unsolicted @ mentions to trigger the harrassment bots
[KevinMarks] joined the channel
#[KevinMarks]Feedparser has a few thousand test cases
#[KevinMarks]Mastodon atom feeds have images as enclosures I think