crodjer

In my defense, I didn't know about Facebook's watchman then (did it even exist?). `watchman` sounded like an appropriate name to me for the task this script was for.

I had not intention about gaining from folks accidentally landing on my project. Apologies if people felt mislead. I have no idea why this was suddenly posted on Hacker News yesterday.

This looks great! I'll also check this out as someone who pivoted to rust tooling in the recent years.

Hello everyone, I am the author of this project. Not sure what generated interest in this.

This was a project I did for my personal use case. But I haven't been using it since years. I'd recommend [entr](https://github.com/clibs/entr) for the use case watchman was to serve.

I was analyzing the network traffic for the app (as i use a self hosted AdGuard Home), but couldn't find which domain it wants. I figured blocking all internet should be fine as Audacity works perfectly fine offline.

Is disabling the internet access to the application not a viable short term solution? We can't remove it yet as it is required in an ongoing project.

I am currently denying access to the application via:

flatpak override --unshare=network org.audacityteam.Audacity

In practice, I haven't see that happening much. If spammers were smart enough, they would actually do something useful.

If a service you subscribe does this, it is a good clue for you to mark them as spam and delete account after setting garbage values.

Turned the service off for now. Will be working on the issues raised at various forums: https://github.com/crodjer/qotr/

Updated this as a notice on the project README.

I understand the name is confusing. I was a long way into naming everything about the project QOTR before I realised that OTR is best used if the protocol is implemented, instead of taking it as general concept.

I plan to re-write the application (at least the front-end, which does all the encryption stuff) based on the reviews and if people think that it is actually an idea worth pursuing. May change the name as well.

Thanks for pointing that out. Updated the document.

No, it doesn't actually use the OTR protocol. The application actually follows this flow: https://github.com/crodjer/qotr/blob/master/FLOW.rst#how-qot...

I understand the name is confusing. I was a long way into naming everything about the project QOTR before I realised that OTR is best used if the protocol is implemented, instead of taking it as general concept.

I plan to re-write the application (at least the front-end, which does all the encryption stuff) based on the reviews and if people think that it is actually an idea worth pursuing.

True. Given the business Heroku is in, they should have redundancies in multiple regions if not multiple service providers.

Heroku build logs spitted this out:

    Unable to fetch source from: https://s3-external-1.amazonaws.com/heroku-sources-production/heroku.com/<some-uuid>?AWSAccessKeyId=<some-access-key>&Signature=<some-signature>&Expires=1439198046

Could this be a reason why Heroku is misbehaving? https://status.heroku.com/incidents/792K

Redirects issue fixed. Can you try it now?

Fixed. Can you try it now?