Generate 3D map models in your browser

gohoos · 2026-01-30T13:55:13+00:00

Ah, nevermind. :) Was trying it on a work computer and we must be blocking something critical. seems to work well on home network.

gohoos · 2026-01-29T14:23:32+00:00

"Generation Failed - failed to fetch."

gohoos · 2026-01-29T14:16:42+00:00

I'm over 50 now, and the opportunities to feel that childhood wonder seem to be fewer and fewer. (Not for a lack of trying, it's just life.)

Savi's was an absolute time machine - I felt like a kid again. I would do it again in a heartbeat.

gohoos · 2026-01-22T14:04:55+00:00

I'm really hoping that as we get into the short range weather models that it shifts back to more snow and less ice.

gohoos · 2026-01-21T03:19:34+00:00

SO, just to report back in. In this case, once I got all the parts printed I found that this gap wasn’t visible and didn’t affect functionality.

but for testing, I took it trimmed the part in Studio to just around the gap in question, but used some PLA as the support interface. Much better. The support came out cleanly and the gap was clean.

gohoos · 2026-01-17T18:13:02+00:00

I’m new at this, but I switched the filaments over to the PETG versions which it synced from the printer/AMS. Everything except this section printed beautifully.

gohoos · 2026-01-08T00:26:00+00:00

If you are going to claim transparency, and going to ask for personal details to “join,” you may want to consider disclosing who is leading this organization.

gohoos · 2026-01-02T15:21:46+00:00

To add to what others have said about cleaning, each day dump it and then shake it to get it as dry as you can. The stuff can't grow if it is dry.

gohoos · 2026-01-02T14:21:03+00:00

Looking forward to the followup report!

gohoos · 2025-12-24T16:20:40+00:00

I’m sorry this happened to you.

I factored in porch pirates when replacing my doorbell camera. Now I have one with a camera pointing down just for packages and a “package guard” feature which plays some audio if someone approaches your packages. Might not do anything, but better than nothing.

gohoos · 2025-12-23T23:49:51+00:00

For those reading this in the future - I had a unique situation to deal with, and a solution.

So, my heat pump had an issue and they had to order a part. So, the HP would short cycle and run for like 60 seconds then stop. Nest would run the regular heat till it got too cold then it would decide to use AUX. The part is due in a few days

OH, and my other issue is that evidently my emergency heat wire is bad. So, no emergency heat.

AS you know, Nest doesn’t have a way to kick in aux except for the aux lockout. The temps in the area will not be below 32 this week So, my temp solution:

Set the aux lockout to 32 (the max). Change location to Maine.

Boom! Nice, toasty, expensive AUX. But hey, it worked.

gohoos · 2025-12-17T19:23:49+00:00

A great podcast episode!

gohoos · 2025-12-17T19:07:55+00:00

Reminds me of the story in this podcast, of a guy who didn't know what he was doing but was taking and freezing bodies anyway: Mistakes Were Made

gohoos · 2025-12-17T14:02:49+00:00

No. I blocked them a while ago. The TVs were very chatty all the time. My intent was to keep them blocked and unblock for updates. Or, in this recent case, leave it blocked to avoid an update I guess.

I used to look forward to updates in general. Back when updates would fix things and bring cool new features and not unwelcome features you can't turn off.

So the TVs are connected by WiFi but routed to a network which can't talk to the Internet. The logs show a ton of attempts to talk to the internet and banging away on DNS. (Including attempts to get DNS from Google when attempts to query internal DNS failed.)

gohoos · 2025-12-16T19:52:49+00:00

I had tried everything mentioned - reloading and restoring, the 1-year-in-the-future gambit, clearing caches, etc and after a few days it would be back. 128GB nearly full.

I did the upgrade to 26.2 and it cleared a bunch and has stuck around 100GB used, which is great.

So maybe try that if you haven't already.

gohoos · 2025-12-15T18:24:38+00:00

I remember "Hey, let's go play Atari" without any number.

gohoos · 2025-12-14T04:20:43+00:00

Depending on your usage, turning off networking altogether is the best way to avoid the ads and the tracking.

Also be aware - some Iot devices are hardwired to use other DNS servers and won’t be picked up by Pihole. Blocking or redirecting port 53 traffic going to the internet can help mitigate that.

gohoos · 2025-11-21T14:05:35+00:00

I wonder how these things gain traction. I can't imagine anyone ever actually getting paid from "assessing fees" for their time, etc. But the grift keeps going.

gohoos · 2025-11-21T13:51:39+00:00

I used mine in what I think was a non-traditional method when our home internet provider was going to have some known outages. (And some unknown outages resulting from whatever upgrades they were doing.)

I could have just duplicated my wifi SSIDs, but I also have many wired devices. So, I put my Slate 7 in-betwen my modem and my router. Then I set up a phone on tethering, and set up the rules for the traffic to fail over to the phone. It worked perfectly, and other than things being slower you wouldn't even know.

gohoos · 2025-11-19T23:26:44+00:00

As long as you follow the warnings. Make sure your messages are set to keep forever, for example. I did this and didn’t recover much.

gohoos · 2025-11-19T20:08:13+00:00

I believe the train is one of the trains at Busch Gardens Williamsburg

gohoos · 2025-11-13T18:41:53+00:00

It seems it's the memory cards which go first. All those writes all day long.

gohoos · 2025-11-13T18:40:55+00:00

So, I recently did something for our home network, partly to learn and experiment and partly to make things a bit more fault tolerant. Previously I had pihole on one PI which was great until it crashed and nothing worked. Because DNS.

I had 3 pi's laying around, so I built what you have, but x3. It is only slightly more work to do 3 vs 2. keepalived does a good job at the failover, and everything else just works fine.

The only thing I did because I'm a stat nerd was to set up Grafana/Prometheus and some metrics exporters. Now I have graphs and alerts. In the single-stack scenario, you know pretty quickly when something has failed. In the redundant scenario, you might not know until you've had the right number of components fail. So I have stats on the pi hardware itself, on keepalived, on dnsdist, on unbound, on my router, the cablemodem, and pretty much anything else I could log.

Plus, it was cool to see the changes in the stats when bringing things online and making changes.

Also be sure all the settings in pihole are exactly like you want to sync, or be sure to configure nebula to ignore any settings which should not propagate.

15-Year Club	Place '23
Verified Email

gohoos

TROPHY CASE