fdroidserver VS Sandstorm

According to the latest comment on this F-Droid bug report it looks like the problem should be finally fixed in the next F-Droid build server update.

Proprietary: - https://gitlab.com/fdroid/fdroiddata/-/merge_requests/11359 - https://gitlab.com/fdroid/fdroiddata/-/merge_requests/11361 - https://gitlab.com/fdroid/fdroiddata/-/commit/37e72d45f841b72b334f23f3e15a2e31fa8c4d56 - https://gitlab.com/fdroid/fdroidserver/-/issues/1004

Different solutions may be better for the different file types than a single download centre for everything. For example, for APKs, there's f-droid. You could selfhost fdroidserver and add your own repo to the f-droid client. This way, the APKs are distributed via an app store that's searchable and can be configured to auto update.

They were all on different days. I do test the app on my phone before releasing, and usually only release after not noticing anything for a few days of using the dev version. The reason for the time is a bug in the F-Droid server software that is used to generate the repo. The releases of GitHub have the correct date.

Note that F-Droid uses algorithm at https://gitlab.com/fdroid/fdroidserver/-/blob/2.1a0/fdroidserver/build.py#L746 to automatically detect built APKs, so ensure any modifications to location or file name are compliant. Auto updates are detected by checkupdates bot at https://gitlab.com/fdroid/fdroidserver/-/blob/master/fdroidserver/checkupdates.py

For the source of fdroidserver which creates the F-Droid repository in the end see here: https://gitlab.com/fdroid/fdroidserver

Clone the fork onto your local machine. You'd need to use linux or mac (windows doesn't work). Install https://gitlab.com/fdroid/fdroidserver.

yep, sadly F-droid doesn't have enough people working on it to keep on top of google's "new" app signatures yet. There was some progress, but then I gave up waiting and added their own repo until it's fixed.

Sandstorm really had this kind of feeling. Not that it presented as a desktop environment visually - but it offered a much more integrated “computer” of documents versus silod web site apps where you need to open each site to see the files in the app. https://sandstorm.io/

RemoteStorage https://remotestorage.io/ seems to be trying to do this too

I also really like the https://sandstorm.io approach which goes a little farther beyond

They tried, it was called sandstorm https://sandstorm.io/

I did read from somewhere, that with Wordpress SEO plugins etc some website got to top of search results.

Those that did website with other tech did not get same results, and thinked how to compete or survive.

For security, I use Sandstorm https://sandstorm.io fork of WordPress that generates static websites. But that does not work with some interactive plugins.

Urbit made the choice to use a bunch of silly new words for familiar concepts, not because they were inventing something so new that there were no words to describe it, but because they wanted to fool people into thinking that's what they were doing. Actually they just spent 10 years trying to do https://sandstorm.io/, but made it 10 times harder than it needed to be by coming up with a wacky new set of programming languages with silly names for everything.

That's funny, and it is OK to make fun of it.

I don't work at Cloudflare but follow their work and occasionally work on performance sensitive projects.

If I had to guess, they looked at the landscape a bit like I do and regarded Cap'n Proto, flatbuffers, SBE, etc. as being in one category apart from other data formats like Avro, protobuf, and the like.

So once you're committed to record'ish shaped (rather than columnar like Parquet) data that has an upfront parse time of zero (nominally, there could be marshalling if you transmogrify the field values on read), the list gets pretty short.

https://capnproto.org/news/2014-06-17-capnproto-flatbuffers-... goes into some of the trade-offs here.

Cap'n Proto was originally made for https://sandstorm.io/. That work (which Kenton has presumably done at Cloudflare since he's been employed there) eventually turned into Cloudflare workers.

Another consideration: https://github.com/google/flatbuffers/issues/2#issuecomment-...