Notes on Cloudron, crowdfunding app packaging

[bmann]

@girish a CDN can perform a number of different purposes.

Including if I’m hosting stuff behind a home connection that I’d like to stay up! Eg my home internet goes down, a CDN can keep serving up static content.

And: serves up cached content that never has to be fetched from my home connection.

And of course — ALL of this stuff is pretty far beyond basic home use. It’s great that Cloudron enables it at all.

[bmann]

@girish Tailscale is what many people use to access their home networks. It’s a private overlay network that makes it very easy to connect any devices as if they were on a private routable LAN.

Lots of run stuff at home geeks have it on their phone / laptop / home desktop as a way to access their devices from anywhere.

You can specify egress points. So, if you and a very small / cheap VPS / cloud something, you could use that to expose your home network without having to deal with what your router can do.

It’s built on the Wireguard protocol that is now in the Linux kernel.

There are of course tons of professional uses too, like making arbitrary private networks between any devices.

There’s an open source implementation called Headscale https://github.com/juanfont/headscale

[bmann]

@jdaviescoates said in Notes on Cloudron, crowdfunding app packaging:

Just to say, in many ways all apps that staff package, and all the apps in the app store which they maintain are already crowdfunded, in that they are funded by the crowd of customers who buy Cloudron licenses

No that’s the business of Cloudron: maintaining and supporting the core software, and deciding which apps to add and maintain or drop.

As I mentioned elsewhere, getting a strong signal from paying Cloudron customers could be helpful in understanding which apps to keep.

I get the analogy you’re trying to make, and I’d welcome a formal “fund this new app” run by Cloudron.

Luckily, the packaging format is all open, so we can also fund private / custom apps as we like. And the team can even choose to take over maintenance and offer it officially if they like!

[robi]

It may be important to modify the funding aspect in a way that clearly connects the maintenance of the app too.

[bmann]

@robi yep! The dual edge sword of "fund the feature" and "fund the long term maintenance" has always been a challenge in open source.

It might be interesting for active members here to make a stack ranked list of the apps they run a lot / would "vote for".

[robi]

@bmann we have it already in a few ways, via the forum app request votes, via the app store installs (but the demo server churns far too much for good data).

It needs more active management, which the core team isn't geared for.

[LoudLemur]

@bmann Thanks. Did you make your blog available via IPFS too? Cool!

Please mention on your page why more than one domain name would be useful.

[jdaviescoates]

@bmann the App Wishlist category can already be ordered by upvotes which gives as a pretty good idea of relative interest of each app

[bmann]

@jdaviescoates not by paying licenses, which is what most aligns with Cloudron’s business model and effort required.

Also, people don’t change their votes. There’s a “decay function”. Maybe I loved AppX when it came out, but want AppY now.

Anyway, this is most interesting to look at over an arc of years, and hopefully Cloudron can continue to be sustainable.

[bmann]

@LoudLemur _DNSLink is a feature of the IPFS protocol that you map a TXT record of the hash of the root of your published website or app and then CNAME at a single IPFS gateway. This means you don’t need to run a gateway for each domain.