#dev 2021-03-17
2021-03-17 UTC
[KevinMarks], alex11, NinjaTrappeur, [scojjac], [tw2113_Slack_] and anon_CWEJRrIS joined the channel
# 
@foobartel ↩️ Lost my page files section after re-adding webmentions, they got eaten by the indent monster. (twitter.com/_/status/1372044210262536193)
treora, GWG, Zenyattus, jjuran and GWG_ joined the channel
# 
doosboox jacky: how's the rewrite going? :D What tools were you using before and what are you going for now?
shoesNsocks1, [schmarty] and jeremych_ joined the channel
# 
@tomlarkworthy ↩️ Do you have an opinion on WebID vs. IndieAuth? (twitter.com/_/status/1372188315311570944)
# 
@kidehen ↩️ Yes.
They aren't the same thing :)
#WebID is a globally unique identifier that scales to the #Web.
IndieAuth is an authentication protocol. (twitter.com/_/status/1372191244454133760)
# 
petermolnar the web? pff, are you living in the 90s? the only thing that scales to the web these days is blochain on k8s on public cloud.
# petermolnar (oh. sorry. not -chat. nevermind :) )
[KevinMarks] joined the channel
# 
@kevinmarks @kidehen @tomlarkworthy IndieAuth uses domains, which are globally unique identifiers that demonstrably scale to the web. WebID is a url with fragment on the end for arbitrary reasons, and a fragile way of connecting certificates (twitter.com/_/status/1372194071628935174)
# @kevinmarks ↩️ IndieAuth uses domains, which are globally unique identifiers that demonstrably scale to the web.
WebID is a url with fragment on the end for arbitrary reasons, and a fragile way of connecting certificates (twitter.com/_/status/1372194071628935174)
# 
[schmarty] i will agree with the "they are different" part of that opinion 😂
# @tomlarkworthy ↩️ Yeah I am thinking IndieAuth my be the perfect authentication mechanism for user hosted @observablehq notebooks. Just checking I have not missed any other ideas. OpenID is too heavy for individuals (twitter.com/_/status/1372198087154937860)
nertzy, Zenyattus, nertzy_ and alex11 joined the channel
# 
jacky doosboox: my current stack is at https://git.jacky.wtf/indieweb/koype - mostly a Elixir/Phoenix setup
# 
@jackyalcine ↩️ WebID has to use certificates - you’d be fighting for provider support. It also ignores other clients like phones, CLI tools, etc. IndieAuth’s an extension of OAuth2 - used everywhere. You used it to post this tweet on your phone or sync your e-mail to… https://v2.jacky.wtf/post/bf50f47a-afb5-4824-a60f-8597e96fb330 (twitter.com/_/status/1372215385408352265)
bhavin192 joined the channel
# @jackyalcine ↩️ If you want something you can give to people tomorrow and keep using as long as the Web is around, use IndieAuth. If you want to yak-shave and use it with three people, WebID’s ideal for that! (https://v2.jacky.wtf/post/32cfbd45-384a-4d8f-bad7-a79a4dfdbd2a) (twitter.com/_/status/1372217256575389705)
# 
[KevinMarks] WebID got the tea
# [KevinMarks] ObservableHQ is pretty neat. I need to play with it more, but a self-hosted version would be very cool
# [KevinMarks] it's like a hybrid of Jupyter and CodePen - you can share code snippets that run in the page https://observablehq.com/@mourner/simple-web-map
# @kidehen ↩️ No.
A #WebID is a #Hyperlink that identifies an Agent. That's it.
It has nothing to do with #TLS or any other protocol.
Which is why WebID vs IndieAuth isn't an Apples vs Apples comparison.
#Identity #NetID (twitter.com/_/status/1372221277902143501)
# [KevinMarks] WebID is like ogres, it has layers
# [KevinMarks] HTTPRange-14 << https://twitter.com/_/status/1372221277902143501
# 
Loqi ok, I added "https://twitter.com/_/status/1372221277902143501" to the "See Also" section of /HTTPRange-14 https://indieweb.org/wiki/index.php?diff=74906&oldid=24929
# @jackyalcine ↩️ Have you read over the IndieAuth spec? I did read the WebID spec some time ago, back when people were toying to expose it in Mastodon and it never went through because it’s not friendly to portability (people change names, identities [think trans… https://v2.jacky.wtf/post/a66997c8-13ac-428e-b239-7a4fbd05a33d (twitter.com/_/status/1372223958444089344)
bhavin192_, [Aaron_Klemm] and alex11 joined the channel
# jacky TIL about https://hjson.github.io/
tomlarkworthy joined the channel
# tomlarkworthy wow how is this weaved with Twitter!
# tomlarkworthy ok I have a meeting now but this looks very cool
# [KevinMarks] We have bots that look for indieweb keywords
nickodd, [Rose], marinin[t], bhavin192_, [schmarty], [KevinMarks], [tantek] and tomlarkworthy joined the channel; nickodd left the channel
# tomlarkworthy cool, this is awesome. Erm, anyway, I am extending ObservableHQ to the backend with a dynamic serverless environment
# tomlarkworthy https://observablehq.com/@endpointservices/serverless-cells
# tomlarkworthy a constant annoyance is its hard to do auth on that platform
# tomlarkworthy every user has their own <username>.static.usercontent.... subdomain
# tomlarkworthy but also the whole environment supports forking notebooks like github
# tomlarkworthy and its ideally aimed at community based code improvement
# tomlarkworthy but its hard to build a service on it, because a code fork and the origin changes
# tomlarkworthy so I made a federated login system that kinda works in user space https://observablehq.com/@endpointservices/login
mxd joined the channel
# tomlarkworthy but ultimately it ends up using 3rd party open ID providers
# tomlarkworthy its got problems coz I still have to figure out which user owns which domain which requires a second step
# tomlarkworthy anyway, I kind of think IndieAuth would be perfect
# tomlarkworthy users could self host their own identity in a notebook
# tomlarkworthy I can even provide auth endpoints using https://observablehq.com/@endpointservices/serverless-cells
# tomlarkworthy then users can log into 3rd party services using their notebook URL
# tomlarkworthy 3rd party being other notebooks on the platform
# tomlarkworthy though I am only jsut exposed to indie. atuh so I am not entirely sure how it would work
# mxd When a post is syndicated to twitter, Should users like/respond to the tweet or to the original post on the website (comment system) via webactions?
# mxd Assuming both options are possible
# tomlarkworthy one problem with user notebooks is they are loaded into an iframe with Javascript, so if IndieAuth assumes static HTML I might have problems though its all workable around.
[snarfed] joined the channel
# mxd jacky: 👍 so it shall be. i will try to make likes created on my site 'webmention compliant'
# 
Zegnat "if IndieAuth assumes static HTML I might have problems" - IndieAuth requires that there is some way to find the authorization endpoint from the URL the user writes in the login form. Either through an HTTP Link header or an HTML link element. (https://indieauth.spec.indieweb.org/#discovery-by-clients)
marinin[t] joined the channel
# tomlarkworthy ok, I will figure something out. Gonna start messing around tomorrow so I will probably have clearer questions soon.
alex11 joined the channel
# [KevinMarks] there is an assumption that pages are curlable in a lot of the indieweb building blocks, especially if we're looking for rel links or microformats. Your serverless pages look like they work with fetch so is that equivalent?
# 
@ripixelcodes Testing webmentions, ignore me please! https://www.ripixel.co.uk/thoughts/2020-08-16_Stop-Blaming-Slack (twitter.com/_/status/1372319276435116033)
[scojjac], jeremycherfas and samwilson joined the channel