expyth0n

Thanks so much! Really happy to hear that, it means a lot ❤️. I’m obviously looking forward to adding more block types and integrations, and ideas like Nextcloud or custom blocks are definitely on the roadmap.

Thanks for the detailed feedback! I see what you mean, once people start dumping a lot of content, managing everything can get tricky. I actually use Ideon myself to develop the app and track progress, and honestly I’m not quite at that “large-scale brain dump” stage yet 😅. Nvm this is just the beginning, and I’m continuously improving the organization features !

Awesome! Enjoy testing it out :D

And really cool suggestion :D I’ll look into how to integrate that in a simple/practical way. Thanks for taking the time to comment !

Thanks! I hope it ends up being really useful for organizing your ideas and projects :D

Thank you so much! that really means a lot :))

Thanks a lot. Yes, it’s not the most adequate solution yet, that’s exactly why I’m reaching out to communities and forums, to get feedback and improve it every day so it can eventually be useful to more people.

I understand perfectly, thanks for the feedback, in fact it may seem counterproductive, I wanted to release too many features and merge everything to say that it is ultra secure, so I absolutely understand all the comments, I will make sure to improve all of that.

Also, now that I’ve re-read this (I didnt understand what downvotes mean at first): why does a new project that doesn’t compete with big companies deserve downvotes? I’m just trying to meet tech people and talk about it, that’s all. It doesn’t need money, it doesn’t hurt anyone, and I’m not posting bullshit.

If it doesn’t solve a problem for you yet, that’s fine, it will get better over time. I genuinely want to understand what made you comment like this. And since you’re a moderator, respect btw, but why push people toward hating on it? What’s the goal here, should I delete the repo?

nobody here asked for technical details, so I didn’t respond with technical stuff. but now that you ask, I can respond:

1. the rebuild occurs periodically. you set the period (in seconds) in the .env. a container named orchestrator stops and rebuilds vault containers by deleting every file that is not in the database and therefore not encrypted (like payloads). for event-based triggers, I haven’t implemented specific ones yet, but I plan to.

2. session tokens are stored encrypted in the database, so when a vault container is rebuilt, sessions remain intact thanks to postgres.

3. same as 2: auth tokens are stored in the database and are never lost, even when the whole stack is rebuilt.

4. yes, but not everything. since one container (the orchestrator) needs access to the host’s docker socket, I don’t mount the socket directly. instead, I use a separate container with an allowlist to prevent the orchestrator from shutting down services like postgres. this container is authenticated with a token. I do rotate this token, and it is derived from a secret_key stored in the .env, regenerated each time using argon2id with random parameters. and i also use docker network to isolate containers that doesn't need to communicate between each other, like vault containers and the "docker socket guardian" container.

5. every item has its own blob: one blob per file. for folders, I use a hierarchical tree in the database. each file has a parent id pointing to its folder, and files at the root have no parent id.

6. can the app tune storage requirements depending on S3 configuration? not yet, S3 integration is a new feature, but I’ve added your idea to my personal roadmap. thanks.

and I understand perfectly why you’re asking this. No hate at all, I like feedback like this because it helps me improve.

Hey, thanks for the honest feedback, I really appreciate you taking the time to share your thoughts.

Yeah, v1 was pretty rough, I won't lie. It not even worked on a clean install. I was just starting to mess with GitHub back then, so my early work lacked proper tests, workflows, and a good release plan. That's totally on me.

I rushed v2 out because I didn't want to keep building on shaky ground. Since then, I've really focused on making things stable: adding pre-commit checks, setting up CI workflows, and testing installs on fresh VMs so i know it actually works for other people, not just on my pc.

You're also right about the words I'm using. Zero trust fits way better than zero knowledge (I literally translated from french words 😅), and I need to be much clearer and more exact about that in the docs.

Regarding issues, I'm still hoping more people will check it out and give feedback. But honestly, I'm always happy to chat and answer questions when they come up, that's exactly what I'm hoping to get more of.