1·
23 days agoOh See Paren Left Brace Whatmark
For loads of alternatives, see the Jargon File
- 0 Posts
- 12 Comments
Joined 1 year ago
Cake day: July 23rd, 2023
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
Gonna have to disagree with #3 - stopping Vim is not necessary for this. There’s the builtin
:!command.
Don’t forget /auto, for things that get automatically mounted when you first access them (autofs)
Slow down there - you’re making some rather large assumptions about why they have guns. Sure, some people have guns for “self defense” (some for valid reasons, others because racism). Others have them for hunting. Sometimes they’re inherited and have sentimental value.
Edit: Also, kids aren’t the only reason not to keep them loaded. Keeping guns and ammo separately secured introduces enough of a delay to reduce the risk of suicide, for example.
Easy. You either set it up as a nonprofit (still not great in terms of incentives) or, better, as a consumers (or members) cooperative.
Alternatively, you don’t - you modify the incentives. Agency sets a one time, lifetime membership fee. Every failed match they set you up with refunds you a percentage of the balance.
Detailed example:
Let’s assume it’s a $1000 membership, 5% refund.
First match works out? They keep the $1000 First match fails? You get $50 back. Second fails? You get another $47.50 (2% of the remaining $950) By match #45, you’ve been refunded 90% and they’re still holding less than $100.
Why it works:
This strongly incentivizes the agency to make the best possible match as quickly as possible. Users aren’t incentivized to join fraudulently because they’ll never get more out than they put in. The agency has no reason to create fake profiles, since a bad match costs them money.
Where it (arguably) fails:
-
This incentive structure is designed for long-term, monamorous relationships. It fails to account for poly relationships. People using it for short term hook-ups would settle over time into #2 below.
-
After a certain number of bad matches, it’s not worth it to the agency to put any effort into making a good match. Since they make the most money on early matches, their incentive is to connect the most “desirable” candidates with new members. People with more failed matches will most likely be connected to … other people with more failed matches.
Arguably, this is a feature not a bug. For new members, it means they don’t get spammed by long-time members that are hard to get along with or not actually looking for a long term relationship. For the ones that the early match algorithms didn’t work put for, it means they’ll at least get exposed to different groups of people over time - including others that failed to match for similar reasons as themselves.
- Even if the user never makes a successful match and gives up, the agency still gets paid. An alternate strategy for the agency could be to make the worst possible matches so members give up early and they keep more of the membership fee.
This would not do wonders for their reputation and is probably not a good long term strategy for them - at least on the early matches. After a certain number of failures though, it might be an effective way to cut losses.
-
Pornography is
close tofull sex workFTFY
6·2 months agoThat would be true for competent web developers. Unfortunately, those are a vanishingly small subset.
Favorite would be a highly customized zsh.
fizsh (not fish) is what I actually end up using, as I can’t be bothered to copy that config around and retune it for each machine. Gives me the syntactic sugar of zsh with common default options on by default, an OK default prompt, and doesn’t break POSIX assumptions like fish. Also Installs quickly from the package manager without needing to run through the zsh setup each time - unlike oh-my-zsh. And if I still need customization, all the zsh options are still there.
107·4 months agoNotify the maintainer of the open source tool - they’re in the best position to push for compliance. They have the power to revoke the company’s license.
Something I haven’t seen mentioned yet - who is the company’s HIPAA “Compliance Officer”? If it’s anyone other than your boss, you could document the situation to them in an e-mail. If you want to be slick about it, ask them if there is “still any compliance need to keep the replacement machine ready or if it would be OK to repurpose it, given [your boss’s name here]'s decision not to move forward with the upgrade.” They’re on the hook for compliance violations, so they’ll likely see to it.
I would also suggest making a habit from now on of documenting verbal conversations that result in actionable decisions in short e-mails to the other party: " To recap our discussion, [bullet point list]"
You can excuse this as being for your own reference so you don’t forget any to-do items or so that they can correct any misunderstanding on your part, but it makes for a fantastic CYA if that ever becomes necessary. For really important items likely to bite someone later, print a paper copy if you don’t fully own and control the machine AND the e-mail local archive. Only bring those out if absolutely necessary, as in when SOMEBODY will be fired or you’re about to be legally scapegoated. They’ll save your butt once, but it will probably be time to start looking for another job because the boss will think either that you should have pushed harder earlier to fix the issue or be worried about their inability to scapegoat you in the future.
Probably because of this. The commenter overstated the situation, but there are valid and serious criticisms to be made.
Not true.
He can’t prevent anyone that received the code under the GPL from using (and distributing it) under the old license. He also can’t relicense code that he received under the GPL only under the new license.
If he receives a new license from the other contributors to distribute under a more restrictive license, he can do that because he has a dual license to the code and is not relying on the GPL for his right to distribute.