1,220 karma · joined September 28, 2011
You've got some really excellent algorithms and tools in WBT, I've used them to shortcut some obnoxiously long lidar/pointcloud processing with other packages.
I'm not sure that this is "less complicated" than the linked tutorial though, but some great exploration for someone who knows a little more ;)
This doesn't seem like artists controlling their IP, to me it seems like another method of sales that lets them tap into essentially a pineapple fund. Those who made money in crypto, sloshing around the excess, making it look bigger and bigger.
We can test this.
```sql
create role data;
create role api;
create role bob;
create role alice;
create schema api_v1 authorization api;
create schema data authorization data;
set role data;
create table data.user_profile (
id int generated always as identity primary key,
username text,
value text
)
grant usage on schema data to api;
grant select on data.user_profile to api;
insert into data.user_profile (username, value) values
('bob', 'Bob''s First Value'),
('bob', 'Bob''s Second Value'),
('alice', 'Alice''s First Value');
create policy "Users can only see their own data"
on data.user_profile
for select using (current_user = username);
alter table data.user_profile enable row level security;
select * from data.user_profile; -- shows 3 record, both bob and alice's
set role api;
create view api_v1.user_profile as
select * from data.user_profile;
grant usage on schema api_v1 to bob;
grant usage on schema api_v1 to alice;
grant select on api_v1.user_profile to bob;
grant select on api_v1.user_profile to alice;
select current_user; -- currently api
select * from api_v1.user_profile; -- shows 0 records
set role bob;
select * from api_v1.user_profile; -- shows 2 records, both bob's
set role alice;
select * from api_v1.user_profile; -- shows 1 record, alice's.
-- both alice and bob cannot access the data schema or it's contents. RLS is respected for the api_v1 schema.
```
Does that make sense, or did I misunderstand your meaning?Creating a separate "data owner" and "api owner" to own the api and data schema+tables/views respectively alleviates this problem. Your API schema owner != your table owner unless you `ALTER TABLE FORCE ROW LEVEL SECURITY` in addition to just enabling it.
What issues are you running into with RLS?
I love working with PostGREST and have used it quite often for quick services (e.g. a vote button on a static site), internal tools (recently a covid checkin-screener), and for Proof of Concepts (postgres+postgis-powered full text search for address lookups in a webmap without using an external geocoder).
I personally have yet to use it for something with more than 200 users, but it sounds like others certainly have successfully. Supabase (https://supabase.io/) uses this for parts of their backend.
Again, maybe I haven’t thought about this enough yet.
What I like:
* Already supports the tooling I enjoy → SCSS out of the box, django/jade-like template engine (Terra, its sister project), markdown w/ TOML frontmatter
* Fast → build times are almost instant, dev server builds to memory and does live-reload
* Gets out of your way → it doesn't do more than it can, yet provides enough to work
* Builds a search index for client-side searching if needed
* Single Binary → I can pass the executable around with the repo and installation and environments are not an issue (ruby and python are painful for part-time developers it seems, at least with my non-developer academic peers).
I like that it provides a simple base to build on. I have one site that uses webpack to generate bundles for a couple JS files to allow for modern JS (babel) → all I have to use webpack for is JS, Zola handles the rest.I migrated our Django theme for our previous site in an afternoon. I've found that those I work with often don't really understand how formatting in a CMS will apply in the published result, and often have to go back in and edit their pages for conformance → If I have to touch it anyway, I'd rather do it in markdown myself, something I enjoy using.
I have students/interns who have picked up markdown faster than any other markup or CMS. I've tried mezzanine [^meh] and wagtail [^excellent, but heavy for our brochure-ware] in python, wordpress is a pain [^either too flexible, or not flexible enough, research interns don't easily see how complex theme interactions occur] and some others like cockpit [^neat but flexible to a fault, yet too rigid for how free-form folks want to interact with it]. Markdown is translatable, and usable in other tools: it's a great common denominator with a very low bar for entry. Students continue to use it after first interacting with it on these projects after they've left.
What I'm missing:
* a way to build from an API endpoint instead of markdown, i.e.: point to an endpoint to get the section list, build children as pages. Then I could use content from a postgrest instance, or build it from a list of remote markdown files... (no, I haven't really thought this through very well)
YMMV.Not to mention Facebook’s are even more difficult. Tangentially related, remember when you could use “View As” on your profile page to see what your profile looked like to others? It doesn’t work anymore, only works for Public and Yourself; you can no longer choose the person to view as.
It’d be great to test these algorithms. We can’t. They need to be designed and instrumented so this is possible.
Current statistics show that there's around 1'400 deaths of those under 50 with COVID-19 listed on their death registration, ( https://www.ons.gov.uk/peoplepopulationandcommunity/birthsde... ).
Where's your data from?
> Lockdown seems to drive deaths, at huge social and economic cost, rather than prevent them.
This could easily be a reversed causality, that deaths drive lockdowns... which, on the surface seems to make sense as high deaths seem to force politicians to lockdown (either for reality or perception).
AGOL (ArcGIS Online) is only providing the basemap and layer overlays (state boundaries etc), those probably come from Esri's "public" data portal and I doubt are part of the bandwidth issue.
There's some things that get close though, like Directus (directus.io). API-wise there's PostgREST ( http://postgrest.org/ ), PostGraphile ( https://www.graphile.org/postgraphile/ ) and Hasura ( https://hasura.io/ ). Commercially there's Supabase (https://supabase.io/) which is new and based on PostgREST and their own tooling, and SubZero ( https://subzero.cloud/ ) which is similar.
There are some non-ingestion (requires you to use the frontend) headless CMS options that may also fill this space ( https://headlesscms.org/ ) if you tilt your head and squint.
This space seems to be growing, primarily on the API side, I imagine the frontend side may be next.
Currently my favorite is PostgREST and custom VueJS forms (using Quasar for "rapid dev"), but requires lots of 'bring your own' work.