Posts by fristi@subcon.pub
(DIR) Post #9vhVhu4JrFvQAWMlc0 by fristi@subcon.pub
2020-06-03T08:42:31.430833Z
0 likes, 0 repeats
@absturztaube honk honk are you reading this
(DIR) Post #9vhVhuVGF5TZW4yHbc by fristi@subcon.pub
2020-06-03T08:43:29.087586Z
0 likes, 0 repeats
@absturztaube this is the old pleroma instance talking :blobcat3c:
(DIR) Post #9vhVhupT1xdgWkQQ6K by fristi@subcon.pub
2020-06-03T08:44:20.187985Z
0 likes, 0 repeats
@absturztaube oh god all of my follows and followers refreshed or something and the notifs got spammed
(DIR) Post #9vhVhvS6iIY0SaVHKT by fristi@subcon.pub
2020-06-03T08:45:54.317935Z
0 likes, 0 repeats
@absturztaube yes, I just saw a new follow notif from you.
(DIR) Post #9vhVhvrHCigFieHNYm by fristi@subcon.pub
2020-06-03T08:46:10.969615Z
0 likes, 0 repeats
@absturztaube did you also get a new follow notif from me?
(DIR) Post #9vhVhxiUIMq3TyBO8e by fristi@subcon.pub
2020-06-03T08:48:19.226037Z
1 likes, 0 repeats
@absturztaube then I guess reverting back to the pleroma instance kinda "unfucks" everything again. I'll have to test a bit more but I guess there's a good chance I can properly revert everything back to normal on the subcon.pub domain :blobfox_w_:
(DIR) Post #9vhVi3IpWfsco8Dyym by fristi@subcon.pub
2020-06-03T08:49:25.112337Z
1 likes, 0 repeats
@absturztaube although I presume the @fristikun handle is now the one that would be fucked.
(DIR) Post #9vhVktkvTevk4EiuCu by fristi@subcon.pub
2020-06-03T08:43:05.978564Z
0 likes, 0 repeats
oh god fuck
(DIR) Post #9vhVuegwLCDqF4VlUO by fristi@subcon.pub
2020-06-03T08:45:33.796898Z
0 likes, 0 repeats
@absturztaube ok so refollowing works (and I saw your refollow as well)
(DIR) Post #9vhVz0d2ilXBRAlSts by fristi@subcon.pub
2020-06-03T08:53:13.550477Z
0 likes, 0 repeats
@absturztaube I guess there is an issue communicating to udongein.xyz though, maybe it's because I actually did manage to properly federate to there from the misskey instance.
(DIR) Post #9vhW44w28bIYF0445w by fristi@subcon.pub
2020-06-03T08:54:08.738262Z
0 likes, 0 repeats
@absturztaube hm, it's as I've suspected, that user is completely bork on udongein.xyz.
(DIR) Post #9vhWHVziqICdvfCGzg by fristi@subcon.pub
2020-06-03T08:56:33.444833Z
0 likes, 0 repeats
Test Test
(DIR) Post #9vhXoY6s6AqS03rB9U by fristi@subcon.pub
2020-06-03T09:13:44.051404Z
0 likes, 0 repeats
@NaiJi iiiiiiiiiii :akko_weary:
(DIR) Post #9vha5r6Qw77xjk22Ii by fristi@subcon.pub
2020-06-03T09:39:16.652345Z
1 likes, 0 repeats
@absturztaube git püll
(DIR) Post #9vhaCWWxoykLxccYUa by fristi@subcon.pub
2020-06-03T09:40:26.759676Z
1 likes, 0 repeats
@absturztaube so it seems I'm better off just starting new on a new hostname since most instances won't accept messages from this user anymore :blobfoxmelt2:
(DIR) Post #9vhaVJIjEUaAQpv8Xw by fristi@subcon.pub
2020-06-03T09:43:52.034323Z
1 likes, 0 repeats
@lucy @absturztaube @_p nah, in this case it's a technical problem caused by me migrating to a misskey instance on the same domain, with a user that had exactly the same handle. It's a known problem.Now I migrated back to my old pleroma instance, and it seems I'm only able to federate properly with those instances that refused the misskey user. But those that did I now can't federate with.
(DIR) Post #9vhaXc4qOXRbFBWZG4 by fristi@subcon.pub
2020-06-03T09:44:18.149140Z
1 likes, 0 repeats
@lucy @_p @absturztaube for instance this account can't federate with udongein.xyz anymore.
(DIR) Post #9vhaa5Cb4zYW9XKQ5I by fristi@subcon.pub
2020-06-03T09:44:44.998906Z
0 likes, 0 repeats
Misskey was a mistake.
(DIR) Post #9vhajL2VZAXvsT1T3A by fristi@subcon.pub
2020-06-03T09:46:23.909098Z
1 likes, 0 repeats
@_p @absturztaube @lucy yeah. Pleroma even has an issue for it on the tracker, but I'm not gonna sit and wait for the fix. If I'm relaunching this instance, I basically have two options:- make a new user with a different handle- start new on a different hostname
(DIR) Post #9vhatpA6QUq8CFZi88 by fristi@subcon.pub
2020-06-03T09:48:18.362168Z
2 likes, 2 repeats