@mint new vuln dropped?
Conversation
Notices
-
pomstan (pomstan@xn--p1abe3d.xn--80asehdb)'s status on Wednesday, 22-May-2024 19:58:37 JST pomstan -
(mint@ryona.agency)'s status on Wednesday, 22-May-2024 19:58:33 JST @i @pomstan Gleasonwaffen remembers. -
:blank: (i@declin.eu)'s status on Wednesday, 22-May-2024 19:58:35 JST :blank: @pomstan @mint it was a year old, but no one cared -
:ihavenomouth: (inginsub@clubcyberia.co)'s status on Wednesday, 22-May-2024 20:03:06 JST :ihavenomouth: @i @mint @pomstan wait, mint, did you change the tag a year ago? -
(mint@ryona.agency)'s status on Wednesday, 22-May-2024 20:03:06 JST @Inginsub @i @pomstan The date in the object can be arbitrary, servers have no way of figuring out the actual date of the post that wasn't immediately sent to inboxes.
e.g. https://clubcyberia.co/notice/AfgtplpaaoFZ5tXRR2 -
:ihavenomouth: (inginsub@clubcyberia.co)'s status on Wednesday, 22-May-2024 20:03:07 JST :ihavenomouth: @i @mint @pomstan i think you’re missing the point In conversation permalink -
:blank: (i@declin.eu)'s status on Wednesday, 22-May-2024 20:10:32 JST :blank: @mint @Inginsub @pomstan yeah, and people have known about it since https://gitlab.com/soapbox-pub/rebased/-/merge_requests/270 which is 4 months off a full year, though no one considered the fact it would overwrite the original accounts tag in the db
every single instance it federated to is going to need to fix grafs @ manually in the dbIn conversation permalink Attachments
likes this. -
(mint@ryona.agency)'s status on Wednesday, 22-May-2024 20:12:11 JST @i @Inginsub @pomstan There's https://git.pleroma.social/pleroma/pleroma/-/merge_requests/4084, but it requires pretty much the same amount of commands as just changing the nickname field in DB. In conversation permalink Attachments
-