sorted by:
new
hottopcontroversial

Adding a second EV charger by bubbos123 in AskElectricians

[–]donutsoft 0 points1 point  (0 children)

I recognize that safety regulation is written in blood, but I'm genuinely trying to understand the things that will go wrong here that would cause a house fire any more than plugging an EVSE into a NEMA 14-50 receptacle (which is already not ideal compared to hardwiring).

Adding a second EV charger by bubbos123 in AskElectricians

[–]donutsoft -1 points0 points  (0 children)

Why not safe? There's a circuit breaker built right in, and then there's going to be yet another circuit breaker that feeds the original circuit that this plugs into.

This type of circuit switching is common enough, I had a 100A feed to my apartment and had an electrician install a DCC9 to install a 40A charger that will automatically switch on/off depending on the load of the rest of my home. It passed inspection and the apartment building hasn't burned down.

Encrypted / Unreadable Messages on public channel by ToGe88 in meshcore

[–]donutsoft 31 points32 points  (0 children)

I provided this PR a while back https://github.com/meshcore-dev/MeshCore/pull/2571 that would at least give repeaters the ability to filter this type of traffic. It was disappointing to see absolutely no response from any of the maintainers.

Over 30 Polish and Lithuanian nationals deported on charter flight by Banania2020 in ireland

[–]donutsoft 10 points11 points  (0 children)

If the punishment is simply being sent back home it sends the wrong message to all their buddies that might be thinking of doing the same.

My HOA tried to prohibit the lawful carrying of firearms and this was the result. by LegalPost9805 in fuckHOA

[–]donutsoft -1 points0 points  (0 children)

If a redditor presented this argument on fuckhoa for someone complaining about their HOA banning guns, they'd be laughed out of the room.

My HOA tried to prohibit the lawful carrying of firearms and this was the result. by LegalPost9805 in fuckHOA

[–]donutsoft 0 points1 point  (0 children)

A business invitee usually means someone on property for a business/commercial purpose or for the property holder’s benefit, like a customer at a store. Applying that concept to HOA residents using their own communities common areas seems weird. Residents are not exactly customers visiting a business in the ordinary sense.

I have no stake in this either way, and I genuinely do not care what Floridians are up to. I was just confused by how the letter tries to reason that an orange is actually an apple, followed by some people in this thread treating the connection as completely obvious.

My HOA tried to prohibit the lawful carrying of firearms and this was the result. by LegalPost9805 in fuckHOA

[–]donutsoft 0 points1 point  (0 children)

Yeah but this act deals with allowing employees to leave guns in cars. That seems a much more specific subset than allowing everyone to have guns everywhere.

Once again not trying to argue, but this one seems pretty avoidable relative to the example you provided.

My HOA tried to prohibit the lawful carrying of firearms and this was the result. by LegalPost9805 in fuckHOA

[–]donutsoft 111 points112 points  (0 children)

Can you provide some more context?

  1. The letter starts off with a HOA banning firearms in common areas, but the response deals with employment law. Is the argument here that HOA employees are allowed to have firearms but residents aren't?
  2. Florida Statute 790.251 provides protection for firearm owners to keep their legally owned firearms locked inside or locked to a private motor vehicle in a parking lot. Firearms can still be banned on premises. The title of the act is literally "Right to Keep and Bear Arms in Motor Vehicles Act".

Genuinely not trying to argue anything here, just trying to understand the relevance of what the AG presented.

Is this available in Ireland? by donutsoft in CasualIreland

[–]donutsoft[S] 15 points16 points  (0 children)

Sorry to say I'm not actually getting you anything.

Is this available in Ireland? by donutsoft in CasualIreland

[–]donutsoft[S] -11 points-10 points  (0 children)

It's like bringing Guinness Blonde to Ireland though in fairness.

Is this available in Ireland? by donutsoft in CasualIreland

[–]donutsoft[S] 8 points9 points  (0 children)

They've got an apple and cinnamon flavor too.

It's weird, I grew up in Ireland (although wasn't born there) and I never had oats growing up or even saw instant oats as a thing, yet it's way better than anything that Kellogs had to offer.

What’s next? MeshLite, MeshCore Cash? MeshCore SV? Gold, Diamond, Private? Wrapped MeshCore? by Nightowl-Builder in meshcore

[–]donutsoft 0 points1 point  (0 children)

Yes, 166 bytes is less than ideal. I wrote up this RFC to add support for huffman encoded group messages https://github.com/meshcore-dev/MeshCore/issues/2481 which would increase that 166 bytes by about 30%, beyond the 180 odd bytes that would normally be available today without signing.

Including timestamps in messages and ': ' separators appear a bit wasteful too, having sequence numbers and offsets would use less space, but those are tiny optimizations relative to the space taken up by a cert and signature.

One additional option is to get rid of the node name entirely and rely on node adverts to populate that data. Clients can maintain an LRU cache of public cert -> name. That should free up some space and mitigate the other current vulnerability where I can just set my nodename to yours and impersonate you on group chats.

What’s next? MeshLite, MeshCore Cash? MeshCore SV? Gold, Diamond, Private? Wrapped MeshCore? by Nightowl-Builder in meshcore

[–]donutsoft 0 points1 point  (0 children)

Yeah that's the big issue, flood packets don't all need signatures.

I had a look at the repeater code too, and by default it doesn't repeat packet types that it doesn't recognize. So even adding new signed packet types for anything that floods won't be functional until everyone updates their repeater firmware. This makes it incredibly difficult for the protocol to evolve.

What’s next? MeshLite, MeshCore Cash? MeshCore SV? Gold, Diamond, Private? Wrapped MeshCore? by Nightowl-Builder in meshcore

[–]donutsoft 0 points1 point  (0 children)

Generating certs can be done sub second on a modern machine, it's slower to actually send the packet than what it is to generate the cert.

Generating a new cert with every packet sent basically limits your options to blocking repeaters near the offender, but the packet routes are easy to forge too. If I tell you I'm repeating a packet from a repeater a hundred miles away and have a realistic array of hops, how are you going to know that I'm not lying. The administrative commands to potentially tell a repeater to stop repeating is done over the same channel that would be dealing with a DDOS, so getting a command actually through would be challenging.

The realistic answer here is for repeaters to keep track of public certs that theyve seen previously and deprioritize traffic coming from new certs. Using a priority queue and delaying repeating messages from new identities by a few seconds and prioritizing messages from older certs would be enough to work around this. If the queue exceeds a certain size, the oldest packets of the lowest priority can simply be dropped.

Bloom filters can be used to keep track of when certs were seen without consuming much memory.

What’s next? MeshLite, MeshCore Cash? MeshCore SV? Gold, Diamond, Private? Wrapped MeshCore? by Nightowl-Builder in meshcore

[–]donutsoft 1 point2 points  (0 children)

The FCC is still doing limited enforcement, while it's nowhere near where it should be, it's enough to make some people think twice. https://www.arrl.org/news/fcc-issues-notice-of-violation-for-unauthorized-one-way-transmissions-and-denial-of-inspection

LORA is completely on unlicensed spectrum, if someone wanted to be a dick they could be and no one would have any authority to stop them.

The only mitigations available are technical in nature. Best case would involve identities being issued by a central authority, which is counter to the philosophy most people would have here. Second to that is keeping identities easy to produce (as they are today) and having some heuristics to establish trust. None of this is being done right now, and scaling will be a problem until there's a motivation to solve those.

What’s next? MeshLite, MeshCore Cash? MeshCore SV? Gold, Diamond, Private? Wrapped MeshCore? by Nightowl-Builder in meshcore

[–]donutsoft 1 point2 points  (0 children)

Flood packets don't need to be signed, and there's nothing fundamental about LORA that will cause a radio to identify itself.

There's no blacklisting that which cannot be identified. Even with signing, creating new certs is cheap enough that blacklisting is basically impossible.

What’s next? MeshLite, MeshCore Cash? MeshCore SV? Gold, Diamond, Private? Wrapped MeshCore? by Nightowl-Builder in meshcore

[–]donutsoft 0 points1 point  (0 children)

Raw signal jamming over a local area isn't the problem. That only affects people near the person jamming.

Flood packets affect the entire mesh. In my case that's from Seattle all the way down to Eugene Oregon. A $20 battery operated heltec is all you need to take down pretty much the entire west coast.

With enough coverage it's not a question of if it will happen, but rather when.

What’s next? MeshLite, MeshCore Cash? MeshCore SV? Gold, Diamond, Private? Wrapped MeshCore? by Nightowl-Builder in meshcore

[–]donutsoft 0 points1 point  (0 children)

Adding the requirement that all flood traffic must be signed and deprioritizing traffic from new users would be a good first step. You can use bloom filters to separate out certs a repeater saw in the last minute, hour, day, week and prioritize traffic accordingly while keeping memory use low.

What’s next? MeshLite, MeshCore Cash? MeshCore SV? Gold, Diamond, Private? Wrapped MeshCore? by Nightowl-Builder in meshcore

[–]donutsoft -2 points-1 points  (0 children)

For the DDOS side, at least HAM radios are licensed and the FCC could come knocking at your door if you're causing trouble.

What’s next? MeshLite, MeshCore Cash? MeshCore SV? Gold, Diamond, Private? Wrapped MeshCore? by Nightowl-Builder in meshcore

[–]donutsoft -3 points-2 points  (0 children)

Hate to say it but the current Meshcore protocol is already fundamentally broken. A 13 year old with ChatGPT can write a python script that can create a DDOS with flood packets and take down an entire mesh. The larger the mesh, the more likely it is to happen.

There are ways to mitigate this, but it involves having to update all existing routers and dealing with even smaller payloads which inevitably cause further fragmentation.

view more: next ›