Cloudron Forum

@girish that's excellent approach, fully consistent with the trusted Cloudron environment, and thank you for the explanation. Now I understand much better. (sorry, I don't read the commercial pages any more, already bought in, didn't even know there was a Max Plan.)

Yes, I understand about the commercial pressures - everyone suffering and inescapable. So I support what can be done to make Cloudron successful, financially as well as technically, user adoption, market share etc.

So, @jdaviescoates, how is your post directed ?

• wrong Pro/Max split ?
• prompting ideas for Max ?

I'm almost there on intent, but not quite.
Sorry for being thick.

Interesting thoughts.
I'm a little unclear (just pay my sub annually, it's about the only bill which I am pleased to pay, and don't follow the plan details).
But is the Pro/Max split actually moving stuff out of Pro into Max ?

Please forgive me if I misunderstood - corrections gratefully received.
I'm deliberately surfacing it so proposal is not misunderstood by others.

But if it's true, I think it is a very bad and dangerous precedent commercially.
Great to create a Max plan, but not at expense of causing user base resentment they just lost something which had been included previously.

Max Plan should be adding stuff that doesn't exist already.
I will have to have a think about what could go in.

Surprised they don't just pull the source (archive the repo if cannot delete) and make it a commercial app.
Would save everyone a lot of time on positioning.
I hate all these faux-OSS (core open, anything useful paid).
I respect paid apps, use a lot, but they have to deliver and justify pricing.
OSS as "pre-market-building" should attract suitable amounts of venom from the community.

Aha !
Now I see.

I’m bit confused.
I thought ClouDNS is separate independent service. That’s how I use them anyway.
I’ve not come across “Netcup ClouDNS”.
Do they have a tie up ?

@girish yes, I do !
I know there are other good ones out there, but ClouDNS does me very nicely.
Mostly interact with it through my app, not so much in their Dashboard.

@LoudLemur no no no
Don’t try my version - is ALPHA PRROF OF CONCEPT.
Not for deployment just in case it helped another package.

@scooke you're welcome.
Hope you can make use of it.

Now added as Community App to ca.cloudron.io :
https://ca.cloudron.io/app/io.timconsidine.campfire

It's not a Discourse, or Stoat, or Haven.
But that's mostly the point : simple, no fluff.

What are you looking for?

That is a really great question @robi !
When I work it out ....
Seriously, list started as :

• something that worked
• something that is not WhatsApp
• something that is simple and intuitive for non-tech users

But thank you for the suggestions !
More research to be done.
Stoat was always interesting, time to take another look.

Thanks for the feedback @loudlemur

I took a quick look at packaging but Snikket is too much for my needs, so I parked it.
Looked at using your Prosody but it's also more than the simple chat I was looking for (packaged Campfire instead and will see how that goes).

Thanks to a nudge from @mononym

I have packaged Campfire : https://communityapps.appx.uk/cloudron-campfire/CloudronVersions.json

Testing it out, will then add to ca.cloudron.io

@mononym I do not recall seeing that so will take a look

@humpty initially registration was intended (just users not on cloudron instance)
But i guess instant use has some advantages for adoption.

It's not a defined use case.
Even maybe discourse could work - investigating.

@humpty awesome

completion of vat return is now under threat

@joseph thank you for clarification.

It's not meant to replace WhatsApp/Signal etc.

Good, not what I'm aiming at.

It's a mattermost replacement for an org.

Also good.
But cloudron users comes unstuck for this specific use-case.

I have no problem with Matrix/Mattermost.
But the user group in question would struggle with them.
And I'm not adding them to my Cloudron (could be thousands).

@loudlemur just interested :

• why Prosody not Snikket ?
• issues with Snikket ?
  Trying to decide a chat app for a new group.

Chat app is great, but I think I misunderstood positioning.
It's not a general chat app - channels and DMs require the other user to be have a Cloudron account ?

I have a new use case and thought this would be good to use, but it's restricted to users of my Cloudron instance - yes ?

Not an issue, I just misunderstood positioning.

Please don't.. (=

Ok !

I thought tags might help in the Postiz case : @brutalbirdie could just add a tag "unsupported".

I also thought about time-based-update status checks.
But if you take example of my Facilmap app, it's not been updated (except eMudhra in case) and doesn't change, no upstream releases and it's in daily use. A low-maintenance workhorse. I don't think marking it as stale would be fair or useful to any who do use it.
There will be many other similar cases. Maybe a packager's "touch update" could defeat the auto-stale, but it's more work just to side-step an event.

Abandoned apps : yes, a problem to think about.

Ooops, I am at risk of hijacking the topic. Will continue elsewhere if needed.

@BrutalBirdie well done and thank you.
I started using Postiz but ceased when there were issues (twitter limitation?) and removal from official App Store was mooted.

Your post raises one extra thought.
Forum posts age and get ignored.
I wonder if there is a case for tagging Community Apps as "maintained" (maybe leaving unmaintained as silent opposite).
But @james might have nightmares about the thought.
We probably want to avoid "badge soup" and extensions to CloudronVersions.json which muddy the water for devs.

Maybe simplest is app publishers use existing "tags" but as well as "app type" (productivity, AI, business, files, whatever), we also have "status type" tags like "maintained", "best efforts fixes only", "report an issue and I will fix it in 2 hours".
Yeah, well, maybe not the last one.

Ooh, another thought, can we put emoji or emoticon in a CloudronVersions file ? Must try it sometime.