#GWGI've discovered an interesting problem. I test my site periodically in an RSS reader. The one I'm using, when there is no explicit title, such as a note, displays the GUID as the title. Wondering what if anything I should do.
[snarfed] joined the channel
#[snarfed]you can put the full content in the title, and truncate and ellipsize it
#tomlarkworthyAwesome my relmeaith server can get a github access_token. I don;t actually want these potentially PII things in my system, so I want to exchange a 3rd party token for one that just has the username/URL data in it
#aaronpkyou shouldn't need to store the github access token, but you do need it in order to verify that the right user logged in. then you can fetch their info from github and discard the access token
#tomlarkworthyseems like have a ton of design liberties with how I make the token, so I am going to create my tokens using the Firebase CustomToken scheme
#tomlarkworthyI would jsut send the github token off?
shoesNsocks joined the channel
#tomlarkworthyor more accurately, a service accepting relme, uses the links to know that github is an acceptable form of identification for a person identified as a URL
#aaronpkso the user types in their website, you find a github URL, your goal is to confirm that the person at the computer actually controls that github profile
#tomlarkworthyso one the service has to bring its own Oauth client for github, and accepts that authentication
#aaronpkin order to do that you need an oauth client registered at github, you do the oauth flow, then you find out who logged in, which is done by sending the access token to their "userinfo" endpoint to return their github username
#tomlarkworthyyeah, so at the end of its dance it has an access_token which is can use on the /me endpoint for Github to confirm the newly authed profile is indeed the person at the beginning
#jboveQuestion about microformats and birth places; the h-card has the dt-bday property - how do I set the birth place and birth country and distinguish it from h-adr?
#aaronpkh-adr is the vocabulary used to describe an address, it still needs to be set as the value of some property
#aaronpke.g the "location" property might be an h-adr
btrem joined the channel
#btremI recently learned that colons are acceptable in urls. So I could use e.g. `/foo/2021/02/22-10:37`
#btremBut there are probably caveats. Anyone want to point one (or more) out?
#jackywouldn't want to put them in the anchor part since that's used to parse timestamps
#btrem"anchor part"? You mean a fragment url? Like `foo#10:37`?
#jboveThanks aaronpk - if a birth date is an h-event, then that would solve my current problem where I need to keep the date and the location together. Is that acceptable?
#aaronpki believe the use case was described in that conversation
#aaronpki don't mean there has to be an active consumer
#btremMaybe I forgot what it was, or maybe I don't grok "consumer."
#aaronpkthe use case for the u-translation-of was to be able to write a translation of something, add that markup, send a webmention, and provide the webmention receiver with more information about the link other than a generic link
#btremI see, but that spec refers specifically to media url fragments. In the case of an html fragment, it doesn't (seem to?) apply.
[tantek] joined the channel
#[tantek]I think vCard4 may have added something about birth location. Though the longer answer is, research & document existing publishing examples and existing formats for representing that information (for adding a new property or format)
#btremIn any case, if timestamps are a convention in urls, should I regard that as a good reason to use `10:37` as part of an html page url? Or a reason to avoid it?
#LoqiURL design is the practice of deliberately designing URLs, in particular, permalinks, typically for a better UX for everyone who creates, reads, and shares content https://indieweb.org/URL_design
#btremI've read that, but apparently not well enough to recall the section on time in urls. Which indicate that colons in time are ok (and preferable to no seperaters, even!).
#btremI'm probably going to omit seconds. That way I can regret it for the one time two months from now when I create two brief items in the same minute of a day. ;-)
#aaronpkthis is why i stopped using the timestamp as the unique identifier in my URLs
#aaronpki didn't want to guarantee that my automated systems wouldn't step on each other and create two posts within the same second
#aaronpkwhich might sound far fetched until you realize that if you schedule two cron jobs for the top of the hour, they will likely post at the same time
#aaronpkor if you are importing posts from another system that doesn't have second-level precision, you have to pick some default artificial value for seconds
#btremI don't create posts via cron jobs, so not a worry for me.
#btremThing is there isn't a convenient way to create arbitrary urls in 11ty, e.g., `2021/04/02-1` 2021/04/02-2`, etc.
#btremIf there were, I'd most likely go with that.
#btremI imagine that's common to ssg programs that store data in text files.
#aaronpki don't see why that's an inherent limitation
#aaronpkmy site stores posts in flat files very similar to jekyll and it works fine
#btremHmm, I wonder if that is possible in 11ty. I haven't come across anything like that in my searches (and I have been searching for a few weeks now). I gotta think on that.
#sknebelhm, for flat files there is the argument that not all operating systems like colons in file names, if that ever is a concern regarding moving the files around
#btremI don't know much about it, but do you store data in frontmatter?
#sknebeland you need to take care with relative links to files in your HTML
#btremsknebel: in fact, osx seems to not like them. I can't create a file with a colon in the name. But for reasons that escape me, 11ty writes files and substitutes a solidus for the colon, but then serves them up correctly. It's actually kinda weird, and I haven't poked around to see what exactly is happening.
#btremsknebel: what would be the problem with relative links?
#aaronpkoh yeah macos is weird about colons, it turns them into some other char on the filesystem but then shows you a colon anyway
#sknebelwindows bans them entirely, on NTFS they are used to access alternate data streams
#sknebeli.e. I wouldn't be surprised if something got confused by i.e. <a href="lorem-ipsum-10:37"> and thought it was supposed to access host lorem-impsum-10 on port 37 :D
#sknebel(I *think* HTML spec is clear on it being a relative url even without the clarification, so if you want to help find broken tools :D)
#btremI almost never write urls that way. Intrasite urls almost always start with a solidus `/foo/lorem-10:37`.
#[tantek]depends if you want to be relative to the domain or the document base
#btremsknebel: I could. The site is just my personal site, nothing critical.
#btrem[tantek]: I'm (nearly?) always relative to the domain. (I'm actually not sure what you mean by "document base.")
#[KevinMarks]: was the directory separator in Mac OS pre X, so it needed special casing for compatibility
#[tantek]btrem it's that part of the URL before the document (file) name
#[tantek]typically. it can also be altered with the <base> element
#btrem[tantek]: ok, that's what I guessed. So yeah, my relative urls are relative to the url in (almost?) all cases.
#btrem[KevinMarks]: I have 11ty write files like `26-17:56`, and what I see in my directory is `26-17/56`. But I can then open that in Firefox and the url shows `2021/01/26-17:56`. I don't know what voodoo is going on, but it seems to work.
#btremOk, there's some voodoo magic happening with the colons. 11ty write a file `02-17:56`. In the os, the file appears as `02-17/56`. When I upload it to a Linux server, it's `02-17:56`. So the solidus substitution is perhaps only a display thing?
#btrem...and only in the gui finder window. In a terminal, the colon is, in fact, there.
#btremSo yeah, apparently just a display feature of osx finder.
#aaronpkit's very weird that i rename a file in Finder to include `/`
#jackyis making a list of things he'd like to implement and has implemented thus far
[KevinMarks] joined the channel
#[KevinMarks]When we were building OS X compatibility with older macos was key, and Carbon used : everywhere, the apps concatenated paths with strings etc so the finder preserved that
KartikPrabhu, [fluffy] and [tantek] joined the channel