Do we have numbers on that other robot taxi?

persay

per se

I respect your opinion I just think it’s a little naive.

Under isos 27002, 90003, 25000, and 9001, and their requirements for software pedigree and sustainability, it’s just best-practice.

Is it ironic that you’re calling best-practice “naive”?

Based is fetch.

regularly use windows because we love modding the crap out of all of our favorite games and that’s just not feasible on Linux

Linux isn’t a game.

Yay! This means America will be cleaning up it’s fentanyl issue so we done get so much smuggled into our country.

Right?

takeover

As a verb, it needs a space. Here’s your tree.

European countries spend too much on their people to properly outfit a military as massive and bloated as America’s.

Can we start using “executed foreign nationals in international waters without proof, trial, process or even jurisdiction” yet?

Sometimes, an app can be an app and not some hosted web service mess.

Remind me of the recent source ownership issue? I thought there was a “thanks for all the community work over a decade and we want to participate; oops now we own it” story.

Appimages and flatpaks frustrate validation and thus break iso27002.

Anything else?

Just a page with the name of the project when I checked just now. Nothing else.

Look. Is part of the plan to build and distro an OTA flash for my ~9 echo flex models deployed out on the world? They have everything they need for interaction, as well as networking and Bluetooth beaconing.

a […] software

A software WHAT?

Its fantastic when you’re a few rungs up and already reaching back to help others.

Linux since 1.2.13, here.

Yes, self-hosters can be really focused on their own complex setups, and forget that they’ve become overcomplicated through years and iterations of rebuilds.

A new bucket to stash all those crabs, though, isn’t it.

Start the noobs a little lower on the complexity scale, so it doesn’t look like a mandelbrot just to get basic stuff. App installs on a basic host is totally okay, to start.

Teach and reinforce proper patching and maintenance. Teach man-pages at every turn: promote good ones and take a second look at the bad man-pages because, really, maybe they need updates. Reinforce the “look up before asking;then ask well” routine for discussions and seeking help. Be super-welcoming for good questions, even if the pre-work is “I checked the man page and it didn’t really make sense for that option”, and gently nudge toward a cursory search when even that’s missing.

We lost a LOT of mentorship after the dotcom bust, and we’ve not been great in the Lost Boy generations that followed. We need to make it easier to get help, and we need to encourage that walk-before-fly mentality.

And if apps can’t properly package their stuff so that the secure and safe usage is the easy usage, then we steer noobs around it. I’m looking at you, docker-fixated app ‘releases’ without adequate delivery and via channels that aren’t validated normally as part of the process. We need to be so much better at that.

the maximum RAW bit rate of this LoRa chip is 62.5 kb/

Sooo, 1998 “USR X2” dial-up speeds.

1.5mb is okay. 32mb we used ‘at’ to schedule (just so we’d get the mail when it was done) and go to lunch.

Keep in mind, when USENet was in full swing, we had entire institutions daisy-chained off a single 56k incoming line like a trunk line, from America to Vancouver through Edmonton and then Calgary. The best and brightest surfed binaries and alts like mad off that single chain.

It’s really usable if we tune our workflow.