*uncharacteristically at a social event*
them: this has been fun! we have to stay in touch... do you have FACEBOOK???
me, wincing: haha it's funny you ask, i don't, crazy right?
them, aghast and backing away: wow what do you do? Instagram?!
me: well, no... i don't really believe in...
them, disappearing into the darkness as the lights turn off: well how do you even talk to other people???
me, alone and whispering: i... run... my own instance...
who reppin the snouts online at #mff
shout out to my new favorite barkitect friend from the flight into ORD #mff
seriously considering being that guy on the fedi live tooting #mff this year
@tootapp any insight would be helpful before i start tearing the elephant apart
@tootapp yo my push notifications seemingly never worked with toot! and i figured my server was totally busted but it actually seems to be sending notifications to other clients just fine
i finally bothered to do a bit of sleuthing and turned up these backtraces in sidekiq:
https://gist.github.com/friskywhiskers/29728342cc9e598b8ea7cfbdc6c41b9c
i poked through the masto notification implementation to get a sense of what it supposed to be happening, looks like whatever key information is stored causes openssl to bail:
https://github.com/tootsuite/mastodon/blob/master/app/models/web/push_subscription.rb#L68
@TomYote but alas it was not to be, i guess i should probably just ask the developer at this point before i spend the rest of my night reading the push subscription implementation
@TomYote i had tried reinstalling the client before, but i just realized i had a couple of other authorization keys hanging around so i figured i would clean those out and it might get the ol toots a flowin again
treetops and billboards
ithaca, ny