An eletric heater powered by an old #bitcoin miner, with a meshtastic node embedded in it. It uses #meshtastic to bounce data to a gateway to submit PoW. By default, that could go to the person who built the heater. The user just plugs in the heater without ever having to deal with any of this, nor connecting their electric heater to their wifi. Then they get a small check in the mail each year for running their heater. If the customer is technically savvy and interested in obtaining bitcoin, they could reconfigure the heater to mine for them.

#meshtastic users/developers: 1. How often does an OTA uodate render a node non-functional? 2. What can we do to improve reliability?

I need to get this yard/garden work done so I can get back to #Signet. I had to use the new (unreleased) build to import my Keepass database to a new Signet. Not ideal. 🫤 If I can get the Mac- and Windows-specific updates done, I can get this merged in and cut a new official release.

OK, I'm looking for some help from a fellow lnd node runner. Problem 1: My comnection to my peer keeps dropping about every 3.5 minutes Logs say "pong response failure" and "timeout while waiting for pong response -- disconnecting". The error in the peer's log says the same. That it also had a timeout while waiting for pong reaponse. I can reconnect with no problem at all. There is not any network issues such as packet loss (see notes on the pcap below for the evidence to back this up). Tor is not in the mix for this test. I am able to sends sats if I do so quickly after connecting to the peer. So it seems like things can work properly if the connection issue can be sorted out. I took a pcap of a connection, transaction and disconnection. Near the end, I see the client (node which initiated the connection) just absolutely slamming PSH,ACKs to the tune of 37 of them in just under 0.001 seconds. Then it sends a TCP Retransmission 0.006 seconds later and gets an ACK 0.036 seconds later, which is a perfectly reasonable response time. The next batch is some TCP keepalives and keepalice ACKs. Some PSH,ACKs and ACKs in sub ms response time, followed by a retransmit and and ACK from the other side. Finally 2 more keepalives and Keepalive ACKs in 0.012 seconds and then we get the FIN,ACK from the client followed by the RST,ACK from the server (remote peer to which we connected). The FIN,ACK did come 5 seconds after the last ACK, so I feel like the server should have responded sooner, but at the same time I don't feel like a 5 second lag should cause a connection to be dropped and no attempt to ever be made to connect to it again. Also, these blitzkreigs of packets within 1ms is absurd. Any ideas on where I should look next? I guess take pcaps on both sides and compare them? This is absolutely brutal. I wouldn't expect most sysadmins to go through this much trouble to track down this issue, let alone any normal human be expected to do so.

If anyone wants to do some coinjoining, now would be a good time. It looks like the miners are getting bored. 😝

It's been a month and a half since the JFK assassination files were released and I haven't heard anyone pointing to what was in them that took this many years to finally be made public.

National Archives

JFK Assassination Records - 2025 Documents Release

March 18, 2025 Release In accordance with President Donald Trump’s directive of March 17, 2025, all records previously withheld for classificatio...

The year 2050 is closer than the year 2000. Yeah, I bet a lot of you gen Xers are probably feeling pretty old right now

I remember a short semi-parody of "industrisl" music which was sampled from a bunch of heavy equipment: grinders, specialized manufacturing equipment, etc. I thought it was by someone like chin guy, or chin dude or something. No I can't find it. Am I hallucinating? Does anyone know what I'm taking about? Including me?

Oh man, this new case design is 🔥 I still need to adjust the tolerances of the sealing lip, but it's already very nice.

This is a brilliant pun that will be lost on most Americans.

Anyone on here still have an X account? I'm trying tonget ahold of Matt or Jay, but the only contact info I have is Twitter. I want to email them about my Meshtastic Solar node project.

About Us… – hackspace.io

The parts for the #solar #meshtastic node came out to $224.78 to build one unit. My node covers at least 7 square miles in a urban/rural area with lots of trees and the antenna is not above said trees (or buildings for that matter). A better antenna position would greatly increase this range. Now that I have the spreadsheet, I'm going to reach out to the person at hackspace.io who said they'd host my writeup.

Well that's disappointing. I reported that the LNBits error message that says "server is still in the process of starting" doesn't say which server is still in the process of starting. No, it's not the LNBits server that they're taking about there. A LNBits dev closed it as "not in scope"

GitHub

Improve error message for non-developers / new node runners · Issue #3120 · lnbits/lnbits

When I try to connect to a peer using lnbits, I get an popup in the UI informing me that an error 500 has occurred. The log had the following error...

They're not even willing to add 4 characters to a log message to help new node runners troubleshoot problems. 🙁💔