#dev 2026-10-28
2026-10-28 UTC
bterry, troojg, JoshuaMorris, grufwub, Saige_Leah, [burgeonlab], barnaby, oodani and JadedBlueEyes15 joined the channel
# 
WinnerWind what are all the types of p-rsvp? from the microformats wiki they say "yes", "no", "maybe", "interested". is that *all* the types?
barnaby, [tantek] and dustinm` joined the channel
# 
[aciccarello] WinnerWind, those are the ones listed on the microformats wiki https://microformats.org/wiki/h-entry#Core_Properties
# WinnerWind are there more types that are in use?
# [aciccarello] I don't think so. The brainstorming page mentions a theoretical "invited" status but that wouldn't be something you post https://microformats.org/wiki/rsvp-brainstorming
# WinnerWind got it!
# WinnerWind not sure if this is devtalk suitable for another channel but in your opinion are these RSVP icons visible enough? https://x0.at/jxMbx8S4n6.png
# [aciccarello] It might need some better context to make it clear that they are RSVPs
# 
[burgeonlab] WinnerWind: You mean the ABCD are the different p-rsvp responses? I would agree with Anthony that it needs a bit more context like maybe event title, event datetime to show it is some sort of response to an event.
oxtyped joined the channel
# WinnerWind [aciccarello]: there is an icon that displays behind all the icons (like the likes there) in the actual site build
# WinnerWind [burgeonlab]: they are p-rsvp responses ^_^. the event response thing would probably be in the main body, if i understand what you are talking about
rMdes-bnc and barnaby joined the channel
# [burgeonlab] WinnerWind: right... I guess that's just a demo to show all four statuses? Usually there'll be only one?
# WinnerWind [burgeonlab]: yeah its just a demo to show all the four statuses, if there's multiple people that RSVP "YES" to an event then they all get a green badge along their icon
# [burgeonlab] Ohhh.... it's to show RSVP of others to an event you're hosting....
# 
[tantek] this is some very nerdy early web history / discussion stuff that's finally been restored (with notable events) https://www.w3.org/blog/2026/historical-www-talk-archives-made-complete/ back when most of the web was what we would call indieweb today
# WinnerWind [burgeonlab]: yeah! my bad if i did not make that clear
# 
[capjamesg] [tantek]++ wow!!
# burgeonlab seeing history preserved/recovered is always happy news.
barnaby joined the channel
# WinnerWind [tantek]: wohoo!
# WinnerWind this is great news!
[artlung], aaronpk[d], capjamesg, suki, ancarda, rossabaker and ramsey joined the channel
# WinnerWind burgeonlab: do you send webmentions automatically?
[Murray] joined the channel
# 
chokito76 Hi everyone, how’s it going? I’m still getting familiar with the concepts here, hehehe... Is there anyone here with experience implementing the Micropub protocol?
barnaby joined the channel
# chokito76 Both, in fact, starting with the client. I've been working on a publishing tool for some time that can currently create kind of "entire" posts (HTML/CSS/JS/media) that can be published both as "stand alone" sites or as part of posts (like embedded on wordpress posts). This got me wondering whether it might be possible to send content created using this protocol to live websites. The tool also includes its own post mana
# [tantek] chokito76 check out the implementations listed at https://indieweb.org/Micropub/Clients and https://indieweb.org/Micropub/Servers
# chokito76 Oh, I hadn't seen these lists yet. I'll check them out. Thanks a lot!
# [aciccarello] chokito76 what language are planning on using. There might be a library that could help.
# chokito76 the tool is created on haxe, but exported on javascript, so I can use javascript libraries as well. here, a small site published on the "stand alone" version of it
# chokito76 https://tilbuci.com.br/pwa/
# chokito76 This page shows where I intend to implement the client. Notice that in the middle of the post, there is an area that says "click/tap here to start." It acts as a piece of media embedded within a post/page.
barnaby and deathcomestotime joined the channel
