2019-10-05 UTC
KartikPrabhu, [schmarty], [aaronpk] and [Lewis_Cowles] joined the channel
# 02:03 [Lewis_Cowles] Wow Tantek you finished working for MS before I was 20
# 02:04 [Lewis_Cowles] tantek++
# 02:04 Loqi tantek has 21 karma in this channel over the last year (118 in all channels)
jfoster, KartikPrabhu, jjuran, eli_oat, MikeShultz5937[m, cweiske, krychu, vinDiscord[m] and [jgmac1106] joined the channel
# 08:46 sebsel reading up on logs... why don't we start all tokens with the string `dont-paste-me-im-your-password`
# 08:49 sebsel `secret-token-abcdef12345` would be a more serious suggestion
# 08:49 sebsel random strings don't mean anything to people, and computers do not care about longer random strings.
# 08:50 sebsel I know that Mollie (the Dutch Stripe / a payment provider API) uses the strings `live_` and `test_` in front of their tokens.
KartikPrabhu joined the channel
# 08:53 Loqi Ok, I'll tell them that when I see them next
KartikPrabhu, [mapkyca], gRegorLove and [grantcodes] joined the channel
KartikPrabhu, djmoch and [schmarty] joined the channel
# 11:36 Loqi Ok, I'll tell them that when I see them next
# 11:43 Zegnat Re: “I think Zegnat cares [about webmention spec not being bound to mf] because he keeps bringing it up for no reason out of the blue” - I mostly care for the issue that we also had with the IndieAuth spec. That is 1 specific implementation of a tech agnostic spec being what everyone thinks the name of the spec means.
[jgmac1106], [Rose], [tmiller], [arush], [mapkyca], [tantek], dougbeal|mb1, [mifga], Zephyr, muan, [aaronpk], gRegorLove, [schmarty] and jfoster joined the channel
# 17:32 jfoster Anyone work with Amplitude to instrument analytics?
[xavierroy], IWSlackGateway, [schmarty], [Rose] and [aaronpk] joined the channel
# 19:22 [Rose] Server updates done in advance of IWC Brighton! Early enough that any problems should become apparent before I get there I hope 😛
KartikPrabhu and [dmitshur] joined the channel
# 20:54 aaronpk I just adapted cleverdevil+eddie's Switch script and i'm pulling in my play history now!
# 20:54 aaronpk haven't turned it into posts on my website yet but i'm storing it in a holding pattern now
# 20:54 aaronpk sebsel: the capability URL spec itself actually does a pretty good job of saying why not to use them
jfoster, [arush] and [jgmac1106] joined the channel
# 21:49 gRegorLove I added 'visibility' to my micropub q=config on my site (easy part), now to update indiebookclub to use it
# 21:58 GWG I still have issues with the visibility property in the query
# 22:14 aaronpk after I was thinking about it after last weekend I think I would also like to remove "private" and use "protected" instead
# 22:19 GWG I use private and protected in the location visibility property I use
AxieDiscord[m], KartikPrabhu and M123897974564Dis joined the channel
# 23:34 aaronpk from the wiki summary of "visibility": "If the visibility is set to private, that means this post should not be accessible unless viewed by an authenticated user. (See audience for more details.)"
# 23:34 aaronpk which implies that "private" isn't actually private, since it may be visible to whoever the audience is
# 23:36 jacky aaronpk: for that reason, I've labelled 'private' as something that's only viewable by the author who created it
# 23:36 Loqi jacky: [jgmac1106] left you a message 2 days, 11 hours ago: the recorder apk coming our sounds amazing. Wonder if there are micropub possibilities
# 23:36 aaronpk yeah that matches more what I would think "private" means
# 23:40 Zegnat In Facebook is it: Public / Friends / Specific Friends / Only Me. That separation makes sense to me, and gets rid of ambiguous words like protected vs private.
# 23:40 jacky right but everyone is considered a "friend"
# 23:40 jacky without that 'friend' concept, what would it be?
# 23:41 [jgmac1106] Jacky not out officially until Pixel 4 but you can sideload the nee recorder APK... Captioning done locally, its stupid sick
# 23:41 jacky "Public" / Vouchable Sites / Explicitly Defined Sites / Me
# 23:41 Zegnat Well, sebsel has something like the friend concept, in that everyone who can login with IndieAuth to his website gets to see his checkins
# 23:41 Zegnat Which I guess is “vouchable” in his case, in the most loose sense of the word
# 23:42 jacky I'm trying to avoid using the word 'friend' tbh
# 23:42 gRegorLove Friends / Specific Friends sound like audience. Could be a separate selection after selecting "protected" visibility
# 23:43 Zegnat Public / Identified / Chosen / Just Me - jacky? In that you know who the identified people are, you just do not care to limit amongst them?
# 23:43 gRegorLove But that's way advanced for me. I don't have audiences yet, certainly not implementing in an mp client anytime soon.
# 23:44 aaronpk yeah I think audience and visibility are good to have separate
# 23:44 Zegnat aaronpk, with “protected” I somehow only think password-protected
# 23:45 gRegorLove That is how most posts are protected these days, like in wordpress.
# 23:45 jacky is also thinking this is also a bit of bias from how protection works
# 23:45 gRegorLove jacky, to clarify, my context was a micropub client, so it's up to the server
# 23:46 Zegnat It probably is a bias, as jacky describes. Seen way to many examples of “protected pages” = “password protected pages” throughout the years.
# 23:46 Zegnat just realised his spelling is going down as the clock approaches 2am
# 23:47 Zegnat I am going to sleep and let the smart people figure out a naming guideline for visibility ;) Have a good one all!
# 23:48 jacky I think I'm going to cling to protected though
# 23:48 jacky and let behavior 'rewrite' the meaning over time
# 23:54 aaronpk I like "protected" because it leaves the question open as to what exactly the protection is