𝗜𝘁'𝘀 𝘂𝘀𝗲𝗱 𝘁𝗼 𝗽𝘂𝗻𝗶𝘀𝗵 𝗱𝗶𝘀𝘀𝗶𝗱𝗲𝗻𝘁𝘀 𝗮𝗹𝗹 𝗼𝘃𝗲𝗿 𝘁𝗵𝗲 𝘄𝗼𝗿𝗹𝗱.
Here's a retired Royal Navy radiological weapons expert explaining how it's been used on foreign adversaries since the 60s:
Full video: https://youtu.be/v5Tn89I7uic
47 karma · joined June 1, 2010
𝗜𝘁'𝘀 𝘂𝘀𝗲𝗱 𝘁𝗼 𝗽𝘂𝗻𝗶𝘀𝗵 𝗱𝗶𝘀𝘀𝗶𝗱𝗲𝗻𝘁𝘀 𝗮𝗹𝗹 𝗼𝘃𝗲𝗿 𝘁𝗵𝗲 𝘄𝗼𝗿𝗹𝗱.
Here's a retired Royal Navy radiological weapons expert explaining how it's been used on foreign adversaries since the 60s:
Full video: https://youtu.be/v5Tn89I7uic
Neat syntax overall but it's not clear what it makes more succinct than the equivalent `elif` statements.
https://theguardian.com/sustainable-business/2017/jul/10/100...
What's costlier, the new stack frames plus conditional for a decorator or the `elif isinstance()`s in one function definition?
How does a programmer reference the correct function definition by name if they're using @typedispatch instead of `isinstance()`?
A lot of the proposed value-add seems like the authors aren't aware the built-in `type()` can dynamically modify class definitions.
Getting rid of `hex(id(self))` in `__repr__` is regressive UX.
@typedispatch seems like both a slow way of using 'isinstance()' and a FOMO C++ virtual function bloat.
Can we use asyncio to update multiple charts simultaneously / at arbitrary intervals?
Wouldn't it be better if Jupyter absorbed this API for its dashboards?
Imagine if Google Wave had a friends list similar to Telegram and each peer acted as a public cache for dead hypermedia.
Shameless plug for anyone who just wants their own IRCD: https://github.com/LukeB42/Psyrcd
Personally I'd lengthen the course with a Section "1.5" on the raw math topics being dealt with (Set Theory and Category Theory) plus ones the student will certainly bump into if they ever find themselves having to deploy MapReduce in production...
Enough energy enters Earth's atmosphere on days like this one to sustain 7 billion people plus the six-legged majority with room for human technological innovation. We're just not capturing each day's energy with even greater than 50% efficiency yet.
https://www.jstor.org/stable/43619013?seq=1#page_scan_tab_co...
It's a p2p caching proxy that also lets you edit web pages collaboratively in realtime over a LAN or the internet. It has a contacts list system and p2p chat functionality. This project effectively died due to lack of interest and I still have various security concerns about it (Should you break/reimplement Same-Origin policy or break/reimplement the TLS chain of trust?)
The main security concern is that because it decentralises HTTP in-place (existing URLs can now be looked up on an arbitrary number of overlay networks if the original URL isn't providing an OK response) it puts users at risk of malicious actors spamming overlay networks with browser exploits for popular resources like "news.ycombinator.com/".
I hope TBL and co converge on satisfying answers to these problems or constrain their design to not bother with decentralising existing URLs in-situ.
Code lives here: https://github.com/Psybernetics/Synchrony
Feel free to shoot me any questions.