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
Since I read the JPL coding manual I'm always very considerate before introducing an infinite loop.
Then I usually decide that "it's fine, this is not a spaceship" and forget to implement the exit path.
@filippo Last time I checked you couldn't even migrate post between instances running the same software... I'm not sure if this is only a limitation when you'd transfer posts between remote servers and you could just vibe code a DB migration script, or there's some fundamental limitation of how posts are referenced in the network.
@filippo Pleroma/Akkoma are more lightweight if that helps
@algernon I wonder if the death of the last Pope was on HN...
Chuck Norris didn't die, he just roundhouse kicked all of us into this shit timeline :(
R.I.P.
Remote development mode in @zed is true killer feature! Previously I highlighted its usefulness for x-platform Rust dev, but now I'm using it instead of devcontainers to develop some not-very-trustworthy Python stuff.
Debugging worked out-of-the-box, I only had some trouble figuring out that LSP is not available until I mark the remote project as Trusted too.
Next Page