6,920 karma · joined January 1, 2010
The one exception is AI. Historically, redirecting charitable funds towards AI safety tends to starve or undo the rest of these efforts, which is why I’m so disappointed by many EA institutions dropping other initiatives to put their eggs in the AGI basket.
X Wing: Wedge’s Gamble (1996) by Michael Stackpole shows the rebel alliance using similar tricks during the battle of Coruscant.
OpenPhil changing its name to Coefficient Giving, 80000 hours and bluedot and (to a lesser extent) CFAR dropping other initiatives and switching to AGI promotion… to my knowledge GiveWell is the only other big name that continues to advance other initiatives. Then look at figureheads like SBF committing fraud and begging for a pardon from the architects of the USAID shutdown… We begin to paint a picture of a community that’s (by and large) abandoned its principles for power.
I know the view from the inside is more nuanced, but I think it’s a reasonable association for random members of the public to make.
My critique of the EA community is that it’s myopic and unregularized. If you really think AGI is make-or-break for civilization, it’s completely rational to deprioritize side bets.
Double-check that this method actually works though.
Machine ID is used for things like dhcp leases, log rotation, etc. IPV6 addresses or transient MAC addresses are derived from it
could the author clarify what we should be seeing or what the point of this is?
The library is highlighting a few titles for increased visibility to ask, “would this pique a reader’s interest if they knew about it, or is this generally bad?”
Without this stage, the library would expunge more genuinely interesting titles.
I’ve always kinda felt the role of a library is for recall rather than precision
In a sense, sharing products in threads like this helps future people see what else has been done!
Agentic development tends to encourage siloed individualistic development, so a lot of engineers reinvent similar patterns from first principles. It’s easier to write your own new thing than survey other approaches, so you’re more likely to perceive good ideas as original to your session.
Another critique: the abstract mentions how their system allows for “branch[ing] a run at any event without re-executing the shared prefix,” but that’s only possible with very careful KV caching. Generally, rerunning inference from an earlier point still incurs O(n) input token cost and this paper is working at the wrong layer to see that. In this work, execution refers to tool calls but token generation is the expensive part.
Event graphs aren’t just the agentic foundation for $MY_HARNESS — they’re the working cognitive substrate, native to what our favorite toolcall gremlins actually consume.
(Looking for lead investors for our angel syndicate btw! DM me if interested)
In fact they say the raw file size of the demo splat was only 427MB, so maybe the 640MB/s was a statement about encode speed? Why write it that way instead of “this demo splat was encoded in 0.6sec” or even just “the time to produce the original splat took longer than the time to encode this video format”?
How are you reading that differently?
"functionally illiterate" is the brush that one paints with when describing people of opposing political viewpoint or lower socioeconomic status, for example.