GET https://safebrowsing.googleapis.com/v4/threatListUpdates:fetch?$ct=application/x-protobuf
probably tells google every domain you visit. but idk about this encoded req and res.
I looked at the code earlier when you mentioned it, it uses twitter's internal api, requires someone to have one (or probably more) twitter accounts to retrieve the tweets and save them, this could be built into some nostr relay, and it would technically not be hard, it would just need more maintanance than the average relay, and just like nitter's code when twitter changes something, so too would that relay
HIDING IN PLAIN SIGHT!
nobody knows your note is really just a dump of binary data
hiding any data in 32 byte hexadecimal keys allows to hide data in nostr in plain sight. using long lists such as follow lists may be optimal for hiding in plain sight.
echo "testing some values testing some values testing some values testing some values testing some values testing some values testing some values testing some values" | xxd -p -c 32
74657374696e6720736f6d652076616c7565732074657374696e6720736f6d65
2076616c7565732074657374696e6720736f6d652076616c7565732074657374
696e6720736f6d652076616c7565732074657374696e6720736f6d652076616c
7565732074657374696e6720736f6d652076616c7565732074657374696e6720
736f6d652076616c7565732074657374696e6720736f6d652076616c7565730a
forget Y2K even a leapyear + software bug can cause down time in π°οΈ internet #outage #newstr
https://image.nostr.build/7129d5e5fae5c198dea5ce4dbba52a2420c4bea44ca97570e58d9404730f7d8a.png