Notices by :niggy: (niggy@poa.st), page 2
-
:niggy: (niggy@poa.st)'s status on Friday, 06-Oct-2023 20:58:32 JST :niggy: @Dicer miss that old @, btw this was in response to me drawing fanart for this guy
twitter.com/ArgyleAchilles/status/1389116663522480132 -
:niggy: (niggy@poa.st)'s status on Friday, 06-Oct-2023 20:58:20 JST :niggy: @Dicer curious where you even found that screenshot? wonder if any more funny stuff from my old twitter is archived -
:niggy: (niggy@poa.st)'s status on Friday, 06-Oct-2023 20:58:19 JST :niggy: @eolach ban evasion is still against twitter rules I think... but @freshniggy only lasted a few months back in 2021, have @bestniggy now -
:niggy: (niggy@poa.st)'s status on Thursday, 05-Oct-2023 02:55:53 JST :niggy: @ruina her name is niggy -
:niggy: (niggy@poa.st)'s status on Thursday, 05-Oct-2023 02:55:52 JST :niggy: @ruina her name is tenshiggy -
:niggy: (niggy@poa.st)'s status on Thursday, 05-Oct-2023 02:55:52 JST :niggy: @ruina her name is sniggy -
:niggy: (niggy@poa.st)'s status on Thursday, 05-Oct-2023 02:55:51 JST :niggy: @ruina her name is chiggy -
:niggy: (niggy@poa.st)'s status on Thursday, 05-Oct-2023 02:55:39 JST :niggy: @Inginsub @ruina -
:niggy: (niggy@poa.st)'s status on Tuesday, 03-Oct-2023 23:44:46 JST :niggy: @Billy_Hughes google -
:niggy: (niggy@poa.st)'s status on Tuesday, 03-Oct-2023 23:44:45 JST :niggy: @Billy_Hughes why wouldn't I research my Computer Niggy Exploitation operation? -
:niggy: (niggy@poa.st)'s status on Tuesday, 03-Oct-2023 20:05:45 JST :niggy: the word "niggy" is now officially recorded in US federal court documents -
:niggy: (niggy@poa.st)'s status on Monday, 02-Oct-2023 23:40:21 JST :niggy: @theorytoe :niggy_dab: -
:niggy: (niggy@poa.st)'s status on Friday, 29-Sep-2023 20:53:57 JST :niggy: I am racist -
:niggy: (niggy@poa.st)'s status on Tuesday, 26-Sep-2023 22:37:46 JST :niggy: yes friend, I believe the artist hints at it in their (translated) description:
>The first time, I failed to land, so I set up money with everyone in the office and made Sachiko a body that could keep flying all the time.
>Also, you may think that it was a composition you saw somewhere, but don't worry.
archive.is/84A9I -
:niggy: (niggy@poa.st)'s status on Tuesday, 26-Sep-2023 18:36:32 JST :niggy: her name is niggy -
:niggy: (niggy@poa.st)'s status on Sunday, 24-Sep-2023 19:07:04 JST :niggy: her name is niggy -
:niggy: (niggy@poa.st)'s status on Wednesday, 13-Sep-2023 03:44:00 JST :niggy: the code bases are massive, 10s of millions of lines + all the 3rd party libraries, and these bugs are tiny and very hard to find. these are the kind of mistakes that cause memory corruption exploits:
- indexing an array at 1 instead of 0
- freeing an object, then using that object somewhere else
- freeing an object twice
these bugs are rarely even found by humans, but automated fuzzing. it’ll find the most obscure complicated edge-cases that cause these conditions, which a human can’t find by reading the code
-
:niggy: (niggy@poa.st)'s status on Thursday, 07-Sep-2023 10:05:31 JST :niggy: got community note access -
:niggy: (niggy@poa.st)'s status on Thursday, 07-Sep-2023 09:29:26 JST :niggy: her name is niggy -
:niggy: (niggy@poa.st)'s status on Wednesday, 30-Aug-2023 16:11:09 JST :niggy: @Zerglingman @graf no XSS stuff, people worked pretty hard at finding all those vectors in the backend, and the standard Poast frontend (Soapbox) dev is actually competent and has CSP that mitigates that. Soapbox has never had a XSS vulnerability I believe
Even a couple of years ago when I reported exploitable HTML injection (forms + css), there wasn't XSS