Take no offense, I'm not assuming anything lol just want to hear more about your own experience. Thanks.
It works for me. Their support a couple of years ago wasn't as good, but has improved a bunch since then.
Hey thanks for the review folk 🙂
That's what I thought, since the complaints I'd found were relatively old, and I also thought a folk in the Cloudron community wouldn't mislead us, wouldn't it?
Truly, prices are hard to beat.
customer signs up for an account (on Nextcloud) to collect a free product.
to buy more, customer is asked to log into their account, but that page is actually a Wordpress registration form looking like a log in form. Customer enters the same credentials, so both accounts will correspond (and both sites are under one brand/visual identity).
when coming back to their account page (on Wordpress) for future purchases and such, customer will use a similar looking log in form, that is actually a log in form.
the camouflaged registration form needs to be used only the first time. I can arrange that through the onboarding flow.
I still need purchases on Wordpress to be reflected for the corresponding user on Nextcloud. I'll start manually (again, tiny operation), then I think I can automate that through the APIs on n8n, like Stripe to Nextcloud. Just need to learn more about how that works...
@LoudLemur Understand the motivation and also the usefulness in certain use cases.
But (repeating another comment elsewhere) I like that Cubby is separate and reduces/eliminates any risk of "link bleeding" or hijacking of links.
I guess that if integration is implemented, it could just be disabled.
At least that is what I would request.
In that way its standalone / segregated implementation can be retained.
However, the point of Free Software is not only about how things are now but also about future proofing. Things might change in the devs' lives, they might need to move on, they might need a lump of cash cause something terrible happen and sell the company, or whatever else. And if the new devs have a different ethics what do we do? Look for another software and all the time and energy spent on Cloudron is kinda wasted and then not as many people benefit from this amazing platform? And to be honest the current situation makes it hard to recommend it and promote in some context because not everyone is just interested in the best software or value for money but also care about software license but ethical and practical reasons.
I don't have a perfect solution as I understand and respect Girish and Nebulon's current position in that they don't want someone to just fork everything and release it for free.
Maybe something could be added in the license that says the code must be made publicly available, and that if the license changes to a more restrictive one (one that removes the public release of the code), then the current license reverts to a Free Software license e.g. AGLP 3.0 or its successor. This would basically guarantee Freedom 0 and 1 and would implement some kind of (twisted) copyleft. And that would be enough to make me happy 🙂
But I don't know if that is possible at all?? I'm a legal geek but not on software license...yet 😉 Anyone know?
I have a RS 4000, RS 1000 and a couple of small VPS at Netcup. For storage space I use Hetzner Storagebox since Netcup is way too expensive. On the other side, if you need faster storage and interconnectivity, you can order Cloud vLan at Netcup to build your own Network within their Datacenter.
@necrevistonnezr I avoid fussing about GDPR as I consider it a total mess but one important distinction to bear in mind is that while an IP address is indeed capable of indicating identity, the core issue is whether it is “PID” : personally identifiable data.
As I said, Identifiers can be problematic in combination. And please think of false positives, where totally legit IPs are combined with your server domain - think a private domain and an IP to abortion information, stuff like that. BTW companies are not protected, only persons.
And while GDPR is exhausting (mostly, if not really understood) and needs improvements, it has lead to many companies thinking privacy when developing a product, not just afterwards. Or how they need to secure private data with technical and organizational measures (Art 32 GDPR) - hardcoding passwords or keeping them unencrypted for example (think the current Twitter scandal) can lead to fines and liability. It’s a new mind set.