51–60 of 73 posts
Since that's been happening a lot in this thread, the easiest thing is to take the term out of the title, and thus (hopefully) the issue off the table. Let's stick to discussing the project now!
Deta Space appears to be very lacking in the product details department. I see a comment saying you can't self-host it, so it has to be on Deta's cloud, or can you even bring your own cloud provider? Is there any technical/security guarantee's to Deta's privacy claims? For one, a casual reading of their privacy page suggests they integrate a half dozen analytics (aka monitoring) tools including Google Analytics.
Hi, CEO of Deta here. On Deta Space, self-hosting means that once the app is installed in your own personal cloud, you have full ownership of the instance and it's data. Not the developer. We use GA in our dashboard but the apps themselves do not contain tracking. We aim to remove all tracking in the future. GA only collects web pages visits (anonymously).
I can't see how I could have full ownership of it since I didn't set it up and have no idea how it works. It comes across as very 'black box' and hidden behind the scenes.
Either way it's not self-hosted unless I'm the one doing the full setup from the start.
Earlier quoted context omitted.
See, I wouldn’t call it self-hosted if you can’t actually… self-host it. Someone else’s server isn’t mine.
come on, let's be a bit more inclusive about the term "self-hosting". For instance, I run a few apps in Linode. I manage the virtual servers, and consider myself to be a self-hoster of these webapps (Nextcloud, Drupal, PixelFed, et cetera) These aren't necessarily my servers but at some level, they are.
This detaspace thing is like saying that Amazon S3 is self hosted because you can upload your own files to it.
The word 'self-hosted' is like 'open source' in that it leads to tons of distracting objections when people disagree about what it ought to mean. Since that's been happening a lot in this thread, the easiest thing is to take the term out of the title, and thus (hopefully) the issue off the table. Let's stick to discussing the project now!
Deta Space appears to be very lacking in the product details department. I see a comment saying you can't self-host it, so it has to be on Deta's cloud, or can you even bring your own cloud provider? Is there any technical/security guarantee's to Deta's privacy claims? For one, a casual reading of their privacy page suggests they integrate a half dozen analytics (aka monitoring) tools including Google Analytics.
Hi, CEO of Deta here. On Deta Space, self-hosting means that once the app is installed in your own personal cloud, you have full ownership of the instance and it's data. Not the developer. We use GA in our dashboard but the apps themselves do not contain tracking. We aim to remove all tracking in the future. GA only collects web pages visits (anonymously).
You're both trying to redefine what everyone understands as self-hosting, in some seemingly direct ways.
As someone with over 2000+ bookmarks organized under 30+ folders on Google bookmarks, I've been looking for a self-hosted bookmarking tool with a nice UI that can run on my home server and is easily available across all platforms and devices for a while. This looks like a great start but I wouldn't call it self-hosted though, I'm more than happy to pay a nominal one time fee for a docker deployable image version of t…
I am not planning on providing a version of WebCrate which can be run on any server any time soon. WebCrate uses services provided by Deta (like Deta Base for the database) internally and thus can't be moved to a docker image without a rewrite of the backend.
I hope you understand and may consider giving Deta Space/WebCrate a try in the future!
Earlier quoted context omitted.
Not out of the box no. You could fork and modify it, but that would take a lot of work. Can't recommend Deta Space enough though, it is kind of like self-hosting it without managing an actual server!
It's not at all like self hosting it, sounds like it's just running on some servers located somewhere, and is completely unknown to the user. I'm also surprised it's that difficult to convert to self hosting, it makes me think that detaspace has a very convoluted system for running things.
Those services made it possible for me to build WebCrate in a short time and took a lot of work off my shoulders.
The word 'self-hosted' is like 'open source' in that it leads to tons of distracting objections when people disagree about what it ought to mean. Since that's been happening a lot in this thread, the easiest thing is to take the term out of the title, and thus (hopefully) the issue off the table. Let's stick to discussing the project now!
Thanks, didn't expect so much backlash about the term!