Conversation

Notices

1. meso (meso@asbestos.cafe)'s status on Monday, 29-May-2023 05:47:22 JST meso

   • Alex Gleason
   @alex doesnt work for me
   •  (mint@ryona.agency)'s status on Monday, 29-May-2023 05:47:19 JST 

     in reply to

     • Alex Gleason
     • Zero :zt_think: :artix:
     @zero @meso @alex The XSS is likely in the DM on that screenshot, public posts left on that instance do nothing. You can guess the chances of it getting reported to upstream.
   • Zero :zt_think: :artix: (zero@strelizia.net)'s status on Monday, 29-May-2023 05:47:20 JST Zero :zt_think: :artix:

     in reply to

     • Alex Gleason
     @meso @alex same, maybe cause I'm on older PleromaFE tho
   • meso (meso@asbestos.cafe)'s status on Monday, 29-May-2023 05:47:21 JST meso

     in reply to

     • Alex Gleason
     @alex <a href='d&#x61t&#x61<scr&#x69pt><scr&#x69pt\" src="/media/bd9ba60cefe8156fccc5bd9d6ee0e06e534d4d7d513890968d39b0e4bceb911a.js">'> this doesnt work for me i mean
   • Zero :zt_think: :artix: (zero@strelizia.net)'s status on Monday, 29-May-2023 21:03:07 JST Zero :zt_think: :artix:

     in reply to

     • Alex Gleason
     • 
     @mint @meso @alex I think I just found one that works if the FE is in an improperly configured subdomain without CSP to block inline JS eugh
      likes this.