78 karma · joined June 13, 2023
* Where do you buy a ≤20 euro bike?
* Most people on the street have bikes that look to be at least 200 euros new, from what I can tell.
* Maddy: https://github.com/foxcpp/maddy
* Mox: https://github.com/mjl-/mox
* and Stalwart
which all see to aim for more or less the same niche. I wonder if we'll see two of those merge eventually.
¹: https://download.fsfe.org/campaigns/pmpc/PMPC-Modernising-wi...
²: https://www.admin.ch/gov/fr/accueil/documentation/communique...
³: https://joinup.ec.europa.eu/sites/default/files/inline-files...
* Something like row-level access control, so that people can only access the data in tables that belong to them (say clients can only view their own purchases, and also not modify them after they checked them out).
* Integration with the rest of the world, e.g. sending email, acting on triggers, etc.
* Something like CSV export/import.
* Internationalization.
Would that all be possible? Straightforward? Do those all require extending (with go or js)?
Looks like a nice tool.
The only counter-argument I have is that if all the heating were done using ventilation, you might have to live in a very windy house, but I feel like entirely decoupling the two is not the best solution to that problem…
Isn't that the case?
It would be nice to have just the one or two options, with app store and some kind of official entities backing (say, states, or universities, or distros).
With tools like xournal++ or other things like document processors, you can usually define your own panels, reorganize them, move them around, add icons or separators, etc, and all of that in a drag&drop fashion, live from the program running.
I feel like having a (compile-time) declarative description of that wouldn't cut it, or be very abstract, with most of the logic outside of the declarative description. Another option might be something that's "runtime declarative", and drag&dropping icons and panels around just change the ui definition?
and ask your users to install those before being even able to use your app?
I haven't phrased my argument very neatly, but the point stands: anyone with an iphone/android/linux/… can easily use a web app, now, without any prerequisites. You don't have to bundle it or distribute it differently than with a webserver and it's a single codebase. That's not the case for any other tech that I'm aware, and it's a shame.
* usable on pretty much any platform
* easy to distribute/update
* easily trustworthy/jailed (no need to install something that might access your data)
It makes me sad, but as far as I can see, there is no serious alternative for universal+jailed apps.
What I'd like to see is something that can connect to a pg server (or sqlite, or mariadb, but I think settling on one is more feasible) and tries to surface as much as possible of the underlying data representation, and add features that are translatable to how pg works, instead of just using pg (and in grist's case, sqlite) as a dumb backend.
* it doesn't sync with anything but has its own data store, built around sqlite, and you can indeed download "documents", which are just sqlite files. (I looked at how they encode summary tables, and it's not as views, so the grist<->sqlite translation is not as shallow/isomorphic as one might hope)
* authentication is not taken care of by grist-core itself, but they provide different integration methods (saml, forwarded headers, … ?)
* Are you self-hosting?
* What auth method are you using?
* How is the linking done? I presume API (or are you just using widgets?), but that means you need users to copy/paste their API key by hand?
Thanks!
And compared to the alternatives (nocodb, mathesar, baserow) they seem to provide the best self-hosted/open source solution in terms of polish and features.
*Edit* I've been looking for a while for a similar software stack for the organisation of a coop I'm a member of, and have not found anything better as of now, though open to alternatives!