for text search in postgr5esql, try rum index from postgrepro.

https://postgrespro.com/blog/pgsql/4262305

we run wg, star topology over port 443/udp with a specific ip in the center. never once had an issue on the road.

i think of wg more as point-to-point, encrypted network interfaces cards than a vpn.

That's what a vpn is - a virtual private network.

You can make a private network by adding more network interface cards and wiring. If you do it with software instead, it's virtual.

nice start. i signed up. looking forward to mobile version.

some observations:

items -> stacks, items -> folders, folders -> stacks, stacks -> desktop. each item can only be in single folder. copies of items can go into different folders. drag item to copier machines to duplicate.

Thank you :) Did you like the wireframes for the mobile version ? Is that the way you would imagine it ?

I’m not sure what you mean by Stacks … and copier machine ? For me an item can be copied and pasted anywhere.

I THINK they mean that once you move like-items they auto group into stacks?

Also I THINK they mean, create a little copier machine icon where you can drag items to and out pops a copy of it.

Basically, extending the " physical environment" aspect of this app. I actually quite like both ideas, but for the stacks could see things getting accidentally grouped too easily. So maybe some friction to auto grouping.

Hmm I like the idea of stacks I must say. In fact replicating something that’s very real in the physical world. And a Copier machine ok I guess I see the idea. So you could put more than one item in there at a time, I guess ? Otherwise not much point, no? It’s like a temporary place to put stuff you’re moving around. I like the idea.

Thanks !!

could you elaborate on pg not really having matviews?

Materialized views in Postgres don't update incrementally as the data in the relevant tables updates.^1

In order to keep it up to date, the developer has to tell postgres to refresh the data and postgres will do all the work from scratch.

Incremental Materialized views are _hard_. This^2 article goes through how Materialize does it.

MSSQL does it really well from what I understand. They only have a few restrictions, though I've never used a MSSQL materialized view in production.^3

[1]: https://www.postgresql.org/docs/current/rules-materializedvi... [2]: https://www.scattered-thoughts.net/writing/materialize-decor... [3]: https://learn.microsoft.com/en-us/sql/t-sql/statements/creat...

The pg_ivm plugin adds incremental updates to Postgresql materialized views:

https://github.com/sraoss/pg_ivm

Though I don't know how well it works on a write-heavy production db.

As somebody who implemented manual incremental materialized tables using triggers, yeah it's pretty dang hard to make sure you get all the edge cases in which the data can mutate.

amen.

Fast is fine, But accuracy is final. You must learn to be slow in a hurry.

        - Wyatt Earp

the link to RFC is broken:

    https://github.com/universal-tool-calling-protocol

yep, seems the big guys running out of ideas, to some degree.

i recall from years ago a site index url could be submitted to google. creating that index took some work.