🌿 About me:

Hi, my name is Urli Veyn, Urli, or just Urik.
I create simple, user-friendly products that make life easier, simpler, and safer for the average user. I am the founder of the Ayume company and services.

🦎 What I do:

Programming on Kotlin, Rust, Go, TypeScript & Tailwind CSS

🫀 My love:

@the_echo_info - my ray of sunshine in the dark of night.

💫 Social media:

✉️ @urliveyn
🤖 urliveyn
📹 urliveyn
🐣 urliveyn
🐱 urliveyn
📹 urliveyn
📹 urliveyn

🐾 Support:

SUPP - https://donatex.gg/donate/urliveyn

🦋 More:

😈 N/A
🤩 N/A

🦎 #Tags

#UrliVeyn #Veyn #Urliui #Urli #Urqiui #Ayume #media #youtube #urliui #urqiui #minecraft #vr #roblox #gamedev #development #13april #prime #stream #twitch #social #messanger #platform

All content on this channel is protected by the copyright of the "Ayume" organization; the current agreement can be viewed here: https://t.me/ayumerights.

🔝 Ayume Monthly Dev-Blog: What’s Changed in the Messenger This Month

‼️ A quick heads-up for newcomers:

Ayume is currently in active development. We haven’t reached Alpha, CBT, or other testing phases yet. Our primary focus right now is on system complexity, security, and the full functionality of the messenger's backend.

🔥 The Changes:

1. Redesigned Authorization (dev-v3): The authorization system has been completely overhauled. Ayume now relies entirely on sessions and your specific devices.
2. WebSocket Integration for Chats: All chat operations have been moved to a WebSocket connection. Messages will now travel through traffic as "empty junk," similar to how Telegram handles data.
3. API Access Security: Authorization and backend access have been fully reworked. All API routes are now blocked unless a valid JWT token is provided.
4. CI/CD Implementation: After a significant amount of effort, CI/CD has been configured in the backend repository. The repo now automatically checks the code for errors before deploying updates to the server.
5. Codebase Refactor: We’ve conducted a massive overhaul of the code, switching from Fiber to a different Go framework.
6. Backend Migration: The server-side has officially moved from Bun to Go. Bun will now only be used for the web version of the messenger.

🌿 Future Plans:

Ayume is being built with a "security-first" mindset, ensuring that the only thing between you and another user is the server - or potentially nothing at all. It will be difficult for ISPs or local traffic monitoring organizations to filter Ayume's traffic.
We are also focusing on server optimization by migrating all messaging to WebSockets while keeping other tasks on HTTP. Additionally, active development of a proprietary encryption and data transfer protocol is underway. Plans include launching our own GitLab instance to gain better control over the management of all runners and code servers.
There is a lot of work ahead, but with every step, we get closer to developing the first apps and reaching a full release!

👋 We look forward to your feedback, support, and help.
@urliveyn

🌟 Ways to contact me are temporarily unavailable due to global changes.

🦋 Most likely you have noticed that ayume.net disappeared somewhere and moved under the domain registrar Cloudflare (with its protection).

🌿 For now, I have nothing to say except that something is brewing. The next version of the site will already be functional.

https://x.com/urliui/status/2056232490935689268

My dear ❤️

Oh, ok 🧐

🌟 Again, I will say that there is a lot of work behind the scenes that I don’t want to talk about yet.

🧐 I have given much thought to the technology stack for the Ayume. I have decided that the entire backend (server-side and API) will be developed using Rust and Kotlin, with the bulk of the core development likely handled in Kotlin.

This is our preliminary plan, subject to further discussion and final approval by the team. We are committed to ensuring the security and isolation of our ecosystem.

You can also follow to our new GitHub organization 😙

https://github.com/ayumenet