#dev 2019-10-05

2019-10-05 UTC
KartikPrabhu, [schmarty], [aaronpk] and [Lewis_Cowles] joined the channel
#
[Lewis_Cowles]
Wow Tantek you finished working for MS before I was 20
#
[Lewis_Cowles]
tantek++
#
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
#
sebsel
reading up on logs... why don't we start all tokens with the string `dont-paste-me-im-your-password`
#
sebsel
`secret-token-abcdef12345` would be a more serious suggestion
#
sebsel
random strings don't mean anything to people, and computers do not care about longer random strings.
#
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
#
sebsel
!tell aaronpk Do you have something quotable for capability URLs being bad. I see some mentions of secret URLs here: https://indieweb.org/private_posts#Static_Websites and here: https://indieweb.org/unlisted You had strong opinions during IWC AMS :)
#
Loqi
Ok, I'll tell them that when I see them next
KartikPrabhu, [mapkyca], gRegorLove and [grantcodes] joined the channel
#
[grantcodes]
the actual stripe does that too 😛
#
sebsel
lol, it's just a good idea
KartikPrabhu, djmoch and [schmarty] joined the channel
#
jamietanna[m]
!tell aaronpk https://github.com/aaronpk/webmention.io/issues/140 is the issue we spoke about yesterday / at IWC AMS about webmentions rendering weirdly
#
Loqi
Ok, I'll tell them that when I see them next
#
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.
#
GWG
Zegnat, I care too
[jgmac1106], [Rose], [tmiller], [arush], [mapkyca], [tantek], dougbeal|mb1, [mifga], Zephyr, muan, [aaronpk], gRegorLove, [schmarty] and jfoster joined the channel
#
jfoster
Anyone work with Amplitude to instrument analytics?
[xavierroy], IWSlackGateway, [schmarty], [Rose] and [aaronpk] joined the channel
#
[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
#
aaronpk
I just adapted cleverdevil+eddie's Switch script and i'm pulling in my play history now!
#
Loqi
aaronpk: sebsel left you a message 12 hours, 1 minute ago: Do you have something quotable for capability URLs being bad. I see some mentions of secret URLs here: https://indieweb.org/private_posts#Static_Websites and here: https://indieweb.org/unlisted You had strong opinions during IWC AMS :)
#
Loqi
aaronpk: jamietanna[m] left you a message 9 hours, 18 minutes ago: https://github.com/aaronpk/webmention.io/issues/140 is the issue we spoke about yesterday / at IWC AMS about webmentions rendering weirdly
#
aaronpk
haven't turned it into posts on my website yet but i'm storing it in a holding pattern now
#
aaronpk
sebsel: the capability URL spec itself actually does a pretty good job of saying why not to use them
#
aaronpk
why/when
jfoster, [arush] and [jgmac1106] joined the channel
#
gRegorLove
I added 'visibility' to my micropub q=config on my site (easy part), now to update indiebookclub to use it
#
GWG
I still have issues with the visibility property in the query
#
GWG
Namely mentioned in the issue
#
aaronpk
after I was thinking about it after last weekend I think I would also like to remove "private" and use "protected" instead
#
GWG
I use private and protected in the location visibility property I use
AxieDiscord[m], KartikPrabhu and M123897974564Dis joined the channel
#
gRegorLove
Why's that aaronpk?
#
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.)"
#
aaronpk
which implies that "private" isn't actually private, since it may be visible to whoever the audience is
#
jacky
aaronpk: for that reason, I've labelled 'private' as something that's only viewable by the author who created it
#
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
#
jacky
[jgmac1106]: I don't follow re: ^
#
aaronpk
yeah that matches more what I would think "private" means
#
gRegorLove
Sounds good
#
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.
#
jacky
right but everyone is considered a "friend"
#
jacky
without that 'friend' concept, what would it be?
#
[jgmac1106]
Jacky not out officially until Pixel 4 but you can sideload the nee recorder APK... Captioning done locally, its stupid sick
#
jacky
"Public" / Vouchable Sites / Explicitly Defined Sites / Me
#
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
#
Zegnat
Which I guess is “vouchable” in his case, in the most loose sense of the word
#
jacky
right
#
aaronpk
"protected" isn't ambiguous imo
#
jacky
I'm trying to avoid using the word 'friend' tbh
#
gRegorLove
Friends / Specific Friends sound like audience. Could be a separate selection after selecting "protected" visibility
#
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?
#
gRegorLove
But that's way advanced for me. I don't have audiences yet, certainly not implementing in an mp client anytime soon.
#
aaronpk
yeah I think audience and visibility are good to have separate
#
jacky
that works
#
Zegnat
aaronpk, with “protected” I somehow only think password-protected
#
jacky
yeeeah
#
aaronpk
huh I don't get that at all
#
jacky
like how would 'protection' work?
#
gRegorLove
That is how most posts are protected these days, like in wordpress.
#
aaronpk
how it works is up to the site
#
jacky
is also thinking this is also a bit of bias from how protection works
#
aaronpk
that's the point of "protected"
#
gRegorLove
Not my first thought, but I get it.
#
gRegorLove
jacky, to clarify, my context was a micropub client, so it's up to the server
#
Zegnat
It probably is a bias, as jacky describes. Seen way to many examples of “protected pages” = “password protected pages” throughout the years.
#
Zegnat
*too many
#
Zegnat
just realised his spelling is going down as the clock approaches 2am
#
Zegnat
I am going to sleep and let the smart people figure out a naming guideline for visibility ;) Have a good one all!
#
jacky
I think I'm going to cling to protected though
#
jacky
and let behavior 'rewrite' the meaning over time
#
[jgmac1106]
I am going with, "This is an AB post so C you later"
#
aaronpk
I like "protected" because it leaves the question open as to what exactly the protection is