Bones

@kauffj They are in the db when the asset is first published and spee.ch creates the Claim record; then they are removed from the db record when the record is...

I'll have to read up on GTM but I am interested in making this change. Off the top of my head, I am wondering if it will work with content...

I converted to an epic and created an issue to scope out the individual tasks.

note: we should also reverse the order of claims so newest are presented first. (@tzarebczan )

One option for caching, using redis: https://www.npmjs.com/package/express-redis-cache

@lyoshenka also mentioned https://varnish-cache.org/ which sits in front of the web server

one issue for caching, raised by @skhameneh, is that SSR of page may need user session data. This is currently solved by serving the site without a logged in guest,...

another issue with caching is that the same url (e.g. `https://spee.ch/xyx/doitlive.jpg`) could be one of two types of request: (a) a request from a user that wants to view the...

Rather than implementing a warning modal that would add a click to the publish user flow, I think this can be solved by (1) defaulting publishes to 'in a channel'...

We also discussed setting up a timer that would handle this every X seconds. The same loop could also manage doing tor check and blocked list update on a recurring...