1,142 karma · joined October 11, 2015
Isn't that kind of orthogonal to the question? I can envision both high or low trust societies that could have problems with required 3rd parties attached to personal property.
Even the most well intentioned and highly trusted 3rd party is still susceptible to malicious attacks, or just incompetence or plain old accidents.
I would guess that some other part of the app doesn't even use the constant at all, and just hardcodes "Active" as a string on its own. Maybe taking the value of a dropdown from the UI and never mapping that back to the actual constant.
There's room for a lot of punctuation on the same layer as the alphabet, plus support for ctrl/alt/F-keys. I find it great for working with ssh.
It reminded me of Wastl's other big puzzle collection (Synacore) which also had a big emphasis on implementing a VM to host further puzzles on top of.
I wonder if we ever start to see application-specific biocomputing systems integrated into server farms, we might really start calling our servers "livestock".
toot
Back when I was working in Processing a lot, I could probably have whipped up something decent in an easy weekend. If I wanted to have more complicated features like flood fill, cutting/moving regions etc, I might need an extra day to figure it out.
If all you want is a bare minimum scribbling lines in a limited palette, that could probably be done in a matter of minutes.
I had a lot of fun early in my own education following along with his guides. Coding Train looks like another great resource, thanks for sharing it.
I'd love to see a kind of local consensus/approval paired with distributed moderation to tackle the question of whether a user-agent should load/render any given asset.
Any client wanting to introduce a new avatar/shader/other asset to a session should go through a "proposal" stage first where the other peers can briefly inspect the metadata (polycount, moderation signatures, maybe even lightweight code analysis for scripted objects, etc) before signaling whether they intend to render it or not.
This gives participants (or rather, their user-agents) a chance to vote on whether or not an asset fits within their collective performance budgets, or if they trust a script to run without degrading the experience.
Personally, I'm of the opinion that we need a new kind of "browser" entirely; where the modern browser is focused on the traditional client-server document/application delivery and runtime, a "true" metaverse client should focus on p2p real time (or at least synchronous) shared experiences in an extensible compute environment. Not just 3d/VR either, it should be possible to connect to a session that's just a basic text or video chat room, then scale it into a 3d session.
There's also the matter of content hosting and distribution, I'd love to see native integration of IPFS or something like Bittorrent's DHT for p2p content-addressed file sharing. Popular scripts/application components and assets can be shared across the entire network, and peers can share their own personal content (avatars, applications) directly in active sessions.
If you'll indulge me a bit:
Matrix provides an extensible platform with identity and a shared, consistent, timeline of events. (You can also maybe get this with something web3, imagine a per-session blockchain somewhere between SSB and ETH)
With a consensus timeline, you have a shared history, and thus a shared reality.
On that timeline you can use extensible protocols to introduce assets, scripts/apps, and post events/messages.
Scripts all run inside a deterministic, message oriented compute environment, and the state of this environment gets checksummed and updates in lockstep for all peers. A new peer joining a session can either load a full state dump or just replay the event log to catch up.
For ephemeral/real-time data, like player look/point directions or video/voicechat, streams URIs can be posted to the log in a standard format.
A typical 3d interaction would start with two or more users connecting to each other, post messages announcing their preferred avatars, messages introducing an application package that supports 3D positioning and collision resolution, then loading an environment. Popular suites of code and assets can be bundled up and distributed with the browser and on the DHT.
Each user can have a set of public keys that represent moderators they trust, and require that each new asset be signed, or else allow "self-signed" content from other users at various trust levels, or just be open to everything.
I really feel like all the right ideas are floating around to build a truly p2p, personally liberating, extensible engine for synchronous shared experiences. Putting it all together is the hard part.
I seem to find that this is still the best way to communicate.
It'd be interesting if we did end up with three live chains though, probably not sustainable.
I don't even care that much about torrents or geo-locked stuff, I just trust them more than my ISP.
Setup was incredibly smooth and straightforward.
IIRC Mozilla also re-sells Mullvad's service under a name like (IIRC) FireFox VPN, which, last I'd heard, was still the only way to directly fund development of the browser.
In addition to authentication, I imagine they could also be used to double-check expiration dates or as a last-ditch effort to notify consumers in the event of a recall. Being able to precisely identify exactly which factory and batch any given pill or other edible item came from could be very useful in some cases.
I do think that some kind of "embodiment" or at least the addition of some kind of structured semantic model on top of/in addition to the raw token/vector embeddings is probably going to be necessary.
I am interested though, in how much of that internal/semantic understanding can be "emulated" by a sufficiently rich text model over the course of a conversation. There was an interesting article a little while back about improving GPT-3's (IIRC) performance on math problems by structuring the prompts so that it would describe working out all the intermediate steps in solving the problem.
I do suspect that whatever additional pieces we need to reach real general AI, the first really convincing examples of it will come not from looking at the architecture of the raw model, but at how it can be prompted to generate a believable accounting of it's own internal states over the course of an interaction.
I don't think LaMDA is sentient, but it does seem like we're quickly reaching a point where language models (if not now with LaMDA, then in the near future) are able to combine the right prompt along with a chat history to convincingly simulate it.
On the other hand, if I wish for a friend, and a friendly person pops into existence, we may have some harder questions to answer. Is it possible/meaningful to distinguish the status of the "friend" from the status of the fairy dust?