(FullStory records what you do in your browser. It records all DOM elements, so all your data is being recorded and sent to a 3rd party.)
Source: am European
{ "Domain": ".fullstory.com", "Name": "fs_optout", "Value": 1, "Path": "/", "Expires": null, "Store ID": "firefox-default", "First Party Domain": null, "Secure": false, "Session": true, "Http Only": false, "Host Only": false }
As in: this cookie will stick around as long as your browser is running, but when you close it and start it up again it will be gone?
When you opt-out of Matomo, the message warns that “if you clear your cookies, delete the opt-out cookie, or if you change computers or Web browsers, you will need to perform the opt-out procedure again”.
Matomo also honours the browser’s DNT setting, which is a) nice and b) rare.
https://matomo.org/docs/privacy/#step-4-respect-donottrack-p...
And notion doesn't need to see their users data to charge money for a service. They could engineer it to be E2E encrypted for the group and not have the ability to see their customers data even with a subpoena.
1) sell me apps (desktop, mobile),
2) let me sync the content via my choice of providers (dropbox, iCloud, google drive, my own WebDAV server, etc)
3) Let me manually enter a strong password/key in all of my clients to E2E the data, so I don't really need to trust that sync provider.
Suppose your company handles a fair bit of confidential information, and some of that information ends up in Notion as part of your general project management workflow. Now you've got to worry about Notion experiencing a data breach, and whether or not that breach could get you in hot water with your clients, or even into legal trouble.
With on-prem options, you can gain a little extra confidence, because it can all live behind a firewall instead of being directly exposed to the Internet at large.
This started with the idea of a personal on-prem solution, which is probably not worth the cost to maintain for the company. I mean, how much is it worth to you to have an on-prem personal solution for a diary? Because that's the worry... people are afraid that their household budget or their database that tracks the content of various adult films or whatever is going to get exposed. That's mostly about embarrassment, not actual harm. That's not something worth hundreds of dollars a month to most people.
And really, if I want to write down my deep dark thoughts where no one will read them, I'll use paper.
Why can't it be as simple as containerizing it and presenting it exactly like your would install an app on your phone, with the same possibility to grant permissions? App store provides automatic OTA updates so you don't have to bother about security. And the app itself should not have internet connectivity, connectivity is provided through authenticated tunnel into the container so the app cannot phone home in the background, you can only connect into it using the tunnel with your own password.
(Full disclosure: I'm a total bullet journaling convert. Given a choice between giving up my bullet journal and giving up Google Calendar/Docs and Trello, I'd give up the online stuff in a heartbeat.)
Definitely, but I'd argue that even with containers etc., we don't yet have the capabilities to make what we know is right, as easy to operate as SaaS.
> Suppose your company handles a fair bit of confidential information, and some of that information ends up in Notion as part of your general project management workflow.
Many folks that post to HN seem to miss this even though they are probably very technically capable. Many IT people in small/medium organizations don't have the time to consider this. Sometimes relationships with big organizations force this reality and threats get addressed, but it's not the norm. Most IT managers are under pressure to cut costs, reduce staff, modify accounting (review vs capital budgets), coexist with shadow IT, etc. Cloud solutions seem fantastic to them, and they don't have the energy to fight with someone in marketing who introduces a rogue solution because they don't understand how the current Wiki works.
That's usually a sign of an IT department not listening to the needs of their end users.
This can result in the team being left holding the baby when certain individuals leave, data loss, security issues etc. In 15+ years of enterprise probably two-thirds of the time I've seen this issues and it has been predictable that it would work out this way, but IT didn't help themselves by pretending their solution was better. When IT tries to learn and adopts the tool, or incorporates the needs then things work out better. But, that's only a third of the time.
stackedit.io has been the closest that I could find.
https://news.ycombinator.com/item?id=18906118
Haven't tried it out personally (only support signing in from Slack/Google), but it might be your kind of thing. :)
When it comes to business and productivity applications the situation is very different. Many IT admins are tasked with moving to cloud (or other outsourced) solutions. When you see posts you have to realize you, or I, who value autonomy and control may not be the expected customer of these solutions.
To reduce the economics further:
* Startups like this have a product which may not have a complete market fit or reknown. They can't build something that's most likely to stick e.g. a required mail system because a couple of cloud products own the market. Therefore, they move up the productivity stack to team and document collaboration.
* Since they aren't a mature product and will likely change it considerably in the short-term, possibly "firing" customers as they search for a bigger market, they'll need their product to keep up. If they host it, then they can change it end-to-end.
* Any time you release a product that gets deployed on-prem it's virtually impossible to get people to update in a timely manner. Even if you decide to provide an on-prem version to a potentially huge customer, the enterprise sales cycle means that there is a risk your product will have changed before it gets deployed, but some person/process will prevent you get updated to the latest version as they advocate for a competitor.
* Worse, they like the old version and want to stay on it. How do you support these on-prem customers? They liked the value at your cloud pricing, but the cost to support on-prem customers can be much larger.
https://mobile.twitter.com/notionhq/status/99643620080931635...
Just shipped: export your entire workspace with one-click.
Examples: - Adobe (PS, ID, AI,...) all cloud + subscription model since CS6 is gone - Music (Spotify & Co) - Movies/Series (Netflix, Amazon,...)
And there is many more not only focused on software products. That is why I pirate stuff first and then try to buy something that offers value to me (like vinyl from bands I like to hear) while supporting the real minds behind the work (I don't like companies just (ab)using their power for profit like amzn without delivering real value themselves).
> For a Linux user, you can already build such a system yourself quite trivially by getting an FTP account, mounting it locally with curlftpfs, and then using SVN or CVS on the mounted filesystem. From Windows or Mac, this FTP account could be accessed through built-in software.
One of the best things about Dropbox as an early adopter was knowning that if they died or got acquihired, you still had one or more local copies of everything you'd ever uploaded to them.
Is it going to be open source?
Unfortunately, I'm not in a position to maintain the project if it doesn't bring in revenue.
I very much want to talk about it, but it feels a little meaningless to do so until I've shipped it :)
https://pureformstudio.com/diarly
Think the reason for non-self-hosting is price really. One time purchase is.. well it's one time.
The same is true for all other Atlassian products.
https://www.atlassian.com/software/jira/pricing?tab=self-man...
The next tier is 25 users for $2500. So it went from $1 per user to $100 per user.
JIRA is, by its nature, a multi-user software. The $10 for 10 users is clearly engineered to get small teams to commit to using it and then squeeze them when they grow.
That is a reasonable strategy for what is a product for companies i.e. enterprise software.
It wouldn't work for a product that is primarily for people who are paying from their own pocket, like, I assume, everyone here that expressed the want for a self-hosted version.
Notion is a hierarchical note-taker/wiki with some additional features like simple databases, task lists etc.
They are not the same kind of software.
Also, you can link notion pages. They have a block element that is a link to another page and for inline links you can use the regular link (each notion page has its unique, stable url).
Can they dockerize this and sell that so I can self-host the docker image instead?
for people that is not tech-savvy, what about they buy a docker-container-hosted-by-the-vendor-company but can encrypt the contents in a way that nobody else can peek into the content ever?