cryptocurrency, but more generally
Now that the cryptocurrency hype has largely died down, maybe this will finally be the right time to say this:
The lesson from cryptocurrency ruining everything it touched, wasn't just "cryptocurrency is bad". The other lesson is that making something *about* money, of *any* kind, is the fastest way to stamp out any kind of healthy community dynamics and turn it into a race-to-the-bottom.
If you start your project by focusing on "monetization" as the goal, it will never become an enjoyable place for people to be. You cannot "monetize" your way out of a capitalist society. That people need to pay the bills, doesn't change this.
@cynicalsecurity short answer: yes
daemonising is, as a concept (forking into background), essentially incompatible with go runtime model, which implements its own M:N threading and uses OS threads rather loosely, and it's trivial to end up in a situation where the process would already have some threads started before it would reach your daemonizing code.
long answer: still yes, but daemonizing is bad anyway.
as a preface, the following is coming from being burned in many ways by processes attempting to drop privileges and daemonizing on their own. most often by silent failures with nothing on stdout/stderr/logs; but sometimes by leaking/retaining elevated privileges when they weren't supposed to.
self-daemonising is surprisingly difficult to do properly in general, arguably maybe even impossible if your code is anything but a statically linked executable directly interfacing with the kernel syscall interface (not even going through libc) because of how many things happen before "your" code is reached in process lifetime.
i've seen services dropping privileges improperly too often to trust just about any service to do so, regardless of what programming language they're written in, and instead i strongly prefer to have a service manager that would setup proper environment (privs dropped, etc etc) first, and then start the service.
if nothing else, there's less security sensitive code to audit, and it's in just one place, instead of having a myriad variations, with every service author implementing their own slightly different way of doing things.
And we're talking a fairly significantly-sized company here, this is absolutely not a sole developer or even a small team
Every time someone claims that "perpetual refactoring" for quality is not a viable software development strategy in a Real Business(tm), I think about this one customer I have, which quietly does exactly this, and has been profitably doing it for years, and now has some of the most maintainable and reliable code I've ever seen at any company or frankly any software project
fucked up world where having a brain with exceptional pattern recognition and situational awareness plus the ability to absorb knowledge about completely unfamiliar and dissimilar topics like a sponge, synthesize unconventional ideas and solutions from it, and laser-focus on a task indefinitely if it’s immediately rewarding is a serious disadvantage and considered a disorder rather than a highly sought-after trait on the job market
1000 richest people are approched. "The end of the world is here. Time to go to your doomsday bunker", they are told. The billionaires nodded. They knew this was coming. They were prepared.
So they gathered their loved ones and locked themselves in luxury bunkers. No contact to outside world.
10 years later they emerge. The world has healed. The air is breathable, people are happy. "What was the catastrophy?" they ask the first person they meet.
She screams: "THEY GOT OUT!!!"
@Gargron That’s one side of the deal. The other is to listen to the needs of the full diversity of users. If you want us all to be your marketing team, you need to accept everyone on your product team too.
Ticket revenue is also a way to keep property taxes lower in white suburbs.
Fines shift the tax burden from those who benefit from police presence to those who don't.
Tickets & fines are yet another form of tax evasion for the wealthy.
https://fortune.com/2023/09/25/speeding-traffic-tickets-broke-cities-towns-policing-for-profit/
@openaeros needs some help! If you have any connections with anyone familiar with IEC 61010 and CE compliance we would love to chat. We get the basics, but want some help navigating the labs & companies. Basically just need the inside scoop since this our first time.
twitter, bluesky
Did we all catch the part where Jack Dorsey, now of Bluesky fame, still has shares in Twitter?
https://www.washingtonpost.com/documents/2a00ce74-6d58-4f8e-bc2c-1bb820ee4705.pdf?itid=lk_inline_manual_10
that "nazi bar" analogy
@Heidentweet @joepie91 no, but the metaphor is moot anyway because the bar is owned by a nazi so even if other nazis were being kicked out by staff that’s still kind of a problem. But if we say we shouldn’t protest on the opressors turf, we’re doing the opressor a favor. So, it’s complicated and policing people for still being on there is a distraction not worthy of time, effort and goodwill regardless.
I genuinely wonder why, in 2024, user manuals still include a paragraph in the safety section stating that disabled people shouldn't use the appliance without supervision. Well, it's worded differently, but that's basically what they're saying.
Someone should really tell the folks who write manuals that we are in fact perfectly capable of operating, say, an airfryer without burning the house down. And while we're at it, we should make touch displays on kitchen appliances illegal.
Thank you for coming to my TED talk *gets off soapbox*
that "nazi bar" analogy
When talking about the "nazi bar" story, you should remember that the moral of the story was that the *barkeeper* had to throw out the nazi, and not that the other patrons were nazis for staying in the bar.
It's a story for community moderators. Not for everyone else. And trying to apply it as a universal analogy *will* go wrong.
Technical debt collector and general hype-hater. Early 30s, non-binary, ND, poly, relationship anarchist, generally queer.
- No alt text (request) = no boost.
- Boosts OK for all boostable posts.
- DMs are open.
- Flirting welcome, but be explicit if you want something out of it!
- The devil doesn't need an advocate; no combative arguing in my mentions.
Sometimes horny on main (behind CW), very much into kink (bondage, freeuse, CNC, and other stuff), and believe it or not, very much a submissive bottom :p
My spoons are limited, so I may not always have the energy to respond to messages.
Strong views about abolishing oppression, hierarchy, agency, and self-governance - but I also trust people by default and give them room to grow, unless they give me reason not to. That all also applies to technology and how it's built.