#social 2018-07-02
2018-07-02 UTC
bblfish joined the channel
# 
aaronpk dansup: how are you using https://github.com/99designs/http-signatures-guzzlehttp? It doesn't look like it supports RSA signatures
kaniini joined the channel
# 
nightpool[m] icon
# nightpool[m] and `image` is the background header
# aaronpk here's my actor object, does this look right? https://aaronparecki.com/2018/07/01/17/
# nightpool[m] mmmmm i think just putting the url into the search box will re-fetch it
# nightpool[m] aaronpk: that object looks legit to me
# nightpool[m] try using the webfinger addresses
# nightpool[m] ah
# nightpool[m] then I'd suggest trying the opposite, putting https://aaronparecki.com/aaronpk into the search bar
# nightpool[m] i can never remember which one works so I just use both haha
# nightpool[m] are you actually serving the json there?
# nightpool[m] at the id location?
# nightpool[m] 503 does sound like an error
# nightpool[m] fwiw this is what I see:
# nightpool[m] uploaded an image: image.png (124KB) <http://localhost:8008/_matrix/media/v1/download/cybre.space/dUSMkJdPKPaZVNeiABscHrCZ>
# nightpool[m] when using the webfinger address
# nightpool[m] ??
# nightpool[m] weird.
# nightpool[m] i just used matrix's built in thing
# nightpool[m] the bridge must be fucked
# nightpool[m] it does
# nightpool[m] i dunno i'll take a look at the logs in the morning
# nightpool[m] seems to be working now though using webfinger
# nightpool[m] cool!
# nightpool[m] no idea why the direct uri resolution is borked but ¯_(ツ)_/¯
# nightpool[m] (i didn't get a notification because it didn't Mention me, fyi)
# nightpool[m] I see the reply now if I go to your profile or the post in question though
# nightpool[m] aaronpk: the important thing is the tags array
# nightpool[m] one sec there's a good section in the as2 spec about this
# nightpool[m] the href is cosmetic and can basically be whatever you want
# nightpool[m] the tags array is what's machine readable
# nightpool[m] it's not required
# nightpool[m] because anyone can use whatever microsyntax they want
# nightpool[m] yeah
# nightpool[m] it would be a little weird for mastodon users to see a notification without getting tagged but if it's in reply to a post it's probably not that bad
# nightpool[m] gets a little more complicated when you're trying to notify all the people who are interested in a thread—then you'd want to have it in the content, so users can remove others who shouldn't be notified.
# nightpool[m] Up To You Though
# nightpool[m] if it becomes a ux problem that people are Mentioning others without including them in the contet that's on us to resolve probably
bblfish, xmpp-social, fr33domlover, vasilakisfil, timbl, bblfish_, tantek, jankusanagi_, JanKusanagi, jankusanagi__ and saranix joined the channel
# nightpool[m] you can view it in the web interface
# nightpool[m] but not from the static page
# nightpool[m] just put the url into the search bar :P
# nightpool[m] what instance was the post on?
# nightpool[m] likes only get sent to the instance they were created on
# nightpool[m] was the post on mastodon.xyz?
# nightpool[m] then that's expected behavior
JanKusanagi joined the channel
# nightpool[m] woo!
# nightpool[m] for the like? no
# 
jaywink[m] doesn't mastodon forward likes to other instances that have the original post?
# nightpool[m] no
# nightpool[m] we forward replies
# jaywink[m] but replies are sent?
# nightpool[m] but forwarding likes never seemed very useful.
# aaronpk would appreciate if someone takes a look at this https://github.com/tootsuite/mastodon/issues/7926
# nightpool[m] aaronpk: where's the current mf spec?
# nightpool[m] trying to understand what p-name should be used for
# nightpool[m] right
# nightpool[m] yeah that's basically how we represent it in AP
# nightpool[m] the spoiler is the "summary" and the content is the rest of the post
# nightpool[m] the problem is that if we move p-name to the spoiler item, then there's no p-name if there's no spoiler
# nightpool[m] so i think maybe just dropping it makes the most sense
# nightpool[m] 202 just means it was parsed correctly
# nightpool[m] activities are processed asycn
# nightpool[m] async
# nightpool[m] yeah
# aaronpk so I tried sending a JSON object with type=Accept, actor=my URL, object=https://mastodon.social/a1ae6622-4944-4e7b-8507-50d18e24bef8 which is the value I got for the "id" of the Follow activity
# nightpool[m] ah yeah
# nightpool[m] mastodon is being a little wonky here. it expects you to embed a follow object
# nightpool[m] because it thinks of them as somewhat ephemeral
# nightpool[m] there's no real reason what you did shouldn't work, it's just that we've never really needed to before
# nightpool[m] yeah
# nightpool[m] lol
# aaronpk but i'm confused about this line https://github.com/tootsuite/mastodon/blob/master/app/controllers/concerns/signature_verification.rb#L30 which seems to require exactly 3 properties in the signature line
# nightpool[m] no no
# nightpool[m] that's requiring three things in the rege-
# nightpool[m] yeah
# nightpool[m] dropping signature was a pretty recent change in the httpsig spec haha
# nightpool[m] they made it optional yeah
# nightpool[m] the idea is that the keyid specifies somehow
# nightpool[m] using out-of-band metadata
# nightpool[m] sorry my computer's lagging out a bit :(
# nightpool[m] yeah, we still send it too
# nightpool[m] woo!
# nightpool[m] turns out my computer was probably overheating
# technomancy wow what the heck; they still haven't closed registrations?
# nightpool[m] they close it when stuff is bursty
# technomancy there should be a disclaimer in the signup process that "signing up on this instance means you're agreeing to be part of a load-test of the underlying software"
# nightpool[m] mm. normally it's pretty responsive.
# nightpool[m] i wonder if this is because of the vanityfair article cwebber2 linked
# nightpool[m] i pinged gargron about the timeouts
bblfish joined the channel
# nightpool[m] there's a contentType but it's html by default iirc
# nightpool[m] in mastodon it's always html
# aaronpk how does this look? https://aaronparecki.com/2018/07/02/16/
# nightpool[m] i mean, that all looks right
bblfish joined the channel
# nightpool[m] aaronpk: i'm looking at the mastodon API now, and it looks like all three of those created valid mention records
# nightpool[m] so I have no idea why they're not showing up in notifications
# nightpool[m] maybe refresh? haha
# nightpool[m] ohhh
# nightpool[m] you also have to include them in your 'to' audience.
# nightpool[m] this is probably to prevent things from breaking the other way around, when you mention someone and didn't meant to include them
# nightpool[m] we can probably fix that for public/unlisted visibility posts.........
# nightpool[m] yeah it doesn't fetch remote followers or anything
# nightpool[m] especially since you don't have an advertised followers collection :P
# nightpool[m] well, it uses the count at least :P
# nightpool[m] it's not particularly hard
# nightpool[m] you can optimize it by de-duplicating the sharedInbox routes if they exist
# nightpool[m] but otherwise it's just `followers.each
{|f| deliver(activity, f.inbox)}`# nightpool[m] however you conceptualize that in your code
# nightpool[m] mmm
# nightpool[m] it's pretty safe to assume it never changes
# nightpool[m] if you run into an error, you can try re-fetching the actor json
# nightpool[m] theoretically people will also send you Update activities
# nightpool[m] stale in which sense?
# nightpool[m] iirc, mastodon kicks them out after about a month of unsuccessful deliveries
# nightpool[m] one sec there's a bit about this in the ap spec
# nightpool[m] let me see if I can find it
# nightpool[m] the note here: https://www.w3.org/TR/activitypub/#follow-activity-inbox
# nightpool[m] mastodon's current behavior is "stop delivering to inboxes, but don't do anything to the followers collection"
# nightpool[m] which is maybe somewhat sketch, but if you come back online, i think there's a way to get us to start delivering to you again.
# nightpool[m] so we don't want to remove you entirely.
timbl joined the channel
# nightpool[m] bad type maybe?
# nightpool[m] normally resolving the url fixes it
# nightpool[m] don't know why it's not working in your case.
# nightpool[m] should be using the received date in both instances .....
# nightpool[m] sorry, the date the server recieved it
# nightpool[m] er. unless i'm misunderstanding this code, which is possible
# nightpool[m] oh nevermind
# nightpool[m] i'm an idiot
# nightpool[m] yeah if you send a message it will use the published time
# nightpool[m] but the snowflake will be based on the current date
# nightpool[m] I'll take a look
# nightpool[m] it's an old gnu social feature
# nightpool[m] can't remember where the docs are
# nightpool[m] it uses the http://ostatus.org/schema/1.0/subscribe relation in the webfinger response
# nightpool[m] see here: https://cybre.space/.well-known/webfinger?resource=acct:nightpool@cybre.space
# nightpool[m] yeah
# nightpool[m] after substituting in the webfinger uri for the
# nightpool[m] sent a long message: nightpool[m]_2018-07-02_19:31:01.txt <http://localhost:8008/_matrix/media/v1/download/cybre.space/zaUYgJbTQFVurmJCwZYzdNhm>
# nightpool[m] s/for the/in the template/
bblfish, timbl, tantek, cybrematrix, nightpool[m], zauberstuhl[m] and csarven[m] joined the channel
# aaronpk boom now I have the remote subscribe button https://aaronparecki.com/aaronpk
# dansup aaronpk: Wicked!
bblfish joined the channel
bblfish_ joined the channel
# JanKusanagi he's way more loved elsewhere!
bblfish joined the channel
# nightpool[m] aaronpk: hard to diagnose without a traceback. which server is it?
# nightpool[m] aaronpk: in a quick overview i can't see anything specifically that changed from 2.4.0 to 2.4.2 that would impact it.....
# nightpool[m] did you fix the mime type problem?
# nightpool[m] oh, I meant the application/json vs application/activity+json one
# nightpool[m] oh yeah sorry I said something earlier but it might have been while you were away:
# nightpool[m] sent a long message: nightpool[m]_2018-07-02_22:26:41.txt <http://localhost:8008/_matrix/media/v1/download/cybre.space/yArkwwYhsiEOHEzqSWgZTDdt>
# nightpool[m] lol
# nightpool[m] huh
# nightpool[m] i'm just not seeing these messages on the irc side at all
# nightpool[m] that's frustrating
# nightpool aaronpk: i figured it out
# nightpool you're not serving it with the correct mime type
# nightpool you're serving application/json but it needs to be one of application/activity+json or application/ld+json; profile="https://www.w3.org/ns/activitystreams"
# nightpool ^^^ those were the messages
# nightpool[m] yeah
# nightpool[m] `test` test
# nightpool[m] aosdjfoajsdofjasodfjoasjdfaosdjfoajsdofjasodfjoasjdfaosdjfoajsdofjasodfjoasjdfaosdjfoajsdofjasodfjoasjdf profile="https://www.w3.org/ns/activitystreams"
# nightpool[m] hmm. something to figure out another day I guess
# nightpool[m] at least I can fix those uris
# nightpool[m] can you re-fetch your profile on mastodon.social now to fix the avatar?
bblfish joined the channel
# nightpool[m] aaronpk: searching the url, yes
# nightpool[m] weird
# nightpool[m] worked on cybrespace (filled in the new background you had added)
# nightpool[m] oh maybe refresh or something then
# nightpool[m] could be a caching issue
# nightpool[m] (the new sw cache is sometimes brutal)
tantek, bblfish, cybrematrix, jaywink[m], zauberstuhl[m], csarven[m] and nightpool[m] joined the channel
# nightpool[m] ping
# nightpool[m] sent a long message: nightpool[m]_2018-07-02_23:35:36.txt <https://matrix.cybre.space/_matrix/media/v1/download/cybre.space/rpPNPlgAsUBxoYuMJHTXeTJI>
the_frey joined the channel