#tankiesfuckoff — Public Fediverse posts

"On authority" arguments in a nutshell.
#onauthority #anarchism #debate #leftistmemes #2024election #anarchy #antistatism #authority #queerliberation #tankieLogic #tankies #tankiesfuckoff #tuesday #politics #badargument #anarchistdebates #antiauthority #antiauthoritarian #postleft #stirner #egoism #egocom #egoist #antimorality #anticapitalism #communism #statelessness #utopia #utopian #soviet  #ml #lenninism #stalinism #maoism #authoritarian #authoritarianism #leftism #leftist #lgbt

@[email protected] That #vulnerability was zero-day and immediately exploited leading to at least three very large instances I know of getting unscheduled downtime for a long amount of time, and it took a full 24 hours IIRC for those #Lemmy instances to get their frontends all properly patched up with a release. A #security disaster all preventable if you had just took the #CSP issue that has been there before the exploit a bit more seriously... ​:reimu_sigh:​

Compare that with #Sharkey's JSON vulnerability which was already mitigated and fixed in no time.

Funnily enough #kbin had a similar #XSS problem too one month before yours. But it didn't lead to that disaster your carelessness in security caused because kbin had a line of defense that didn't break down which is the safe link handling in their #Markdown parser.

You had three chances and you spectacularly failed in all of them! For some elementary security issue every #linkaggregator / #socialmedia dev should know of when dealing with untrusted Markdown input! ​:koishtare:​

Now if you could kindly piss off with that poor reply that didn't really address anything in my thread, you fucking #tankies. ​:seija_coffee:​

#tankiesfuckoff

@[email protected]

@[email protected] That #vulnerability was zero-day and immediately exploited leading to at least three very large instances I know of getting unscheduled downtime for a long amount of time, and it took a full 24 hours IIRC for those #Lemmy instances to get their frontends all properly patched up with a release. A #security disaster all preventable if you had just took the #CSP issue that has been there before the exploit a bit more seriously... ​:reimu_sigh:​

Compare that with #Sharkey's JSON vulnerability which was already mitigated and fixed in no time.

Funnily enough #kbin had a similar #XSS problem too one month before yours. But it didn't lead to that disaster your carelessness in security caused because kbin had a line of defense that didn't break down which is the safe link handling in their #Markdown parser.

You had three chances and you spectacularly failed in all of them! For some elementary security issue every #linkaggregator / #socialmedia dev should know of when dealing with untrusted Markdown input! ​:koishtare:​

Now if you could kindly piss off with that poor reply that didn't really address anything in my thread, you fucking #tankies. ​:seija_coffee:​

#tankiesfuckoff

@[email protected]

@[email protected] That #vulnerability was zero-day and immediately exploited leading to at least three very large instances I know of getting unscheduled downtime for a long amount of time, and it took a full 24 hours IIRC for those #Lemmy instances to get their frontends all properly patched up with a release. A #security disaster all preventable if you had just took the #CSP issue that has been there before the exploit a bit more seriously... ​:reimu_sigh:​

Compare that with #Sharkey's JSON vulnerability which was already mitigated and fixed in no time.

Funnily enough #kbin had a similar #XSS problem too one month before yours. But it didn't lead to that disaster your carelessness in security caused because kbin had a line of defense that didn't break down which is the safe link handling in their #Markdown parser.

You had three chances and you spectacularly failed in all of them! For some elementary security issue every #linkaggregator / #socialmedia dev should know of when dealing with untrusted Markdown input! ​:koishtare:​

Now if you could kindly piss off with that poor reply that didn't really address anything in my thread, you fucking #tankies. ​:seija_coffee:​

#tankiesfuckoff

@[email protected]

@[email protected] That #vulnerability was zero-day and immediately exploited leading to at least three very large instances I know of getting unscheduled downtime for a long amount of time, and it took a full 24 hours IIRC for those #Lemmy instances to get their frontends all properly patched up with a release. A #security disaster all preventable if you had just took the #CSP issue that has been there before the exploit a bit more seriously... ​:reimu_sigh:​

Compare that with #Sharkey's JSON vulnerability which was already mitigated and fixed in no time.

Funnily enough #kbin had a similar #XSS problem too one month before yours. But it didn't lead to that disaster your carelessness in security caused because kbin had a line of defense that didn't break down which is the safe link handling in their #Markdown parser.

You had three chances and you spectacularly failed in all of them! For some elementary security issue every #linkaggregator / #socialmedia dev should know of when dealing with untrusted Markdown input! ​:koishtare:​

Now if you could kindly piss off with that poor reply that didn't really address anything in my thread, you fucking #tankies. ​:seija_coffee:​

#tankiesfuckoff

@[email protected]

@[email protected] That #vulnerability was zero-day and immediately exploited leading to at least three very large instances I know of getting unscheduled downtime for a long amount of time, and it took a full 24 hours IIRC for those #Lemmy instances to get their frontends all properly patched up with a release. A #security disaster all preventable if you had just took the #CSP issue that has been there before the exploit a bit more seriously... ​:reimu_sigh:​

Compare that with #Sharkey's JSON vulnerability which was already mitigated and fixed in no time.

Funnily enough #kbin had a similar #XSS problem too one month before yours. But it didn't lead to that disaster your carelessness in security caused because kbin had a line of defense that didn't break down which is the safe link handling in their #Markdown parser.

You had three chances and you spectacularly failed in all of them! For some elementary security issue every #linkaggregator / #socialmedia dev should know of when dealing with untrusted Markdown input! ​:koishtare:​

Now if you could kindly piss off with that poor reply that didn't really address anything in my thread, you fucking #tankies. ​:seija_coffee:​

#tankiesfuckoff

@[email protected]

Since #Lemmy bashing is taking off again (thanks @[email protected]! ​:cirno_thumbs_up:​), here's your friendly reminder that Lemmy devs are #redfash / #tankies, and one of them posted literal #fascist (#LaRouchite) propaganda to the r/socialism #subreddit and got banned for it. ​:seija_coffee:​

They also ban people talking about #Stalin and #XiJinping's #homophobia in lemmy.ml (the flagship instance!), so I guess they're #homophobes too ​:reimu_sigh:​

If your instance already has a #fediblock on all #Soapbox instances in the #fediverse for using software developed by #fascists, then it makes sense to defederate from all Lemmy instances as well for using software by red fash ​:cirno_fumo_yes:​

#tankiesfuckoff #fediblockmeta

Hammer and sickle is a symbol of oppression, period. #TankiesFuckOff