soneil

Surely this is entirely the opposite of proving a negative? It's a direct, testable, provable claim.

I found the same. It's impressive how much bluesky resembles twitter, but I'm not sure if that's a compliment.

On Mastadon I find much smaller circles, but much more engaged.

I think bluesky is winning at discovery. If I want to feel the pulse on a topic, bluesky is winning. If I'm not even aware there's a topic that I want to feel the pulse on, bluesky is winning. But I think mastadon has been successful at curating a very different 'vibe', and I appreciate it. So I catch up on mastadon first, and then doomscroll bluesky if I need to find work for idle hands.

So if my watch shows seconds, I'd be late at 12:59:31?

Not even a $5 VPS - my first WP site was shared hosting. Less relevant these days, but as barriers to entry go, wordpress was only one step higher than notepad.

Not including actual costs seems nuts. Especially with some of the tariff structures expected in the near future, some of those costs are not insignificant.

A bit of a tangent, but on your note amount multi-material being wasteful - you can improve that a lot by thinking ahead in your design and being strategic about where you use colour.

Your benchy is almost a worst-case scenario (which is likely intentional) - because the coloured features are vertical, there will be several changes per printed layer. If you can constrain your material changes to layer boundaries you'll get a much better waste ratio.

A good example of this is printing coloured labels/features on a faceplate. So you print the whole faceplate in a single material, then switch material and print the highlight colour as raised features. That gets you a lot of result for a single material change. (On single-material printers there's a method where you strategically pause the print and swap the materials by hand. Learning lessons from that will really hammer home the mindset of optimising tool changes!)

There's a lot of lessons like this you'll pick up, where making your design sympathetic to the print process can have huge payoffs.

This reminds me of the systemd bug where usernames starting with a digit were mishandled (#15141).

It seems to me like something that "should" be relaxed, but we need to have high confidence in the entire foodchain. adduser seems like the last place it should be changed, not the first - anyone requiring "enough rope" is already served by useradd.

I had fun in the vmware-broadcom transition because the broadcom portal doesn't allow that, but the vmware portal did. Not even in my username, just in the surname field. The new portal ate it on that so hard, I wasn't even allowed to create a ticket to do anything about it.

Not as bad as when I was once issued a first.o'last@corp email address though ..

For me, it's some very simple things. Like being able to set the alt behaviour separately for left/right alt (so I can have the meta behaviour while still being able to type funky characters)

I don't think this is an issue the Pico has had. Regardless, the first reseller that came to mind (thepihut, UK) doesn't seem to have any issues selling me multiples at RRP.

He's been plugging away at this machine for a year and a half - the excitement is well-earned!

It's not unusual to effectively self-insure for shipping.

If insurance costs you more than lost shipments, it stops making sense to pay for insurance. If insurance costs less than lost shipments, it stops making sense for the insurer to offer you insurance at that rate.

Insurance works when the loss is disruptive to your cashflow. If I can't afford to absorb that loss right now, it may be worth finding an insurer that can. If I can afford to absorb that cost, it's almost always better to leave my money working for me, than working for the insurer.

If you're shipping in volume, self-insurance almost always works out better. You can bet amazon don't insure their shipments to you. If they take the potential cost of insurance, stick it in a pot, and dip into it when there's a shipping issue - that pot should never run dry. If that pot runs dry, it means insurers are operating at a loss, and they're not going to stay in business long.

I think that'd be the huge differentiator - you need that feedback loop that there's actual results/outcomes from your work.

If you just sit 8 hours a day effectively solving the world's most gruesome captcha, I wouldn't last long.

They really send a t-shirt. And if you're really good .. a hoodie [0].

You could look at it the opposite way around - someone's come up with a genius idea to do a bug bounty on a beer budget.

[0] https://english.ncsc.nl/latest/weblog/weblog/2022/i-am-on-th...

UDP has very low cost, the header is pretty much source and dest ports. For this low, low price, you get compatibility with existing routing, firewalling, NAT, etc.

Interestingly, where I am they take no money - and give the same advice. My partner just received the all-clear after detecting it early, following advice, and attacking it early. And the doctors got paid the same as if she’d never existed.

It took me a moment to put this together too, so to be clearer - the wireguard endpoint is in docker, so you're adding the docker bridge to your vpn. So DNS is handled by docker, just as containers can already address each other by name - you're on the container network with them.

Are there any signs of this souring?

During the PPC-Intel transition, Adobe compatibility was almost a running joke. Along the lines of the infamous "You can always count on [..] to do the right thing, after they have exhausted all the other possibilities] quote.

I was surprised at how quickly Adobe adopted aarch - it didn't feel sour.

I think this mirrors my take.

Not a fan of the current IP regime, and I'm all for IP activism.

I don't think the IA is the right place to fight it. It is a valuable resource, which is why it needs to be insulated from the impact of activism.

The US often just says 'AM radio' to refer to the MW band, because they don't have commercial broadcasting on the LW band, so there's no need to disambiguate. In the UK we usually specify LW or MW because both bands are in use for 'AM radio' (for now ..).

Same way we just say FM for the 88-108 broadcast band. Were there two FM broadcast bands, we'd need to give them different names.

They always had other methods. Droitwich is more akin to a troubleshooting step - if Inskip is quiet but Droitwich is loud, there's a problem with Inskip. If every site falls quiet at the same time .. well on to the next step.

It's a bit like losing communication with one host, and pinging another to see if it's you or them - the 'other' isn't loadbearing.

People who can’t see their colour TV pay more than people who can’t see their B&W TV.

Oh to be a a fly on the wall when the inspector has to explain the difference to a blind person.

I think it made a lot more sense in the past. The license is set up so it’s a consumption based tax rather than taxing everyone. So only people with TVs paid TV tax. If colour increased the costs, only people consuming colour paid those increases. I imagine it made much more sense before consumption was ubiquitous

> When she asks TJ about what happened, she says he says: “Why me?”

That's the line that turned my stomach. I think that's where it really sank in just how not-dead they're talking about here.

I'm against the death penalty - I do believe there's times it makes sense, and I certainly believe there's crimes worthy of it. But I don't trust the state to make this determination with 100% accuracy - and anything less than 100% means we have to make the choice between not giving the death penalty to those who do deserve it, or executing those who don't deserve it.

It's not unusual to hear stories of people being found innocent after decades in prison - and every single time it hammers home to me that they could have been pardoning a grave.

I suspect it only looks like overkill in the context of the simplest possible example.

Once you start adding things like pre-inst, post-inst scripts, binary redirections with update-alternatives, I suspect the complications start to pay off.

For 1), it seems clear that there's a heavy overlap between Jeff's market and Elecrow's, and it's difficult to see that as a coincidence.

If someone cloned both Shaq's voice and Jeff's, and used them to endorse sneakers - I think it's a fair assumption that Shaq would see this as a business risk, and Jeff .. I'm going to go out on a limb, and assume he'd probably find it hilarious. Using Jeff's voice for sneakers would be more akin to your example of finding a midwestern voice with a useful corpus. Using Shaq's would be a much more obviously targeted appropriation.

What we're looking at here appears to be exactly this scenario, except this is Jeff's niche, not Shaq's. Using Shaq's voice for SBCs and related products would feel quite absurd - using Jeff's feels like a much more obviously targeted appropriation.

I was going to say it'd be easier to have a single script, eg

    #!/bin/sh
    busybox $0 $@

and then every command required could just be a hardlink to the same script, instead of replicating it over and over again for hardcoded command names.

Then I realised the whole point is to posit a world where $0 doesn't exist, and we're not allowed to be clever about it.

You can't really send anything back, they're junk sender addresses. You either send btc to their wallet, or you don't.

(Already had this thought process when I was getting so many of these, I wanted to invite a bidding war)

I believe the biggest increase in security since 9/11, is that passengers are no longer expected to sit down and behave.

Pre-9/11, the expectation was you don't draw attention to yourself, wait it out, you're going to have a long day and a story to tell. Post-9/11, the expectation is you fight for your life.

Better cockpit doors and access hygiene probably come second.

You can fire, there is a process, and this wasn't it. It's that simple.

There is a huge difference between not being able to fire people, and not being able to arbitrarily fire people on the spot.