mej10

It is obviously not going to be until some really bad series of cyberattacks or a chemical/bioweapon attack before anyone takes regulation of models seriously.

They are _obviously_ (please convince me otherwise) going to be capable of carrying these terrible things out almost completely autonomously at some point in the near future, in potentially clever ways. Therefore we must, at some point, ban or heavily regulate them. Seems we should start figuring that shit out _now_, as progress has remained very fast and regulation and enforcement take forever on these time scales.

There was/is a game called Shattered Galaxy that was best described this way.

Several factions continuously battling over discrete territories. There would be calculations throughout the day that would give certain bonuses to whichever factions were winning.

Every territory had a field commander that could request people join that had leveled up certain types of units based on how the battle was evolving.

There was also a form of player controlled government in each faction that could choose bonuses and allocate resources to various battles.

It was really cool for its moment in time.

> I don't get the impression that they had a "ton" of money when they started.

Viaweb was PG's first company, which sold to Yahoo for $49 million in 1998. Just as an FYI -- I think PG/JL/YC are great.

For what it's worth, that is illegal in the USA at least. Genetic Information Nondiscrimination Act passed in 2008.

actix, cdrs, rusoto, cadence, diesel, futures/tokio, serde, chashmap, slog, postgres, criterion, r2d2, chrono

That isn't all of them but those are the main ones.

Interested to know what Rust was missing. I built an ad exchange last year and it has been great. I have been using nightly builds, mostly for access to async/await, and it has been very fast and stable.

I have had to submit a few pull requests to various projects along the way, but didn't find the ecosystem prohibitively lacking.

Cool! I am working on almost the exact same thing. Grats on shipping!

I wonder how enforceable that patent is.

I have also had many lucid dreams -- I used to practice lucid dreaming.

This is like a lucid dream but there is no narrative or control over what is happening -- only awareness. It is really most like being in the center of a river of thoughts, briefly experiencing them as they rush by.

Nope, though I am familiar with that, too. At least in my experiences with hypnogogia I have some "control" or at least a feeling of control over what is happening to some extent. Or maybe it is better to describe it as being a more sequential experience than the other one I am describing.

Maybe if one is to stay conscious during hypnogogia for longer than I ever have they would experience a similar thing? There just always seems to be some bias in hypnagogia steered by and experienced by my consciousness in first person. In the other experience it is really more like I am an outside observer.

I have become conscious during dreams that I would describe as "being in a river of disjointed thoughts and emotions" -- the experience is exactly like I was witness to the many thoughts being considered/happening in my brain rapidly and simultaneously.

It is much more intense than normal dreams and I usually wake up within a few moments, and there is never a narrative like normal dreams -- just an awareness of many concurrent thoughts in quick succession.

There is a typo in the first subheading: "Project Refrences"

We have, so far, only made a GraphQL endpoint for internal use. It has been awesome for quickly finding things in a medium-complexity database schema (30 or so tables, bunch of different relationships). It has become my preferred way to quickly find things in the database.

That being said, there are cases where a join between ad hoc subqueries is the best way, and GraphQL doesn't really offer a way to do that (though I don't see why it wouldn't be possible). E.g. arbitrarily combining two GraphQL queries that return lists where some field in one is equal to some field in another.

But in terms of replacing REST, where you have to do all of that anyway, it is far and away the better option (for ad hoc querying, at least).