Yo, 0.3.3 is out.

You can now add elements on tablet by long-pressing on an empty space, it opens the context menu. Demo’s already updated if you want to test it there.

Public shareable links function as interactive read-only snapshots.

When a link is generated, a unique cryptographic token is mapped to the project’s current state in the database. The route serves this data to a canvas where all mutation logic and API write-access are disabled.

Key facts:

• Read-Only: Access is strictly limited to viewing and navigation. No data can be modified.
• Static State: It is not a real-time sync. The link reflects the project at the time of generation.
• Revocable: You can disable the link or regenerate the token at any time to kill previous access.

This is similar to how tools like Lufi or PrivateBin handle public access to specific resources without requiring authentication. And NoSQL/centralized backdoors 😅

Yeah, that shouldn’t be hard to add.

If you don’t mind, open an issue just so I can track it properly. I’m already working on touch support anyway.

The plan is basically a long press on the background to open the menu and create blocks. That should feel natural on tablet without adding extra buttons everywhere.

You’re not missing anything 🙂

Ideon isn’t fully tablet-compatible yet, and mobile portrait is even more limited at the moment.

Touch support is something I’ve been actively working on for a while. Some interactions, like right-click equivalents, need proper tactile handling, and that requires rethinking parts of the UX rather than just patching it.

A dedicated mobile mode for smaller screens is also planned. The challenge is making keyboard/mouse and touch experiences coexist cleanly without breaking workflows on either side, so it’s taking time to do it properly.

Sorry for the frustration on your side. I completely understand it. It’s definitely on my roadmap, even if it will require a bit more work before it feels right…

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 :))

Here’s a simple way to look at it: it’s all about persistence. If someone sneaks a backdoor onto a server or inside a container, that backdoor usually needs the environment to stay put.

But with containers that are always changing, that persistence gets cut off. We log the bad stuff, the old container gets shut down, and a brand new one pops up. Your service keeps running smoothly for folks, but whatever the attacker put there vanishes with the old container.

It’s not about saying hacks won’t ever happen but making it way tougher for those hacks to stick around for long :)

Nah, not really. I mostly use AI for the annoying stuff like GitHub workflows, install scripts, and boilerplate code, not the actual backend or frontend code.

Oh, and since I’m French, I also use it to clean up my notes into good English for the README (in response to Jokulhlaups). It’s just a handy tool to speed things up, not some magic button that builds everything with one command. If you look at the commit history, you can see the project grew over time. Definitely didn’t just pop out of a single prompt, haha.