KeepFlying

joined 2 years ago
[–] KeepFlying 11 points 1 week ago

You've just opened a wikipedia rabbit hole. Wish me luck I may never return.

[–] KeepFlying 4 points 1 week ago (1 children)

Okay yeah that makes sense. So that rules out founding cults that use the information as their holy book. But it could allow for "keep it secret, keep it safe" cults where there's a holy object that they know is important but don't know contains the data. (But it can't be SO interesting that people try to inspect and understand it and inadvertently discover the data).

I wonder if you could rely on your buddy in the future knowing what your favorite password is and encrypting the data somehow.

Does it need to be discovered ASAP in that 20 year gap or can it be later on in that period once they know that you specifically are selected for the mission?

[–] KeepFlying 10 points 1 week ago (4 children)

I know wrong community but, what year did early civilizations think it was? Was their year zero our 10,000BC? What was their "the big thing that started the calendar"?

[–] KeepFlying 9 points 1 week ago (3 children)

Does it only need to be discovered by the people 100 years in the future, or can people before that be aware of it?

Because this reminds me of the nuclear waste protection research. You found a religion that fears glowing cats....

[–] KeepFlying 5 points 1 week ago (1 children)

I use it to (semi) automate bit repetitive tasks. Like adding a bulk set of getters, generating string maps to my types, adding handlers for each enum type, etc. Basic stuff, but nice to save keystrokes (it's all auto complete).

Anything more complex though and I spend more time debugging than I saved. It's hallucinated believable API calls way too often and wasted too much of my time.

[–] KeepFlying 2 points 2 weeks ago

I run Debian on most of my systems and run all of my services in docker (with rare exceptions for node_exporter or stable core tools). My base systems get automatic security upgrades, and then I'll manually check in every few weeks whenever I feel like it.

My services in docker are version locked to a specific major version (when there's a tag available) so I can usually re-pull to get minor version updates freely without breaking issues. My few more finnickey services get manual upgrades from me every 6 months or so only.

I usually stick to an OS version for as long as I can, and to that aim I stick to LTS versions with long support windows.

4 major versions in 12mo is...a lot. Especially if those include breaking changes for you. Yikes

[–] KeepFlying 7 points 3 months ago (1 children)

Looking at how bad our current system is, there's clearly no need to prevent the videos from getting out because the officer can get away with it despite that.

And even if the officer doesn't, the department can just scapegoat them and just keep doing the same things.

All the more reason to not waste a 0-day or risk the knowledge of a backdoor getting out.

[–] KeepFlying 4 points 3 months ago

Sourcing just shifts the problem to having to verify the source though. Antivax people could easily cite thousands of sources. We'd know there bullshit, but some mod would be stuck needing to vet them.

It's easy for common misinformation like antivax, but more unusual claims could easily be left around just because they have something seemingly relevant linked.

I don't disagree with the idea, it just isn't enough of a fix and would still require a lot of work.

[–] KeepFlying 18 points 3 months ago (3 children)

You'd likely only be able to use it effectively once before people seek out different recording devices, or just the knowledge that cameras were disabled in that area would be as damning as any video.

Especially for any zero-day exploits. As soon as it gets used people start protecting against them so they often don't work for very long. It would need to be a pretty big coverup to be worth burning an exploit on. Especially if it's likely that at least one person in the area wouldn't be susceptible and could still record it.

[–] KeepFlying 4 points 3 months ago (1 children)

I've used this nightly for years and it's been great for me. It takes some time to adjust the sensitivity to capture midnight ramblings properly, but the recordings are freely accessible and easily saved if you want to keep them.

[–] KeepFlying 31 points 3 months ago* (last edited 3 months ago)

Working for the agency isn't the problem on its own. If your job requires you to do something that is against your morals, resist up to and including loudly leaving that job if that's what's required. But until then it's more important than ever to stick it out and push to make things better any way you can.

[–] KeepFlying 2 points 3 months ago

There's definitely incentive for that from both candidates. If they talk about how ahead they are in the pills, people will neglect to vote. If they talk about how they're behind, then it's a foregone conclusion and people won't bother to vote.

If they preach about how close the polls are then it gets people worried enough to actually turn out and vote.

At this point I only seem to hear about polls directly from candidates or PACs so it's hard to know what the biases are.

27
submitted 2 years ago* (last edited 2 years ago) by KeepFlying to c/selfhosted
 

Does anyone have any recommendations for issue tracking for homelab setups? I'm sure I could host some Jira clone but that feels overkill for what I'm doing, and something like MediaWiki is too general purpose.

I'm hoping to track future project ideas (Install Jellyfin / Sonarr, etc) and issues with my smarthome (Fireplace Light not accepting color changes via Google Assistant). Ideally with some kind of organization to it (priorities, subitems, etc).

Yeah I could use plaintext, but that's no fun :)

view more: next ›