*tosses wineglass*
Pneuma
joined 2 years ago
You could get creative with a premium account "A" where you can designate another person/account "B"(can be free account) with emergency access after a waiting period.
When B requests access it'll send an email where A can approve/deny access immediately; or if you're completely locked out, B will be granted access after the waiting period that you can set passes.
B can either be another person you trust, or it could just be a written backup that can be locked somewhere safe but not accessed on a daily basis.
If you want, after designation you can cancel premium and the emergency access will still be active, you just cannot add/edit who has access.
[@piracy](https://lemmy.dbzer0.com/c/piracy) are you federated with kbin? The community does not come up when I search.
I was just thinking about this. The issue may be more complicated than it looks.
Currently Jerboa handles the links of only a handful of instances. As Lemmy as a whole grows and more and more instances pop up, it's just unrealistic to have the app handle 50 million server hosts.
Can opening links be something handled internally, at least initially, like maybe checking against the home instance's list of federated servers?
I thought it'd be useful for people who are only subscribed to /c/piracy from another instance to become aware of the communities local to this one
Good call!
Did my part and searched them on my home instance and subbed to a few of them.
To the folks who are trying to do the same on their home instances, you can actually just paste the URL directly into the search field (eg. https://lemmy.dbzer0.com/c/switchpiracy) instead of doing the !switchpiracy@lemmy.dbzer0.com syntax.
When you click search it may return no results or just a post or two, but just wait for about 10 seconds or so you'll see the community pop up. Like so.
As per usual, Redditors took the matter in their hands and compiled every official response into a readable format.
Unless it was a dig at spez for not giving any actual answers, because ultimately there were none.
If you nuke the entire thing, you can blame technical difficulties, dropping support for "legacy" products and whatnot.
Whereas if you only delete the offending content, it could mean:
When found out, it could be used against you for consciousness of guilt and trying to conceal it. Even if it doesn't amount to charges it could be a bad look for the company down the road; whereas you could just tank the hit right now for being a heartless CEO and it only goes to the pile of things Reddit is doing for IPO.
But let's say there's no crazy conspiracy behind and they're just trying to clean house. You can never be sure how wide spread it is, or if you can indeed remove everything. Most importantly, why would you even devote extra resources to finding and reviewing for something that adds little to no face value to the main product(s)? Might as well just nuke the whole thing and be done with.