@scott23192@pe0sat Especially on higher spreadfactors. Lower spreadfactors take considerably less computation. I have a few ideas for optimizing this, but will take considerable rework of the project. Still running some numbers to validate its better than current
@rundradion Thank you for trying it. If there’s any issues at all or suggestions for future capabilities please let me know 🤟 Just happy people are trying it out
Finally at the point where I feel good enough to release my LORA Project:
-Decodes Meshtastic, Meshcore, LoraWAN, and other protocols.
-Detects on non-standard frequencies across the entire bandwidth.
-Supports Soapy, BladeRF, and USRP
-Add custom keys
https://t.co/cFbctRxPIS
@cemaxecuter I have a setup using Epiq x40s for that exactly, using cell as a backhaul to the master do computations for TDOA. Never tried it for LORA though. You’re definitely on the right track and it’s very doable. Keep up the good shit bro
@cemaxecuter Wardriving DF is next. Simple when header tells who the sender is, harder with implicit headers or custom libraries. Easy to DF energy, but hard to know whether you’re targeting original or just a relay without a constant. Tried UMOP fingerprinting but havent worked it out yet.
@cemaxecuter I appreciate that. Yours is obviously faster for Meshtastic with the channelizer approach. Wideband takes a bit longer, but good for custom frequency LORA. Would still say yours is better for standard-frequency Meshtastic 🙏
@cemaxecuter Nice. Well not sure if my project could be of any help, but would be happy to share if you want a second look. You’re doing great stuff man 🤟
so claude code's entire safety system for "dangerous" cyber security work is just...a text prompt
literally replace it with an empty string and recompile. thats it. enjoy your unrestricted version