#dev 2024-03-30

2024-03-30 UTC
#
capjamesg [snarfed] How can I get my full articles in my Granary-generated RSS feed?
#
gRegor The full post content should be in e-content
[aciccarello] joined the channel
#
capjamesg gRegor I don’t want to put my full post content on my home page.
#
gRegor At all, or just visually? Maybe could use a <details> element or similar UI to expand the full post
#
capjamesg At all.
#
capjamesg My homepage isn’t optimized for reading long content.
#
gRegor Ah, interesting
#
capjamesg The left sidebar pushes the content view away from the center.
#
capjamesg Is the sidebar were on the right it may feel more readable.
#
capjamesg But I want my bio to be first 🤣
#
gRegor You could have a separate page with full contents. I have that at gregorlove.com/stream
#
capjamesg I want my cake and go eat it too 🤣
#
capjamesg *to
#
capjamesg Ah, that would be perfect!
#
capjamesg gRegor++
#
Loqi gRegor has 29 karma in this channel over the last year (114 in all channels)
#
capjamesg It shall be done!
#
gRegor Mine is a mix of notes, photos, and articles. Basically any post I make that isn't a reply or unlisted.
#
gRegor The atom feed on that stream page is via Granary too
jacky, geoffo, [tw2113], chimo, kleb, [qubyte], [aciccarello], IWSlackGateway, [schmarty], [manton], [tantek], [jeremycherfas], [Jan_Tuomi] and [contact898] joined the channel
#
sknebel what is sqlite?
#
Loqi SQLite is a relational database that stores an entire database in a single file https://indieweb.org/SQLite
#
sknebel sqlite << guide on good settings for server-use: https://kerkour.com/sqlite-for-servers
#
Loqi ok, I added "guide on good settings for server-use: https://kerkour.com/sqlite-for-servers" to the "See Also" section of /SQLite https://indieweb.org/wiki/index.php?diff=94412&oldid=83962
ttybitnik, Guest6, [jeremycherfas], [Paul_Robert_Ll], sp1ff, chimo and geoffo joined the channel
#
capjamesg [snarfed] https://granary.io/url?input=html&output=rss&url=https%3A%2F%2Fjamesg.blog%2Flongform-feed%2F returns a 500 server error.
#
IWDiscord <c​apjamesg>
#
capjamesg https://cdn.discordapp.com/attachments/866577430886350869/1223643915027222538/Screenshot_2024-03-30_at_14.43.48.png?ex=661a9a33&is=66082533&hm=aa7298720627b5a908aa7d57d9c92fb0093e591f6d55fe8fdf5109f1d0491677&
#
capjamesg !mf2 https://jamesg.blog/longform-feed/
#
capjamesg !pin13 https://jamesg.blog/longform-feed/
#
capjamesg pin13 gets it: https://pin13.net/mf2/?url=https%3A%2F%2Fjamesg.blog%2Flongform-feed%2F
[snarfed] joined the channel
#
[snarfed] sorry capjamesg! yeah I saw that
#
capjamesg It may have caught a 403 and cached it?
#
capjamesg Nope, still 5XX.
#
capjamesg You may get intermittent 404s. I'm doing various changes to my site right now.
#
[snarfed] looks like the problem is that the feed's mf2 name property is an h-card object
#
[snarfed] granary shouldn't 500 regardless, of course
#
sknebel thats unusual, but it could/should fallback to the "value", which is a useful string
#
[snarfed] sure
#
capjamesg Oh...
#
capjamesg But...
#
capjamesg The p-name is in the h-card.
#
[snarfed] 🤷
#
[snarfed] oh no the p-name is _on_ the h-card, not in it
#
[snarfed] so it will apply to the enclosing h-feed
#
[snarfed] ie in the HTML <h1 class="h-card p-name" rel="author">James' Coffee Blog</h1> , if you want that p-name to be for the h-card, I think it needs to be on a separate tag inside the h1
#
[snarfed] (or just omit it)
#
[snarfed] (I think)
#
[snarfed] ok, I've fixed the granary bug. thanks for reporting!
#
capjamesg [snarfed]++
#
Loqi [snarfed] has 59 karma in this channel over the last year (108 in all channels)
[KevinMarks] joined the channel
#
[KevinMarks] We need a catch case for that mistake in http://indiewebify.me
[qubyte], dustinm`, geoffo, CRISPR and AramZS joined the channel
#
[qubyte] Folks, I’m considering publishing for websub, but the docs have me puzzled. The docs on the wiki are peppered with references to PuSH (presumably PubSubHubbub since that’s where they try to link to) v0.3 and v0.4, but PuSH is now WebSub. Are these up to date? Did PuSH 0.4 become WebSub (or is WebSub effectively a later version)? Example of what I’m looking at: https://indieweb.org/How_to_publish_and_consume_WebSub
#
[qubyte] Next, it _looks_ from the WebSub spec that the feed type isn’t actually part of the spec, so the feed can be RSS, Atom, JSON, or even just HTML marked up with h-entry. Is that practically true though? Hubs in the wild probably have different support for each (I’m guessing atom most and HTML least). That is, if I’ve understood it right… it might be that hubs are just a sort of event relay which doesn’t try any parsing.
#
[qubyte] Or, am I just overthinking all this and it’s enough to post to superfeedr each time a feed page gets an update?
nertzy, bterry, nertzy_, rrix, jacky, ttybitnik, bret, CRISPR, JadedBlueEyes and gRegor joined the channel
#
gRegor what is websub
#
Loqi WebSub is an open standard (W3C Recommendation) notification-based protocol for web publishing and subscribing to streams and legacy feed files in real time, previously known as PubSubHubbub or PuSH, and briefly PubSub https://indieweb.org/websub
#
gRegor yeah, formerly PuSH
#
gRegor I haven't done anything with it for a while, but I used to send pings for both my homepage, since it has h-feed, and the articles Atom feed
#
gRegor I'm not sure how much change, if any, between PuSH 0.4 and WebSub
#
gRegor If you have a superfeedr account it should show you subscriptions to your feeds. I pinged for both versions of my articles because at least I was subscribed to the h-feed in Monocle for testing
jacky joined the channel