#microformats 2020-07-06

2020-07-06 UTC
[chrisaldrich], [tw2113], rawtext and beko joined the channel; rawtext left the channel
#
jacky does anyone have thoughts on https://github.com/snarfed/bridgy/issues/952 for providing content warnings?
#
Loqi [jk-na] #952 enable content warnings?
#
jacky namely https://v2.jacky.wtf/post/d7187860-6d7a-4cc9-9465-792daaab2b30 and https://github.com/snarfed/bridgy/issues/952#issuecomment-648390894
#
Loqi [Jacky Alciné] Hm, advice is interesting. I want this to signify that it’s a tag of sorts; something that can be indexed (for a negative filter search of sorts). This is making me want to lean into something like this format:<span class="p-content-category p-cat...
[Rob_Nugen] and [dave] joined the channel
#
jacky does jf2 not have a representation for alt text in photo (or in media in general?)
#
jacky looking at https://www.w3.org/TR/jf2, I don't see an immediate mention
#
Loqi [Benjamin Roberts] JF2 Post Serialization Format
#
jacky but maybe I have to read more
#
jacky hm so https://www.w3.org/TR/jf2/#multiple-urls hints at this
#
jacky via multiple URLs and allowing for properties there
#
jacky but what if I have only one photo?
#
jacky I know jf2 optimizes away lists so I'm guessing a singular photo would just have a key whose value is an object
justache, [Nishant_Mendir], [tw2113], [dave], [chrisaldrich], reidab and [KevinMarks] joined the channel
#
[KevinMarks] This is the tension in jf2 as it ends up being more complicated to have nested things
[tantek] joined the channel
#
[tantek] jacky, yeah I don't think jf2 was ever updated to handle img src and alt the way mf2 and mf2json was
#
jacky I'm torn now and I think I might just lean to use mf2+json
#
[tantek] that's the more stable/maintained thing anywa
#
[tantek] even if it's a bit more code to pull stuff out
#
[tantek] at least you know you're getting the "complete" version of the data
[fluffy] joined the channel
#
jacky yeah exactly
#
jacky and I'm already storing everything as mf2+json
[calumryan] joined the channel
#
JK_na > namely https://v2.jacky.wtf/post/d7187860-6d7a-4cc9-9465-792daaab2b30 and https://github.com/snarfed/bridgy/issues/952#issuecomment-648390894
#
JK_na As someone who currently only pushes website updates to the fediverse I think that this would be a great addition and as mentioned in the ticket, I agree with your preference to align with categories in some manner.
#
Loqi [Jacky Alciné] Hm, advice is interesting. I want this to signify that it’s a tag of sorts; something that can be indexed (for a negative filter search of sorts). This is making me want to lean into something like this format:<span class="p-content-category p-cat...
#
[tantek] jacky, I suppose I don't understand the difference between p-content-category and what p-category already does. p-category already applies to the content as a whole
#
[KevinMarks] is it more like p-warning-category ?
#
[KevinMarks] because you're explicitly categorising to warn about it
#
JK_na [KevinMarks]: yes, the idea being that there is a unique identifier that can be passed to brid.gy (or other apps) which can be mapped to mastodon's subject field and collapse the content behind the contents of the p-warning-category (or alternate name if more suitable). Aligning it with categories reflects the sentiments behind the initial proposal from activitypub devs rather than how it was implemented by mastodon.
#
[KevinMarks] in effect it's <details><summary> but more complicated
#
[tantek] still seems like a plain text p-content-warning should be sufficient for that. if there is one, display it instead of content or summary
#
[tantek] categories are categories. if you want to tag things inside the p-content-warning, go ahead and do so with p-category on the individual "tags" as you wish.
#
[tantek] if a UI wants to filter out a specific tag or warn on a specific tag, it should do that regardless of whether or not there is any explicit content-warning from the publisher
#
[tantek] no need to make all that dependent on each other
#
jacky true I thought of it as a progressive way to do it (like it's all tags but if it comes across a particular tag - in the event that it's a collection of posts) it'd be something to make more filterable for clients
#
jacky but using the p-content-warning to map against it _actually_ would work for me tbh
KartikPrabhu joined the channel
#
jacky this is good!
KartikPrabhu joined the channel
#
[tantek] and keep the two pieces simpler and separable!
KartikPrabhu joined the channel
#
[KevinMarks] the mastodon api calls it entry.spoiler_text
#
[tantek] spoilers are only one use-case
#
[tantek] only one form of warning
#
JK_na i'm just reading through the microformats wiki to ascertain the correct process for proposing p-content-warning as a new property , should I raise an issue on github to gain "rough consensus"?
#
jacky JK_na: yes (I think that's the process)
#
[tantek] this is specifically for h-entry, see the process there: http://microformats.org/wiki/h-entry
#
Loqi [Tantek Çelik] h-entry is a simple, open format for episodic or datestamped content on the web. h-entry is often used with content intended to be syndicated, e.g. blog posts. h-entry is one of several open microformat standards suitable for embedding data in HTML. ...
#
JK_na initial proposal issue raised: https://github.com/microformats/h-entry/issues/19 I understand it'll need 'out in the wild' usage before being considered for draft
#
Loqi [jk-na] #19 p-content-warning proposal
#
[tantek] JK_na++ thank you for filing the issue! That's a good summary
#
Loqi JK_na has 1 karma over the last year
[jgmac1106], KartikPrabhu, [KevinMarks], kevinCH, [manton], [tantek], [Jose_Leiva], [Ana_Rodrigues], Loqi, [fluffy] and [tonz] joined the channel
#
jacky niceeee
jgmac1106, [schmarty], KartikPrabhu, [fluffy], [tantek], [snarfed], [chrisaldrich], [KevinMarks] and gRegorLove joined the channel