Why are we still stuck with 1 Gbps Ethernet on most consumer routers and switches?

Well, this looks quite interesting. I've never used a node-based editor before and I've been using Photoshop since the 90s, and haven't used much else so I don't know what I'm missing.

I took a look at the demo and at first glance, it looks like the current version is just a basic image editor. I don't see any options to add noise, blur, filters, etc.

Also, curious to know about the graphite fileformat. When editing an image, are the set of transformations, etc. suitable for version control?

We're in the process of refactoring a whole lot of code from the pre-node graph MVP implementation to the node graph version, while mainly aiming to avoid losing functionality in the process and not prioritizing new functionality quite as much yet. You can import or draw an image, though, and then right click in the node graph and search for certain effects and filters (similar to Photoshop's adjustment layers) and insert them in the chain of nodes. But to become actually useful, we need a bigger and more thought-out family of nodes combined with tools which automatically insert and update the nodes for you through the means of using the tools and doing lasso/marquee-style selections. Those are all a few months away on the roadmap, but it should be a lot more powerful and novel by then.

The file format will have its own built-in version control in the future, but I believe we are planning to use an ASCII representation so it could also theoretically be version controlled externally. The current `.graphite` files are entirely a temporary format. Once we finish the aforementioned refactor, we will design and implement a proper file format that ensures backwards compatibility (something the current files don't manage at all), it will be called `.gdd` (Graphite design document).

Mattermost is an opensource Slack clone.

Compared to Matrix/Synapse this is worlds easier to manage

I have no experience in what these systems look like when used at scale, only deployed for play, but I expect a simpler life with Mattermost

I love the fact that this exists, however my major concern is that because this is self-hosted, in the event of a dispute, the other party can claim that I forged the document. In such a scenario, how would I ever prove that I didn't?

When self-hosting it it's possible use merkle tree to ensure the documents integrity (similar to how git works with its commit hashes). So to forge one document it will require to change all document hashes after the disputed document making it impossible to cheat by the organization that is self-hosting it. This will be added into the project soon.

https://en.wikipedia.org/wiki/Merkle_tree

Alternatively I'm thinking about adding a third party AWS QLDB integration - QLDB allows to maintain an immutable, cryptographically verifiable log of data changes.

This looks useful for showing a demo to management folks. The fact that it's readily available just makes it even better for scaring them.

As a manager I bought and distributed these to senior ICs to demonstrate how much work someone could put into compromising you

That kind of depends on how your "management folks" react to "being scared."

Not everybody survives after telling unexpected or inconvenient truths to the monarch.