KillingTimeItself
- 0 Posts
- 69 Comments
im not sure to which scale this is true, but TOR specifically is highly centralized, and by design I2P is extremely decentralized, with most nodes running network routing of other nodes. Not that it’s impossible to do, it’s just a lot harder, and not nearly as valuable.
A lot of the ways in which people are got over shit like TOR is just skill issuing. Don’t run a drug empire on the darknet and you’ll probably be fine. If you do run a drug empire on the darknet, you better be damn fucking good at opsec, and pretty fucking good at laundering money. And even then you’ll probably still end up fucking it up.
it’s all encrypted, and a darknet, so unless you’re routing through exit nodes, or you host an exit node, that information isn’t publicly accessible.
the other problem here is the “illegal contents” problem, if UPS accidentally ships a human head in the mail, is that the fault of the UPS? If someone mails a bomb to someone else, is that also the fault of UPS?
Ultimately, there is little to no reasoning as to why you should be capable of getting into trouble, unless you’re storing it, and it’s a very very strict law. But it’s a router, so it shouldn’t be storing anything.
because there’s also a lot of good stuff on the internet. There was very little on the internet in 2002, and yet people still used it because it was cool. There is a shit ton of information on the internet now, most of which is garbage, and the rest is somewhere between mediocre, or decent, and some of it being genuinely good.
If you hate living, why even bother living? It’s a question of the ages. What’s the point of living if there is no grander purpose? Surely it means nothing, right?
as a chronic documentation reader, the best advice i can give is to document everything Anything that the user can and will potentially interact with, should be extensively documented, including syntax and behavior. Write it like you’re coming back to the project in 5 years after having done nothing and you want to be able to skip right to using it. When we build something ourselves, we often hold a bit of internal knowledge from the design process that never quite goes away, so it’s almost always a lot easier for us to reverse engineer something we’ve made, than it is for someone else with zero fore-knowledge to do it themselves.
Generally this can be a bit of a nightmare, but if you minimize the user facing segment it’s not all that bad, because it’s usually pretty minimal, and what would otherwise be a handful of pages, turns into 10 or maybe 15.
as for existing documentation, the i3wm user guide is really good, it’s pretty minimalist but it leaves you enough to be able to manage.
i would aruge that the arbitrary factor of “9am being morning” is entirely to do with the fact that morning is actually a solar time phenomenon, whereas global time does not have the concept of morning, since it is merely imitating the local solar time.
Local solar time being the literal point in the sky that the sun is in.
It gets even funnier if we include people who aren’t “normal” I for one, consider noon to be morning.
i believe they’re referred to in documentation as “urgency hints” it should be in the user guide. heres the guide just do a ctrl f for urgency, it should pop some stuff up. It’s also a default config option for the base file.
one of my favorite fun facts, is that apparently a non insignificant number of “carbon credits” come from unsealed oil wells being sealed up. Which sounds good and all.
Until you realize that leaving oil wells unsealed is literally illegal and not to regulation standards what so ever. So you are literally paying for carbon credits, that remove carbon, that never should have been in the environment to begin with.
I love capitalism.
floating WMs are intuitive, but the problem is that they’re an incredibly mediocre solution, and the way that problems are often solved around one, is just entirely asinine. Let’s build ten different ways to do the same thing, now we have 10x the code to build and maintain, and it’s 10x more confusing to the end user who probably won’t know about half of them, because 90% of our documentation is redundant!
Tiling WMs have significantly less issues with this, because they often have a very strict set of management rules, and only those. Nothing more.
I think it’s probably because we’ve shifted away from shipping software as a product, and onto software as a service. I.E. in the 90s if win 95 irreversibly corrupted, that would be devastating to sales.
But today with windows 11? Just roll it out in one of the twenty three testing branches you have and see what happens, and if shit does break. Just work around it. It’ll be fine. Even if something does happen, you can most of the time, fix it and roll out a new update.
And i also think it’s moved to be more team centric, rather than department centric. A lot of the theory is probably more senior team led type responsibility. While everyone writing the code can chip in and add some as well. Developers knowing how to write secure code helps, so they should theoretically also be capable of QA themselves to a degree.
Also there’s a lot more money in shipping shit out the door, than there is in shipping a functional product, unfortunately.
yeah, and? What are they going to do? Send the DEA after you for growing GMO titties? Gonna hit you with the ATF because you grew hormonally altered facial hair?
They’ve got shit like fentanyl to be worrying about. I think this is probably the least of concerns, especially considering this is less “drug addiction” and more “illegal prescription drugs” instead. Besides, they don’t get drug money from trans people.
It’s certainly a potential risk for procurement of the drug legally. But that’s already a problem.