infosex.exchange <3

You are probably looking for the infosec.exchange Mastodon instance

This host is mostly for my random stuff, and in little part acts like a well-intentioned placeholder for the typosquatted domain.

Discoverability and Archiving

Currently I'm using this host for saving the items from my own feeds to the Wayback Machine and provide in-links for search engines. I hate that I have to do this, but the non-sense ideology of Mastodon pretty much ruined the search feature for Fediverse as a whole, and this wasn't changed by the fact that they owned their mistake and implemented search eventually.

Yes, I (or anyone else) could do similar things with other peoples published feeds, regardless of the tantrum. No, you can't defederate this, because the process doesn't rely on an instance.

Gluttony Section for Search Engines

@sassdawe AppLocker? :)
this post | permalink
[RSS] SSD Advisory – NVMS9000 Information Disclosure

https://ssd-disclosure.com/ssd-advisory-nvms9000-information-disclosure/
this post | permalink
@randomxusr Herding sheep away from computers.
this post | permalink
AlligatorConEU returns to Krakow - Sept 5-6 (conference), Sept7 (BBQ+workshops)

https://alligatorcon.eu

Bribes for invites are game, as shown here by Clarissa:
this post | permalink
@FlorianTischner @archiloque @dysfun @thephd no. cvss is not risk assessment.
this post | permalink
How would you know that IT should have noticed because someone used it? Sounds like a chicken-egg problem.
this post | permalink
@wdormann I still don't think though that algorithm modernity and "entropy" are connected: a compressor could become highly effective if it recognized large repeating chunks and assigned short codewords to them. I think what results in "noise-like" output is that compression is applied recursively, so the first-pass code tables are also compressed (see BLASTPASS :)). Maybe you could even do that with plain LZ until some point? I may be wrong, those uni lectures were a long time ago...
this post | permalink
@wdormann I've been typing up that LZ is not that advanced, but couldn't put my finger on why this particular pattern would occur considering the basic algorithm. The linked answer explaining the fallback behavior makes much sense though, thanks!
this post | permalink
@wdormann I don't think unreadability is a necessary consequence. Eg if you compress a lot of PEs the compressor may decide that the whole error string will be assigned a codeword and store this tuple in a table in some header. This is of course a very simple algo and Im not familiar with this particular one in Q.
this post | permalink
@TarkabarkaHolgy paging Kőműves Kelemen
this post | permalink
Next Page