jayofdoom

Full send comes from extreme sports-style events originally, basically meaning "go 100% with no fear of the repercussions". In racing, it usually means going into a corner so fast you're basically risking or guaranteeing you won't make the turn safely.

Almost everywhere I've worked that I helped run software in production for would have a step in CD which filed an automatically-approvable change req with automation; just like the automated deploys.

It becomes just robots pushing around paper for compliance.

Thanks! Ironic (ironicbaremetal.org) can be operated standalone outside of Ironic, and we do pay attention to non-OpenStack use cases (e.g. https://metal3.io/). If there's anything you're trying to do with Ironic that you're having trouble with, feel free to come chat. We're on IRC/Matrix on irc.oftc.net, #openstack-ironic.

-Jay, Ironic PTL

Yep. I'd explicitly never work at a place that implemented SAFE. Reading this article felt like someone describing the process at a previous employer. Just nailed it with all planning right at the intersection of useless, time consuming, and painful.

I am a former Mason. I left the lodge due to no longer complying with their requirement to believe in a higher power (God). To be explicit: Masonry used to be segregated into "Prince Hall" masonic halls (for non-white folks) and "normal" masonic halls. This split was ended, and now Prince Hall masonic halls are full masonic lodges, and membership is recognized in both directions. In practice; every lodge I ever attended was integrated even if it was a significant white majority.

When we were voting on new members, it was a silent vote with unanimous consent required. Any vote could be retaken at the order of the master. This means that if someone is eligible and should be a mason, and the vote comes up with a negative vote, the master can say a few words suggesting people reconsider and take the vote up again.

There was only once that I saw someone not pass the first ballot to become a mason. The master said that we should reconsider, and most of the brothers in the room chose not to vote the second time (as a symbol they were not the negative vote), and many of those who did showed their ballot before casting it. The second vote passed.

This as a process indicates there's plenty of room for abuse: any single master mason can anonymously vote to exclude someone for any reason they want. It's up to the folks around them to set them square if they are out of line. I can easily see an lodge existing where there wouldn't be any members willing to speak up in someone's defense.

It's my belief that none of what I've posted here is exposing any of the secrets of a master mason; but if any fraternal members disagree I'll happily edit and delete this post, and I don't intend to expose anything; but instead demonstrate that masonry (as well as, I'd assume, most other 'secret' societies), is as good as the members in the lodge.

I suspect your discounting the amount of effort it takes pypi index maintainers to respond to compromised packages.

In the same way folks can get upset over being required to use 2fa, the package index maintainers likely get upset every time that they lose hours of their life due to someone not using 2fa.

Despite much of this being critical infrastructure, I would be surprised if most people who run the index are doing so as part of their day job instead of volunteering. This is why I always try to show a lot of grace when people make decisions that I don't understand, because they may be facing situations I don't understand.

I've done backend/systems development work for over a decade.

Front end is a world of pain I want no part of. Regardless of how the system is skewed, I appreciate your specialty.

You can absolutely run pipewire for screen sharing while running something else for an audio server. If your distribution doesn't provide this as a supported setup, I suggest you check with them.

They didn't work with a data broker. You can pay the post office in the US to send your mailer to every single address in a given zip code. This sort of bulk mailing represents the majority of your junk mail.

The handful of times I've been up with private pilots who took me in their cessna, I did get an if I become incapacitated speech where they showed me how to operate the radios how to squawk 7700 and how to keep the plane level before we even took off.

A cfpb complaint got an issue resolved I had where my credit card issuing bank was refusing to accept that a charge was fraud. I issued the complaint with the exact same information I had given the bank support: that the supposed evidence that it wasn't fraud didn't include my signature and had an incorrect address, and as soon as the cfpb complaint came through the issue was resolved.

Absolutely not. We're in a period on the internet right now that has Chrome based browsers with a market share like ie6 had back in the day.

The primary reason I use Firefox is because it's a completely different engine and I think diversity in browsers is important to the health of the web as a whole.

Of course the damage was done by non-riders, these things are an absolute menace in the city. I feel like every time I go to Seattle now if I'm in a touristy area there are Lime scooters littering the sidewalks everywhere.

I don't think vandalism is the answer, but I also think taking up public pedestrian space to store your rental scooters is also a form of vandalism.

Yeah, that's the first thing I noticed. It's incredibly irresponsible to post examples without using example.com in order to ensure you don't actually hit someone's web service.

If someone was to try and simjack his mobile, they'd immediately know which carrier to try

from an Ironic core.

There were several months where I think we had contributors running a spell checker against patches as a review. They would miss obvious code syntax issues but would request lots of spelling changes (including British->American spelling).

You get what you measure. There's always going to be someone trying to do the absolute minimum to increment the number they get judged on.

Both in corporate and open source settings, I find the most difficult part of documentation to be how to organize it. There is a huge amount of good information out there, but it's incredibly difficult to find. I have this problem as a user all the time, but even when I'm creating the docs I'm not sure how to make them more accessible.

I don't think RMS is a villain. I think he's a person who helped create a lot of what we appreciate today, but if he's missing the social skills to be a good representative of the open source / free software community, then it's time for him to step aside and leave it to others.

It's pretty clear that he's been willing to do whatever is necessary to further the cause of free software -- today, that would mean stepping away from the FSF and leaving it to doing the business of promoting free software rather than having to cover up for his mistakes.

My wife has probably given away 50+ items of ours on buy nothing. Usually she appreciates being able to choose because some people develop a reputation for being unreliable to pick them up, so she can exclude them.

I think, based on the other comments here, and my experience with my own Brother printers... I think they are the "less clever" people building reliable printers.

Another option is registering a domain and setting up an email forwarder to a free email service. I know with gandi.net, they provide free email forwarding services with domains registered on their platform.

This gives you the best of both worlds: - free email hosting - no lock in to a single provider

Obviously, if you store valuable information in your email you want to back it up as well. But for me the concern was always more about losing the address than losing the data.

Formatting

If you don't own that domain that your email goes to, you don't own the email address.

Any number of things could happen to cause you to lose access to that email address:

- the company who owns that domain is sold

- the domain is sold during bankruptcy proceedings after the company goes under

- the company that owns that domain decided to get out of the email business - the company has a vested interest in migrating you to a new domain (as is here)

I'm surprised at the number of people – even in tech - who are willing to use an email account on a domain they don't have any control over.

If you don't own that domain that your email goes to, you don't own the email address.

Any number of things could happen to cause you to lose access to that email address:

- the company who owns that domain is sold - the domain is sold during bankruptcy proceedings after the company goes under - the company that owns that domain decided to get out of the email business - the company has a vested interest in migrating you to a new domain (as is here)

I'm surprised at the number of people – even in tech - who are willing to use an email account on a domain they don't have any control over.

I always assumed that part of the reason you mandate pre-commit code reviews was to protect the business from a rogue developer. If you have a developer who is empowered to merge code that is continuously deployed to production before a code review is done, that developer could code something that exfiltrates data and could do a lot of harm before it's rolled back.

This insider attack is clearly viable since something like this happened with the recent Twitter hack of verified accounts.

This is always so exciting! Congratulations.

> > Im still waiting for the AIB RX 5700's

> Curious, why are people waiting for these/what's the advantage?

The blower coolers on the reference board have been reviewed as loud and not very effective. The AIB coolers will likely run quieter, cooler, and not be blower style.

(A blower cooler is designed to have one giant fan that blows air across the card and out the slot cover. The advantage is almost any pc, regardless of case airflow, can safely run them... but most people dropping that much cash on a video cards can afford a case fan or two.)

Something I've done in the past is treated Make like a well-known API. Even if the logic is in separate scripts, I still implement a simple Makefile with common targets like "build", "clean" and sometimes "install". This allows people picking up your project to build it and work with it right away, without having to understand the details of the scripts.

Honestly, from my perspective the problem is more the timing. If MongoDB had always been licensed this way, companies could make informed decisions about what product to use. Instead, you pulled a license bait and switch -- attracted people with a free-as-in-freedom license, then switched it for one that was less free after adoption picked up. That's not behavior I'd personally support as someone who has a career because of free software, and I wouldn't support it professionally because of the immense risk a company takes on when adopting a piece of software for long-term use -- like a DB.

And all those comments are gone now. That's the real "oof" of this for me, as someone who did most of my facebook posting via twitter :(.

The thing that's truly bananas about this -- when I worked in SF and lunch was paid for, we always catered in from local businesses! This sort of benefit doesn't isolate you from the community, it invests in the community. More than once I went to a restaurant that had catered a meal at my job -- places I wouldn't have known existed had I not gotten a free lunch.