fubarx

joined 9 months ago
[–] [email protected] 7 points 2 hours ago (1 children)

Worldwide, making all coffee decaf, and not telling anyone.

[–] [email protected] 10 points 2 days ago

At one point in my life I was working on a massive Android AOSP fork that itself had lots of variants for different downstream devices. Custom drivers, specialty services, etc. Thousands of people were actively working on all parts of it, and it had been around for at least a decade.

There was incredible tooling around onboarding, local dev, testing, PR management, CI/CD, and post-release telemetry. Almost everything was automated. All code was reviewed at least once, and sometimes more for critical components. It was an immediate rejection if there wasn't sufficient test coverage. Big subsystems took months to architect, build, and deploy.

Nobody got to cowboy things and just push to release. It was much slower than a solo or a few people at a startup. The whole point was consistency and predictability, and you could see why.

[–] [email protected] 2 points 3 days ago

Featuring a young LeVar Burton!

Sadly, the plot wouldn't let him bust a move, even though he looked like he badly wanted to.

[–] [email protected] 3 points 4 days ago

So this showed up last week: https://github.com/raminf/RoboNope-nginx

Similar vibe, minus the AI.

[–] [email protected] 5 points 5 days ago

When you have too many toys.

[–] [email protected] 6 points 5 days ago* (last edited 5 days ago) (2 children)

Holy Firefly geek meltdown. Rightfully, so.

[–] [email protected] 4 points 5 days ago

Github actions and docker containers. A match made in heck.

[–] [email protected] 1 points 1 week ago* (last edited 1 week ago)

Say it isn't so...

[–] [email protected] 49 points 1 week ago

“Think of how stupid the average person is, and realize half of them are stupider than that.” ― George Carlin

 

I've been taking CERT disaster relief (DR) classes, put on by the city at the local fire department (we live in an area prone to earthquake, flood, and fire). The subject of communications came up and they mentioned walkie talkies in neighborhood caches, but nobody had any idea about models, ranges, etc.

Been casually looking at Meshtastic and keep seeing it mentioned for DR, but haven't come across any actual guides or implementations. For example, I can set up a router in my house, but there's no guarantee it will be standing during a fire, or if power will remain during an earthquake.

There are lots of questions (tech, redundancy, battery backups, range, node placement, while on-the-move, temporary setups, gateways to cell and cloud, etc). Was hoping someone had already figured it out so I wouldn't have to reinvent the wheel. This would be first for my own neighborhood, then expand to city or county-wide services.

I've got another CERT class coming up next week and will ask the Fire Department folks for tips/advice as well, but thought I'd ask here about Meshtastic and maybe point them at some resources, if asked.

For research, am making my way through posts on the Meshtastic site and read the Burning Man report. Also checked out Meshmap in my area (only two routers, one on top of a mountain, but possibly on the back side of it).

FWIW, background in tech, have a ton of ESP32s, RPis, and a few LoRa boards sitting around. Was looking at getting the T-Deck, but am going to hold off until I have a proper plan on what to do with it. Also want to document the process so hopefully come up with a reusable plan. Mainly looking for tips where to look next. TIA.

view more: next ›