U-Net's inception

Who am I and what is Egress

Hello fellow developers and web trotters, My name is Tim Rietdijk and online I usually hold the username "Xevorius". I've been a Backend developer for over 8 years now. In that time I have gone from project to project all over the world. I have never really stuck to one niche and kinda just followed my interests and endeavors the companies I worked for. However, four years ago I started something myself. I called it Egress. Egress was a way to kinda legitimize all my personal projects. One of those projects, Egress Portal, became something bigger and a Company spwned from it. And Although I'm no longer working on Portal, Egress (both as a personal portfolio and corporate entity) continued.

What is U-Net

My current job was perfect for the slow down my life experienced this last year but I wouldn't say it's challenging me. So, over this last year, a new idea formed and this fire that dimmed a bit started to grow again. I've now been working on U-net, the next big Egress Project, for 8 months now. The idea went through a couple of revisions before I really locked in. And after some obssessing the platform is becoming something I'm proud of and want to share. I'm not really someone that shares a lot about myself or my projects but when a project reaches a certain point even I can't keep quiet.

Okay, but what is it?

U-Net is a privacy-preserving identity and communication platform. Now that might sound like a string of marketing words but this jumble of words does describe U-Net well. Every individual feature will have it's own blog post down the line. So, please read thise if they are up already and if you're interested in the more technical side of U-Net. But to kinda summarize it, U-net lets people sign in to online services, prove things about themselves, and communicate with those services without having to hand over unnecessary personal information. The project is more than just an online identity wallet or authenticator app. It's a full platform for users wanting to keep their data private and companies wanting to solve their outdated auth solution. But I'll keep my explaination at this for my first post. I'm sure you have a lot of question on how this works and what problems it solves but I don't want to blow my load too early... Like I said, sharing stuff about my project doesn't come that natural to me. So, by splitting up everything I want to say about it and sticking to taht plan, I make sure I don't run out or quit the blog.

Over the coming weeks I'll be writing about the ideas behind U-net. I'll also speak my mind a bit about why I think the web needs a different approach to identity, communication, and trust online. And for my fellow developers I'll also go over the technical decisions that shaped the platform. Whether you're a developer, founder, or simply curious, I hope you'll enjoy following along. Thanks for reading!