#@voxpelli↩️ Cool, I’m very much behind on the development within this space for the last 4-5 years, so this is great info!
So I guess I could do some things to my WebMention endpoint to push it to have a wider support as well? (twitter.com/_/status/1356920408268824576)
#jeremycherfasSome of it looks tangentially interesting to me.
#sknebelyeah, fosdem often has interestng things. although I personally tend to go through the list afterwards, not much one for watching synchronously
paul3 joined the channel
#jeremycherfasEspecially if things have been prerecorded in the first place.
#@kevinmarks@balajis Turning products into protocols does make sense, but entangling them with cryptocurrency doesn't do that. A platform is easier to use than a product. A crypto entangled protocol is harder. You're adding friction, not removing it. (twitter.com/_/status/1356930147207831552)
Saphire and [schmarty] joined the channel
#[schmarty]KevinMarks: I lol'd at "carrots of crypto". I feel his tweets are coming from some macroeconomic view where the only players are state-level actors.
#[KevinMarks]he's a VC so he really like financializing things
beehiveth and gxt joined the channel; ShadowKyogre left the channel
#Loqi[w3c] webappsec-change-password-url: A Well-Known URL for Changing Passwords
#aaronpkwow iOS safari has already implemented it?
#SaphireOoh. Is there a list of .well-known things?
#Saphireaaronpk: I think it is one of more widely supported things due to various password managers rallying behind it?
#aaronpkit's unusual for Apple to be the first one to implement things in safari :)
#aaronpktries to think of a place he has with a password dialog to try this out
#ZegnatIESG/IANA I guess keep a list of .well-known things, as far as any official registration of them is concerned. But I would not have a link at hand
ShadowKyogre joined the channel
#aaronpkhas managed to successfully not have passwords for most sites he runs thanks to OAuth/IndieAuth
#ZegnatI have always found these IANA registries a little magic. People add it to an RFC with a little IANA section, and then … submissions to age old mailing lists I guess?
#sknebelyes, it says right at the top who to contact :D
#ZegnatTo actually list authorization_endpoint as a link relation, that is, and not just have it as an IANA Considerations section in the IndieAuth spec
#Loqi[Zegnat] #17 Link relations in HTTP Link header conflict with RFC 5988.
#ZegnatAh, right, forgetting about my own issues :P
#aaronpki do think my latest comment there might be the best way to handle it
ShadowKyogre left the channel
#aaronpkespecially since it means fewer things to register as link relations
ShadowKyogre joined the channel; ShadowKyogre left the channel
#Zegnataaronpk: any idea how far along pushed auth extension is? Saw they issues a new draft just yesterday. Is there any worth in tryin to do those two simultanious as part of a breaking-change modernisation, or no?
#aaronpki don't think there will be a last call any time soon on that
#aaronpkalso ugh i hate all this namespacing "urn:ietf:params:oauth:request_uri:..."
#ZegnatWhat is that params supposed to mean? urn is easy, the protocol. Then ietf for the standards body. But surely you could follow that up with oauth immediately?
#Zegnataaronpk: I guess forcing it to follow an URL/URI/URN standard means it can be more easily expanded to other things besides https and urn in the future without clashing with the random strings people have been picking?
#ZegnatI kinda liked the tag URIs for naming. Rather than having to register a namespace with IANA the namespace is instead your email address or domain name combined with a date that you own that domain at.
[tantek] joined the channel
#[tantek]Zegnat, the link registry for HTML rel values is specified by the HTML spec, which links to the microformats rel-registry and it's been that way for ages. The IANA one is only for HTTP headers
#[tantek]so don't be "surprised" when things are missing from it
#ZegnatNot sure if they were added to the wiki registry?
#ZegnatThe aforementioned relation name issue is also specifically re HTTP Link headers. HTML rel values are more lax in their definition of allowed values, it turned out
#[tantek]you or anyone with edit permissions can! no need to email someone and go through some ancient process
#aaronpkyeah the indieauth ones have been on the microformats wiki for ages
#SaphireOh, curious, is there any kind of thing that adds HTTP header with a link to a "rich" content page, when looking at direct links to files (photos, etc)
#aaronpkwhat's interesting to me is as far as i can tell, HTTP clients have no trouble with the technically disallowed underscore in header names
#Zegnatmicropub, webmention, and indieauth (except redirect_uri) are all on the wiki. microsub is not.
#aaronpkwhich suggests that maybe the http spec should be updated to reflect reality
#SaphireI guess HTTP spec is "minimum must support"?
#ZegnatHTTP clients I think have no issue because none of them validate (or do anything, actually) with the contents of a Link header. It is a valid HTTP header.
#ZegnatIt is just not a valid value for a Link header per the spec on Link relations
#ZegnatAnd who bothers to implement that spec to the tee?
#ZegnatYep. That is the Web Linking spec, not the HTTP spec. So I am guessing HTTP clients do not care ;)
#aaronpkalso "Note that extension relation types are REQUIRED to be absolute URIs..."
#aaronpksure, my point is clearly the specs do not reflect the reality of most implementations, so something is wrong with the specs
#Zegnatyes. But in this case "extension relation types" = unregistered types.
#@XabCorinti#100DaysOfCode
R3|D4
Still struggling with comments.
I have decided that I'll display the old ones in plain html (they are from 2013-2017, a Staticman and previous disqus bunch) so the discussion will always be part of the post
For the future, I think Webmentions is the way (twitter.com/_/status/1356995865773297670)
#ZegnatWas that not why webmention originally used a URL as rel, aaronpk?
#[tantek]I think because he had been exposed to some RDFisms and eventually we worked together to simplify it to a keyword because it reality that's all you need
#SaphireMaybe try to compile a nice annotated master list of all the currently used microformats/etc. And then look over it to see what to implement..
#Saphireaaronpk: oh yeah, that page ^^' Lack a blog so that might be a good thing to try and make in first place, hm.
#[tantek]Saphire, best place to start with what to implement is to ask yourself what do you want to use your site to do? And if you don't know and want ideas, you can start with: How can I use my site instead of social media?
#[tantek]interestingly enough we used to answer this question on our "Getting Started" page, that is, it was more implementer-centric, but we've subsequently edited for folks who want to primarily setup and use the IndieWeb rather than implement
#[tantek]And then yes, IndieMark is a way to implement simpler steps first, along the paths that you want for your own site
#SaphireHonestly, want to mess around with all the microformats and such. But lack content to use it with. Hm..
#[KevinMarks]Indiewebify.me will nudge you along too
#SaphireWell, it suggests to check posts markup. Posts I need to make in first place? Hm..
[arush], [benatwork], ShadowKyogre, DanC and KartikPrabhu joined the channel; ShadowKyogre left the channel
[calumryan], KartikPrabhu, ShadowKyogre, miklb_, lahacker and jamietanna joined the channel; ShadowKyogre left the channel
#jamietannahey aaronpk - is https://php.microformats.io/ working for you? seems to be timing out for me, wasn't sure if it was related to the bump to PHP 7.4 you mentioned?
#jackybecause then that's a subtle incentive for me to finish working on the Rust parser
[benatwork] and [tantek] joined the channel
#[tantek]re: "expecting indiewebify.me to be a "wizard" of sorts" <-- perhaps file an issue to turn IndieWebify.me into a Micropub client? Then it could optionally post a "badge" for you to your site when you achieve a certain level of support 🙂
#[tantek]Saphire, do you use any "social media" or any other content silos?
#[tantek]well that's a great place to start! pick one (maybe where you only post "notes") and start building the ability to do so on your own site instead!
#jackyso on my walk with Stella, I was thinking about my site
#jackyand how I wanted to test how different post types could render
#jackyI was wondering if a tool could send a request to post content of a particular type and then conditionally delete it when needed
#jackythe thing about it that I was thinking about the most was having it pull the list of known post types from the wiki and doing deeper introspection on what kind of markup to use
#jacky(the latter half is a bit much and would probably read from #How_to_Markup)
#jackybut I can imagine that being handy for people who want to not only test their site but also use the wiki as a source of test cases!
gRegorLove and [arush] joined the channel
#[tantek]jacky, does your system allow for mutability of "post types" based on the presence or absence of some number of properties?