VoidOutput

5

VoidOutput wrote

Talking very generally: if you're dealing with critical infrastructure you're mostly safe, just have to hope you're not redundant. Other fields, you're at a medium risk of being laid off. Those most at risk are in jobs that could be described as "scouting": areas that were a gamble for the employer, mostly because of surplus resources, are the first to go because they'd be by definition unproven.

So applying that view to the IT field, I'd say: ops teams have a high chance of being safe if they were lean to begin with. Same for low-level or embedded. Apps and web are high risk, outsourcing being your most likely replacement. Data science and ML are straight fucked.

2

VoidOutput wrote

Regarding searching our database directly, there's already discussion about why doing that would be really costly. Now, at least with DuckDuckGo it's a step in the right direction and it doesn't preclude us from actually implementing search.

As for the feature being implemented for all Postmill instances: I had not thought about instances without Internet access, that's interesting. How are such instances run? What would be a way to detect such a situation?

3

VoidOutput wrote

The implementation does work for all postmill sites. As for Tor specifically, it depends on what you want to achieve: it will show results, but they won't be onion links themselves. If that's sufficient, great! If not, I'm afraid I don't know of a simple way to do that.