Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Reaching $10k monthly revenue with WakaTime, my SaaS side project

indiehackers.com

Post reply on HN
Print view View original

101–110 of 174 posts

Re: Reaching $10k monthly revenue with WakaTime, my SaaS side project

#101

Post by mivanchev »

cabaalis wrote: post #99
mivanchev wrote: post #66

I must voice concerns regarding this product. Just took a look at the Notepad++ plugin ( https://github.com/wakatime/notepadpp-wakatime ), because this is something I know a lot about. To begin with, it sends filenames to the mother ship instead of just the programming language. I would consider filenames to be sensitive information giving a very good idea of the project you are working on... Also problematic is the…

Perhaps you could encrypt the filenames with a user-supplied password hash. Upload and store just the encrypted filenames, and when the user is viewing the data on the web can decrypt the filenames by asking them for the filename password. You could run analytics on the encrypted data still, and not expose filenames to even wakatime.

Or you could divide the files in classes like that

-> "backend code"

-> "frontend code"

and upload only the class a file belongs to.

Re: Reaching $10k monthly revenue with WakaTime, my SaaS side project

#102

Post by [deleted] »

graphememes wrote: post #96
rpedela wrote: post #89

Earlier quoted context omitted.

Can't speak for xstartup, but if the dataset is 100+ GB then EBS, S3, etc start to cost real money. I host an application on AWS for a single customer with 10 active users which costs about $1500/month because there are several TBs of data and the nature of the application needs a lot of CPU and RAM. In other words, it depends on the use case and data size.

What? I have a 16TB raid that only costs 800$ a month. You should look into how you store that information.

[deleted]

Re: Reaching $10k monthly revenue with WakaTime, my SaaS side project

#103

Post by rpedela »

graphememes wrote: post #96
rpedela wrote: post #89

Earlier quoted context omitted.

Can't speak for xstartup, but if the dataset is 100+ GB then EBS, S3, etc start to cost real money. I host an application on AWS for a single customer with 10 active users which costs about $1500/month because there are several TBs of data and the nature of the application needs a lot of CPU and RAM. In other words, it depends on the use case and data size.

What? I have a 16TB raid that only costs 800$ a month. You should look into how you store that information.

Or stop making assumptions with very little information. That is really my point, but I didn't think it needed to be said explicitly.

Re: Reaching $10k monthly revenue with WakaTime, my SaaS side project

#104

Post by SteveNuts »

mivanchev wrote: post #66

I must voice concerns regarding this product. Just took a look at the Notepad++ plugin ( https://github.com/wakatime/notepadpp-wakatime ), because this is something I know a lot about. To begin with, it sends filenames to the mother ship instead of just the programming language. I would consider filenames to be sensitive information giving a very good idea of the project you are working on... Also problematic is the…

What if you opened John_Doe_health_information.txt - would something like this be a HIPPA violation?

Re: Reaching $10k monthly revenue with WakaTime, my SaaS side project

#106

Post by brianwawok »

leesalminen wrote: post #93
brianwawok wrote: post #88

Earlier quoted context omitted.

So what is normal in the SaaS world? I am at 5% today, and I try but not focus on costs. Around 5% it seems hard to care TOO much...

We're at ~10% and are just starting to care. We're looking at some infrastructure changes to bring us closer to 4%.

Well it makes sense to care more as you grow for sure.

Shaving 6% off a 10k a month company is $600 which is nice but not a game changer. Shaving 6% off a $1 mil a month company is $60k a month, which is a nice bonus for someone...

Re: Reaching $10k monthly revenue with WakaTime, my SaaS side project

#107

Post by sli »

SteveNuts wrote: post #104
mivanchev wrote: post #66

I must voice concerns regarding this product. Just took a look at the Notepad++ plugin ( https://github.com/wakatime/notepadpp-wakatime ), because this is something I know a lot about. To begin with, it sends filenames to the mother ship instead of just the programming language. I would consider filenames to be sensitive information giving a very good idea of the project you are working on... Also problematic is the…

What if you opened John_Doe_health_information.txt - would something like this be a HIPPA violation?

Having somewhat recently started a job developing frontends in health informatics, I'm noticing that programmers need to consider HIPAA far more than I think many realize. Even when working outside the healthcare industry, as may be the case here.

Re: Reaching $10k monthly revenue with WakaTime, my SaaS side project

#108

Post by cabaalis »

SteveNuts wrote: post #104
mivanchev wrote: post #66

I must voice concerns regarding this product. Just took a look at the Notepad++ plugin ( https://github.com/wakatime/notepadpp-wakatime ), because this is something I know a lot about. To begin with, it sends filenames to the mother ship instead of just the programming language. I would consider filenames to be sensitive information giving a very good idea of the project you are working on... Also problematic is the…

What if you opened John_Doe_health_information.txt - would something like this be a HIPPA violation?

Healthcare startup here: Yes, because first/last name are PHI identifiers, and it's possible that even using the product itself could be considered a breach because you don't have control over the data. If the filenames some non-phi unique identifier, you're fine.

What's the difference between sending data within in a file, and having the file named something that is an important data point? None. So naming the file with a PHI field (even MRN!) is a bad idea to begin with.

A good answer would be to not let true patient data leave the hardened production server and be opened in any kind of development environment, ever.

Post reply on HN