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
I read that a passenger was almost sucked out of a
#Ryanair flight after a window broke. What will be the next move of the airline?
@h0ng10 @Rapid7Official @attackerkb One nice thing about similar initiatives is that people can use them differently. Some moderation work would've been required for sure, but I don't see that as a major, shutdown triggering problem.
@h0ng10 I maintain
@attackerkb and I don't see an alarming level of spam. I see this more as one of the last community-driven knowledge-bases turning into a service/product.
@Rapid7Official
On the bright side now I *think* I figured out why the documented process fails, and now that I understand the problem better I know how to solve it correctly.
Now I'm entering the "How Could This Ever Work?!" phase.
#fail
In case you haven't figured it out already: meming is my coping mechanism
@infoseclogger been there when the CISO who ordered the gig started to create users for initial access like red.team1, red.team2...
Next Page