Wow, it seems like I just had a #RAKWireless current sensor go bad after about a month of use.
It was impeding current flow (thus stopping the battery from being charged) and when I swapped it out for a replacement, the replacement worked just fine.
#meshtastic #MeshRadio #mesh #radio #electronics #repair
Dr. Hax
Dr.Hax@hax0rbana.org
npub16v82...eqha
Cypherpunk. Infosec veteran of about 15 years (vulnerability research, exploit development and cryptography). Cypherpunks write code. :-)
Signet maintainer. Self-custody your passwords... in hardware! https://hax0rbana.org/signet
Want to see wider adoption so Bitcoin can be used as digital cash and not just an investment vehicle.
XMR: 44RDkTFmTeSetwAprJXnfpRBNEJWKvA5dBH5ZVXA4DofgoZ9AgjyZdSa2fo7pMD3Qe3pdKga8X22y3Lyn1xYde5kPQPzVUu
An #open #hardware #meshtastic node with hot swappable MCU. 👀


MY000008
Hot take: having firefighters is a worthwhile thing.
#taxes
It is a happy day. The last parts to build a bunch of solar nodes have arived.
I've been unfollowing people who just post tropes like "bitcoin is the hardest money ever invented". If that's all you have to say, I don't need you in my timeline.
Same for the OP_RETURN "debate". Look, if you don't like the way the software works, run different software, or modify it to run the way you want.
Or you can whine about it and call people names on social media. One of these is going to have a lot bigger impact than the other, and if you can't figure that out, you're getting yeeted from my timeline. I make the rules here.
Scary!


The "Urban Assault Vehicle" is the best mix of "Rollin" by Limp Bizkit.
RIP DMX 🪦
There's no sense crying
over every mistake
You just keep on trying
'til you run out of cake..
...and these points of data
Make a beautiful line
We're out of beta
We're releasing on time...
Look at me still talking
While there's science to do
When I look up there
It makes me glad I'm not you
I have experiments to run
And there's research to be done...
"Still Alive" by GLaDOS
I'm going to be taking a step back from some things. I've got too much gong on every day.
Not sure what will get cut, but something(s) will and I'd rather make a concious choice about it than have things come arbitratially crashing down.
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.
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.
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...
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?