⩖ powrelay.xyz

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.

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

🤣

https://x0.at/P-tB.jpg

https://image.nostr.build/a0a4204b9dde6d4061b048e26ce4a02211e82901e344577df6af18c993554f56.png except there no central server or website like physical flea market setup #torrent #p2p nostr gossip channel #dex #p2sh #swap #howstr #maker orders #AMM #LP #UTXO #atomic avoid fake EVM chain DB servers

Vão dormir bando de desocupado 🤨

i wonder why everyone is implementing captchas and rate limits on web request basis these days its not like bots are efficient web scrapers. nothing new there. they are very slow for doing web requests. traditional scrapers are much faster. so the reason must be that some entities are running much more traditional web scrapers these days. is someone selling extremely cheap bandwidth to some entities, which can then consume all upload of servers or what the fuck is the problem? or is someone using scrapers that do micro requests to servers' dynamic resources to consume their cpu?

EXECUTION TIME CODE SYNTHESIS: SOFTWARE 3.0 With first computers (software 1.0), rendering text was slow. Processors were barely able to render text on screen. With exponential rise in speed of CPUs, rendering text became very fast and took only milliseconds, then sub milliseconds, and even sub microseconds. Then developers noticed: rendering text is so efficient, we dont need to focus on execution time performance anymore. Lets shift our focus to improve development time efficiency! This was the start of next phase in software development (software 2.0). Now rendering text was fast, it took only sub microseconds, but due to shift in focus, soon it took milliseconds, then seconds, and then multiple seconds. We are now living year 2025, software has become so slow that rendering text in modern applications takes multiple seconds from initial request to screen. We live in age of modern web frameworks. Its time to double down with the development time efficiency with birth of software 3.0! By introducing execution time code synthesis, software 3.0 further improves development time efficiency on cost of execution time performance! Execution time code synthesis is real time function synthesis based on abstract logic, or software interfaces. If you are familiar with object-oriented programming, you already know what is an interface. Interface is an abstract class definition. It only defines what functions exist and their parameters and return types. Software 3.0 is all about interfaces. An AI system is then used to synthesize these functions at execution time.

using this 27 lines long interface, mistral synthesized 79 lines of working code with single shot, zero errors.

i dont really report any bugs in github. just try their registration captcha. nostr:note1zp2ags59tlxf2f6kexlv0d46x7d9jlcetf8pyppavq0hewpe9kcqj9a83r