Untitled attachment

Notices where this attachment appears

1. Embed this notice
   Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Thursday, 02-Oct-2025 22:44:04 JST Haelwenn /элвэн/ :triskell:

   in reply to
   @mi @domi Well technically as I put an XSLT on my feeds, it can work.
   
   https://hacktivis.me/feed.atom
   
   And my blog is also a bit of Xinclude/XSLT underneath, like recent-ish articles are written as Atom entries:
   https://hacktivis.me/git/blog/file/feed.atom.in.html
2. Embed this notice
   pistolero (p@fsebugoutzone.org)'s status on Thursday, 31-Oct-2024 06:24:59 JST pistolero

   in reply to
   @lanodan @NonPlayableClown @toiletpaper
   
   > The `application/ld+json; profile="https://www.w3.org/ns/activitystreams" ` thing?
   > I feel like that's just typical W3C, it doesn't even makes sense.
   
   Turns out every parameter but "q=" has been deprecated as of 9110, but who tries to namespace a content type?
   
   > it should just have been something like XML with stylesheets so it renders somewhat sanely in browsers,
   
   I think it should have just been HTML with proper microdata.
   
   > (For example https://hacktivis.me/feed.atom works like this)
   
   Ah, Seamonkey treats it like any other Atom feed (rendered as browser chrome), Firefox won't touch it.
3. Embed this notice
   Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Wednesday, 30-Oct-2024 13:04:03 JST Haelwenn /элвэн/ :triskell:

   in reply to
   @p @NonPlayableClown @toiletpaper The `application/ld+json; profile="https://www.w3.org/ns/activitystreams" ` thing?
   I feel like that's just typical W3C, it doesn't even makes sense.
   
   But well I'm the kind of bastard who thinks it should just have been something like XML with stylesheets so it renders somewhat sanely in browsers, so URLs no matter what kind of headers you pass still uniquely identity a ressource.
   
   (For example https://hacktivis.me/feed.atom works like this)