patillacode

Hmmm, interesting, I will have a look, thanks!

There are two cases:

Self-hosted: your data lives entirely on your own machine/server and obviously I never see it. That's the primary privacy model the app is designed around.

piruet.app (my hosted instance): you're basically trusting me. (I know, trusting a random stranger on the internet... right?)

Other things I can tell you: Passwords are bcrypt-hashed and I can't recover them, but journal entries are stored in a SQLite database on the server. There's no at-rest encryption of content, so in principle the server's administrator could access the entries. I don't do it on principle and there's no infrastructure set up to do so, but I can't make a technical guarantee of that.

If you just don't trust the person hosting it, I'd honestly recommend self-hosting yourself.

At-rest encryption of entries is something I'd like to add, it's just not there yet. In the meantime, piruet.app is best treated as a demo/trial environment rather than a permanent home for sensitive writing.

If you have thoughts on how to approach encryption in a way that doesn't break usability (search, rich text, etc.) I'd genuinely love to hear them.

LOL

"one entry per day" takes on a whole different meaning that way.

Entries are stored in a SQLite database, and uploaded images sit on disk under the configured DATA_DIR. Both are in a single Docker volume.

Thanks for the feedback, I appreciate that you are looking out for me really.

My intention, the meaning of "forever free", is that I will provide the service for anyone and everyone that cannot self-host themselves, but of course, if I don't have money myself to rent a server, for example, and I have to shut the app down I would inform the people using it. This is more or less expected from a free app in my experience and there is a paragraph in the terms related to this, under "NO GUARANTEES"

What I want to say though is that I won't charge users for as long as the app lives, if the app dies for whatever reason I will try to inform users to export their data and find a better place I guess.

I use firefox and I have e2e tests that work in firefox, feel free to create an issue in the github repo explaining a bit what is not working for you

I don't, I just wanted to give back to the FOSS community.

If someone finds it useful and want to collaborate with the project they can tip me on ko-fi.

You can self host the app yourself or use the free hosted one I provide

Thanks for the feedback, I figured it out, I guess I forgot about the trolls...

Rolling out now...

I have tested many times, I have asked other people too... I cannot replicate what you are experiencing, sorry.

Thanks for the feedback! Appreciated!

----

I had some time to look into this, I think it is partially valid.

The pypi.org and pythonhosted.org calls happen only at docker build time when dependencies are installed, the running container makes no calls there.

The ko-fi badge image (storage.ko-fi.com) is a real runtime outbound request though, every page load fetches it from their CDN.

That's fair criticism and it has an easy fix which is to self-host the image, which I'll do like I do with the rest of things, like fonts.

Thanks again!

What about the classic heart-shaped bright red "piruleta" from the "fiesta" brand?

To be honest, my non-negotiable was that it needed to have some orange, but that doesn't work very good with a calm, minimalist app, so it remained as the accent color.

The rest wasn't my choice, we just did a few tests and my gf chose the palette you see today.

Having said that, you got a point and I didn't even realize it until you mentioned it.

The funny thing is that I am Spanish, and I tricked myself because we discussed between "piruletas" and "piruetas", and I had the message prepared before the name change, my bad.

I just tried it demo/piruetas and it works, can you double check?

The funny thing is that I am Spanish, and I tricked myself because we discussed between "piruletas" and "piruetas", and I had the message prepared before the name change, my bad.

I tend to always have a python project or two on the go, usually for my own benefit, little scripts to make my day to day easier/faster/automated or just learning new things or experimenting with ideas.

Because of that I found myself repeating the same steps over and over again when setting up new Python projects. Same song & dance.

I wanted a way to automate the setup for new projects, so I created ppieces.