https://ar.anyone.tech/MQnlj4RjTBOKRRVyHIReBp-EGcb2LJ-W_W79DlC0D0s#IUGUgoMT4...
got a funny different experience recently that's a small blocker for using the internet on my misbehaving phone-like device
i was excited to publish my first sha-256 git repository at https://codeberg.org/xloem/ev which happened a day or two ago. right now it's just a mitmdump/mitmproxy script for extracting EV charging locations and prices from use of the chargepoint or plugshare (git push pending on plugshare) driver websites (or apps if you can access the tls). it contained some unique code for processing my public mitmdump packet logs which handles the decoding errors from interwoven error messages and resumes. the handling code is very simple it just readlines() to the next line break and tries again.
[some mistake ..... :s :s [umm my public packet log uploads got blocked or something after publishing that. pretty quickly
i try to only use my phone's internet when public packet logging, so it has made it hard to use the internet. [--..
ohhh :D :s well it is true yes that it turns out these aren't "packet logs" and a better solution would be to log the tls data and instead do a filtered tcpdump pcap log. i didn't know hadn't looked, common situation, very happy to recover them at all.
but would fixing the robustness of the logging make my uploads work again...?
when i looked into the failing uploads it seemed like all uploads were working except for the indexing txs for my "packet" uploads. i tried to mention that to chatgpt during the debugging, the message didn't seem to get through, but af--