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
@addison Thanks, that's in line with
@alphastrata's suggestion and the advice I got afk.
I'm quite new to Rust and it's strange that something as simple as moving a couple of lines of code into a function (I'm still considering a macro actually) can require this much consideration, but I guess this is the price we pay for stability.
@addison Thanks, that makes sense, but I can't touch Session as it comes from a dependency. There is definitely a lifetime issue here too (esp. because the actual tree of objects goes ~5 levels deep).
I think the root of my Q is if there is a way to create a "will" for Rust functions/scopes that would say "after my death my caller will inherit all that I own (so please don't free shit up)"?
@kstrlworks Oh sry, I'm on 25.7<whatever is the latest patch>. I simply use two bridged interfaces on Proxmox. Based on my above observations I think this is more of a design issue of moving around files during the upgrade process, and *maybe* something you can mitigate with some ZFS magic (I'm on UFS).
@alphastrata Thanks! I'll probably end a up a solution like that but still wonder if this can be achieved without Box/refcounts (should've added to the question)?
@kstrlworks It looks like a transient error, most likely a corrupt download. Shit happens ofc, but he only acceptable reason for bricking the system would be hardware error which is very unlikely because other VMs on the same host run just fine.
Next Page