#dev 2023-03-21
2023-03-21 UTC
geoffo joined the channel
# 
[tantek] great thread here about post migration, lots of details that I think are worth perhaps extracting and summarizing in its own page: https://github.com/mastodon/mastodon/issues/12423
# [tantek] This related issue also seemed interesting: https://github.com/mastodon/mastodon/issues/34 β one of the big differences between following someone in a traditional /readers vs following someone on Mastodon or other ActivityPub service.
# 
Loqi π£ follow is a common feature (and often UI button) in silo UIs (like Twitter) that adds updates from that profile (typically a person) to the stream shown in an integrated reader, and sometimes creates a follow post either in the follower's stream ("β¦ followed β¦" or "β¦ is following β¦") thus visible to their followers, and/or in the notifications of the user being followed ("β¦ followed you") https://indieweb.org/follow
# [tantek] follow << Open Issue: when you follow someone on an ActivityPub service (e.g. Mastodon account) it only shows you their subsequent posts (in contrast to traditional [[reader]]s & [[feed file]]s where you immediately see their recent posts) https://github.com/mastodon/mastodon/issues/34
# Loqi ok, I added "Open Issue: when you follow someone on an ActivityPub service (e.g. Mastodon account) it only shows you their subsequent posts (in contrast to traditional [[reader]]s & [[feed file]]s where you immediately see their recent posts) https://github.com/mastodon/mastodon/issues/34" to the "See Also" section of /follow https://indieweb.org/wiki/index.php?diff=87081&oldid=86827
chenghiz_ and geoffo_ joined the channel
# 
[snarfed] ^ afaict that's Mastodon specific. sounds like the AP outbox is how new followers are expected to see someone's past posts. from https://www.w3.org/TR/activitypub/#x1-overview: "You can GET from someone's outbox to see what messages they've posted (or at least the ones you're authorized to see)."
# [snarfed] looks like outbox is mentioned briefly in that issue, https://github.com/mastodon/mastodon/issues/34#issuecomment-624841885
# Loqi [preview] [yakryder] It seems there's a good higher level outline referenced and described by @gammaPi above on what would be wanted for this feature.
One question:
If I am understanding this issue and the last word by @dansup on https://github.com/pixelfed/pixelfed/...
geoffo joined the channel
# 
@geekplux_cn ι΄δΊε δ½εε¦ζε
΄θΆ£οΌhttps://geekplux.com/posts/webmention εδΊη―ζε
³ http://Webmention.io η (twitter.com/_/status/1638029021530267650)
IWSlackGateway and [tantek] joined the channel
IWSlackGateway and [tantek] joined the channel
# Loqi It looks like we don't have a page for "RSS outbox" yet. Would you like to create it? (Or just say "RSS outbox is ____", a sentence describing the term)
[snarfed] joined the channel
geoffo, chenghiz_, [benatwork], lagash and [dave] joined the channel
# [tantek] Seems worthy of broader consideration (how do we avoid similar thundering herd problems) https://github.com/mastodon/mastodon/issues/23662
geoffo, [schmarty] and [aciccarello] joined the channel
# 
[aciccarello] What similar thundering heard problem does the IndieWeb have?
# [aciccarello] AP/Mastodon's chatty server propagation seems somewhat unique.
lagash joined the channel
# [aciccarello] I'll add that I agree being good web citizens is important so worth watching that issue
# [tantek] aciccarello, the "thundering herd" effect has been a problem for any push-based system. E.g. Atom+PuSH(WebSub). sites used to also go down when feed readers all polled their feeds at the same time. That (and analytics) drove the creation of feed proxies like Feedburner, to take the load off the original publisher.
gRegor and [KevinMarks] joined the channel
# 
[KevinMarks] That's not wholly new - tee slashdot effect was that, and orange site can as well
# [KevinMarks] Older version
yousef joined the channel
# 
[schmarty] ooh. aaronpk's advanced oauth course mentioned http signatures with the reminder that they're not yet a published IETF RFC. looks like it's closer as of 2023-02-20 though? https://datatracker.ietf.org/doc/draft-ietf-httpbis-message-signatures/16/
lagash joined the channel
[jacky] joined the channel
# Loqi It looks like we don't have a page for "Pusher" yet. Would you like to create it? (Or just say "Pusher is ____", a sentence describing the term)
gRegor joined the channel
[benatwork] and [jjdelc] joined the channel
# [jjdelc] hello, is https://indieauth.com/auth still the endpoint to POST to perform an indiauth login?
# [tantek] nope. "indieauth.com" is not mentioned anywhere in the IndieAuth spec: https://indieauth.spec.indieweb.org/
# prologic It's just a test client right?
# [tantek] it may be used for that thought I believe it is being phased out in preference of https://indielogin.com/
# [jjdelc] I had a website that used indieauth to login, and it's not working anymore. I am debugging and I was making q POST request to `https://indieauth.com/auth` from which it obtained an argument I used to then proceed with the login
# [jjdelc] That same POST request is no longer returning the previous promise, so I can't login anymore. I found `indielogin.com` but it needs client registration it seems, so I can't plug that into my site to login (at least today)
# 
gRegor As far as I know, indieauth.com (the service) should still work, though is being phased out, yes. https://indieauth.com/developers should still work?
# [jjdelc] I got a 200 , but the body is empty
# [jjdelc] Ah, I see now the response is JSON, it is not text format anymore! I was parsing it as a querystring