igneo676

Safer to just publish a new article when there's a sufficient amount of content to update. Link the articles together somehow. Maybe add a disclaimer to older (and not updated) articles that they might no longer be valid

Also solves the problem others have mentioned where they don't trust the date on articles. If you have a solid previous article to link to, you're more likely to build trust that the new one really is new

And we back that up, forcefully. If my kid doesn't want a hug, they will not be getting a hug. If they don't want to share, they won't.

My kid's autonomy is worth way more than those relationships. Period.

And it's worth it. Your kids will naturally share when they feel comfortable doing so. They'll share affection when they feel comfortable. And longer term this extends into topics they're not mature enough to tackle at 3

For minor infractions, it's probably not worth becoming an activist. For instance, if I'm not being paid proportional to the market or my boss is creating a difficult culture, it's probably just time to pack up and leave. I might not even bother offering any real feedback on the way out.

For more major ones, an example from the article was preventing an employee from talking about wages, I'm going to continue doing exactly that AND look for my out. I'm also going to talk to my fellow employees about their legal rights and how this isn't right. Bonus, if I'm fired before I can find a job, I'm probably going to talk to a lawyer at bare minimum

Anything above that, I would argue you've drifted into becoming part of the problem. And the fact that you've "never seen this kind of thing work out positively for the person that does it" is part of that system that perpetuates the kind of toxic workplace you've seen. It sucks, but you've been called to fight against a giant and hopefully the worst that happens to you is you get fired. Best case, perhaps the rarest, you're part of the resistance that brings down something truly toxic

Because I actively look to join companies that share my values and leave when things get even slightly dicey, I've not had to go beyond minor infractions. But if I'm ever faced with something truly bad, I hope that I have the courage to stand even when others do not.

Edit: It also helps if you work for small companies and know the whole stack of management above you

For larger companies, knowing a few levels above you and whether or not they'd stand for shenanigans is useful too. Ideally your manager will be frank about the state of things and willing to fall on the sword for important issues

Finally, if you're a manager, you're an extension of the company and any toxic things they inflict on people below you in the hierarchy. "Minor infractions" should be fought, and you're complicit if anything worse happens. You should be willing to be fired rather than enforce anything unethical on your employees. Otherwise you simply shouldn't be a manager.

1. Loses their signing keys

2. Needs to migrate to a better signing algorithm

Google can just handle that on your behalf. Additionally, there's no more need to care about signing keys at any point in the development pipeline. Rather than keep it secret, anyone with proper access to the Google developer console can sign and release apps

More cynically, what they're really guarding against is other app stores. It's MUCH harder to migrate an app from the Play Store to another store if the signatures don't match.

* Without a matching signature, the user can't pull their data from Google in the same way. They'd have to completely uninstall and reinstall the app, potentially losing data if the app isn't backed by a server.

* With a matching signature, the other app store should pick it up seamlessly.

Modifying apps without opt-in seems like a step further than they'd be able to pull off without massive backlash right now.

[1]: https://wiki.archlinux.org/title/Arch_Build_System

> built the technical recruitment operations in the last 3 start-ups I worked for, so I feel I’m somewhat qualified in the subject matter

Sure, your startup might have some very tight requirements for a position and the ability to research candidates before conversations. That's precisely what you should do since time is limited and (presumably) you're not hiring for a TON of positions

But an external recruiter needs to match X jobs to Y candidates. It almost doesn't matter what the tech stack is at that point, you probably have an open position to fill that'll match that person. It's a numbers game and it's a "Please respond to me at any cost" game.

And often, even if you did research, there are so many false negatives that it didn't even matter to begin with. I've had targeted recruiters reach out to me that are amazed when my current position doing $CURRENT_TECH isn't completely representative of my skills and I'm actually a viable candidate for $NEW_JOB_WITH_OTHER_TECH

The only real response here is to cut em some slack or ignore them. Guides like these don't help

1. The F-Droid team has a set of checks that they perform:

  a. Is the app open source?

  b. Does the app do things that the user might not want? ie access non-free services

3. The volume of new applications seem small enough that the F-Droid team can keep up just fine. The only problem I've seen w/ F-Droid resource problems are updates that take days to show up

4. As other have mentioned, you can opt out by running your own repository. Nothing is locking you into the F-Droid primary servers

I appreciate the additional curation F-Droid brings and I love the fact that I can tell other people to use F-Droid unreservedly and know they won't get anything spammy or freedom restricting

Their contract basically states:

1. PTO can't be paid out at the end of employment

2. PTO can't be used to quit the job

3. PTO can't be used _the entire last month_ of your employment with them

Which is nuts

Once a harmful set of actions comes to light, it's your job as the leadership team to:

1. Apologize

2. Correct the wrong

3. Allow your employees the space to process and heal

  a. Note: People are messy. Especially hurt people express themselves in ways that seem foreign to us. Listen to them

Rather than allow space for employees to reach catharsis, they shut down the employees internally. Rather than get their employees back on the company mission, they told them "there's the door". All while externally extolling the virtues of "staying out of politics" and gaslighting everyone.

They're within their rights to do that. Supposedly all of this passed internal HR/Legal review. It's just not the ethical way to deal with this. It's not what we expected from a company that we've long associated with being brash-but-ethical in their dealings

When I was trained in restaurants to deal with (potential) service dogs, the extent to which I was allowed to ask any questions was "Is that a service dog?". As long as the answer was "Yes", I was to leave them alone. No questions asked. Anything else supposedly opened you to litigation

Edit: Looks like there's a separate thread with additional ADA info. Tl;dr - nothing you can do to stop people misrepresenting their dogs as service animals.

Beyond the citation though, it makes logical sense. The mechanism for sanitation is that the soap itself destroys the bacteria. This mechanism works regardless of temperature. Cold water + Soap should be just fine as long as your hands are otherwise visibly clean.

In the food industry, we were required to use high temperature water. This was presumably to remove actual surface contaminants (dirt, grease, other food contaminants) rather than for actual sanitation. That's why you might still see guidelines for using hotter water temperatures.

[0]: https://github.com/arcadia-unity/arcadia

Sourcehut assumes you know your way around Linux and want to spend the time to understand how to host the services you need. The expectation will be that, if you run into issues, you're willing to debug and submit patches if necessary.

Alternatives like Gitea/Gogs are hostable as essentially single binaries and have clear guides on how to host on Docker. They're less feature rich, but more widely used in a self hosting context.

If you're looking for a middle ground, I've had good luck hosting Gitlab but it will consume more server resources than anything mentioned thus far and be a little more difficult to keep up to date

https://cabezal.com/sicp

Unless I'm missing something, that essentially solves the issue, no? Persistent private key, usable across all your machines that can't be exfiltrated. Bonus since you can even generate the key directly on the device!

This gets even easier with newer OpenSSH versions if you use FIDO2 auth for SSH. I've not played with it personally, but word is you just plug in the key and off you go

CDs and/or Streaming services are victims of the "loudness" wars, resulting in music with low dynamic range. Since vinyl is often mastered by someone who specializes in the vinyl and is rather niche, they have full freedom to make it sound as good as it ever will be.

That's also one reason why some people prefer Tidal or <insert HiFi music services of your choice> because sometimes they simply use better masters. At least, that's the only reason that can't be chalked up to placebo

I used Arch Linux and followed their docs[1], mainly because I wanted it to also run without root. Big mistake. Attempting to run a simple postgres database w/ and w/o root permissions for Podman resulted in my system getting into an inconsistent state. I was unable to relaunch the container due to the state of my system.

I mucked around with runc/crun and I ended up literally nuking both the root and non-root directories that stored them on my computer. I reset my computer back to Podman for root only, hoping that I had just chosen a niche path. It still would leave my system broken, requiring drastic measures to recover. No thanks.

After much debugging, finally switching back to Docker, I realized my mistake: I had forgotten a required environment variable. Silly mistake.

Docker surfaced the problem immediately. Podman did not.

Docker recovered gracefully from the error. Podman left my system in an inconsistent state, unable to relaunch the container and unable to remove it

Again, I'm not sure how much of my experience was just trying to force Podman into a square hole? I'm sure there are other people that make it work just fine for their use cases

Edit: I should note that I used it as a docker-compose replacement, which is probably another off-the-beaten path usage that made this more dramatic than it should have been

1. https://wiki.archlinux.org/index.php/Podman

1. No GUI needed

2. Discoverable and searchable directly through Brew

Longer: One of two things -

1. Choose the most boring software possible, trust that the process will work as expected and that you're no worse off than anyone else. Update your software regularly

2. Choose the simplest, most robust software possible (Alpine, OpenBSD, etc). In this case, doas instead of sudo. Pray that works better than everyone else or that you get some benefits through obscurity. Still get surprised every so often. Update regularly

Either way, modern software has gotten complex enough that there's few options for the average person

IANAL - so there's likely some caveats (you probably can't just use the exFAT name unless certain qualifications are met, just like you can't use Firefox's trademarks willy-nilly), but that should be good enough for just about anyone. Including paranoid OSS peeps like me :)

0: https://cloudblogs.microsoft.com/opensource/2019/08/28/exfat...

I had friends growing up who lived with extended family all in one house. They'd convert any space they could into rooms and house as many people as they could. That's not a situation that'd be allowed under rental agreements or housing laws but is totally fine as long as you own the house you're living in. Not to mention the nightmare of communicating with your landlord every single time someone moved in or out.

Similar for me: Before I got into tech, I bought a house on a fast food salary w/ a lot of help from housing programs. 15k of my 65k mortgage was subsidized! This allowed me to jump from a $650/month 2 bedroom apartment to a $550/month mortgage and house 4 children. An equivalent apartment would've eaten my meager salary alive and would have been untenable. Anything equivalent to the apartment I had would've not been allowed legally

Want a numpad? Switch to a different layout on the fly and have a numpad where you want it. Arrow keys? F-Keys? Why not have those on home row with another layout!

It can get gimmicky, but the impetus for it is that less overall finger/wrist movement == more ergonomic but I'm not fully convinced. Instead, I just prefer everything I can get on home row.

Now that people are writing "components" in frontend languages , it makes more sense to reason about styles in terms of those components. That's basically the insight that Tailwind had - can we get the benefits of componentization without resorting to CSS-in-JS solutions? The answer is yes. And we can even bring it to other development stacks by using Post-CSS

My favorite part is how low-effort the video calls themselves are. It makes me far more likely to end the conversation instead of waffling around looking for other things to shove into a meeting