Hello Community

Was I the only one who loved the Mega Man handheld game as a kid?

https://preview.redd.it/c6k1pd2i2u2h1.png?width=900&format=png&auto=webp&s=e75ce94fe79db9ec62bdb6dda0503bc352f5319e

My idea (I'm a full-time developer) is to build an app that does exactly that. It would include the local multiplayer aspect—collecting steps, fighting viruses, and possibly unlocking chips (abilities) online—while PvP and trading would only be possible locally via Bluetooth. Do you think that would be well-received?

Moin zusammen, denke der Titel sagt alles.

Auf welchem Server seid ihr und spielt ihr aktiv?

ch arbeite gerade an einem Desktop-Messenger-Projekt und wollte es hier aus technischer Sicht vorstellen. Die App basiert auf Electron als Desktop-Shell und React im Frontend. Die eigentliche Anbindung läuft über native Bridges im Main Process, damit WhatsApp und Telegram sauber getrennt und trotzdem in einer gemeinsamen Oberfläche nutzbar sind.

https://preview.redd.it/7ienam6hon1h1.jpg?width=720&format=pjpg&auto=webp&s=a1e8399b408180520dbce4ad064fc9c2da675c97

https://preview.redd.it/8a19hl6hon1h1.jpg?width=848&format=pjpg&auto=webp&s=240c34a11eff7b2d894c8abb75d1e639d873a3bf

Technisch spannend fand ich vor allem diese Punkte:

• getrennte Integrationspfade für WhatsApp und Telegram
• IPC zwischen Renderer und Main Process
• lokales Caching für Chats und Avatare
• ein Theme-/Skin-System über CSS-Variablen
• Packaging für Windows, macOS und Linux
• saubere Trennung zwischen UI, Messaging-Logik und Plattformcode

Optisch orientiert sich das Ganze bewusst an einem alten ICQ-5-Stil, aber der eigentliche Fokus liegt auf der Architektur: ein moderner, lokaler Desktop-Client mit mehreren Messengern, ohne Web-App-Gefühl.

Mich würde interessieren, wie ihr so ein Setup aus Architektursicht bewertet.
Würdet ihr für so ein Projekt eher auf eine gemeinsame UI-Schicht mit klaren Service-Bridges setzen, oder die Messenger strikt als getrennte Module behandeln?

I’ve been working on a small desktop messenger project inspired by ICQ 5. The goal is not just to copy the old look, but to bring back the feel of early 2000s instant messaging: simple contact list, old-school layout, message sounds, and a UI that feels like a real desktop app instead of a web wrapper.

What makes it interesting is that it’s not just nostalgia for nostalgia’s sake. I’m combining that classic ICQ-style presentation with modern services like WhatsApp and Telegram in one app. So the idea is: retro personality, but still useful today.

Contactlist

I’m curious how people here feel about this kind of project.

Would a genuinely well-made retro messenger UI be interesting to you, or is that mostly only appealing to people who already have strong nostalgia for ICQ / MSN / early desktop chat clients?

I’d especially like feedback on:

• whether the retro look actually adds value
• what makes an app feel “authentic” rather than just themed
• which old messenger design elements people still miss today

If there’s interest, I can share screenshots or a short build video.

I'm open for feedback.

Code is completly opensource if you are scared that I want to grab some personal infos or something like that.

Chatwindow

Ich habe meine Steam-Bibliothek analysiert und herausgefunden, wie viele Spiele ich noch nie gestartet habe

Hallo zusammen,

ich habe einige Statistiken aus meiner Steam-Bibliothek exportiert und war von meinen eigenen Zahlen ein wenig beschämt.

Meine Ergebnisse:

Steam-Realitätscheck:

- Spiele insgesamt: 341

- Noch nie gespielt: 96

- Abschlussquote: 72 %

- Gesamtstunden: 4726

- Durchschnittliche Stunden pro Spiel: 13,9

- Geschätzte Gesamtkosten: 6820 €

- Versunkene Kosten (Spiele mit 0 Stunden): 1920 €

- Zeitäquivalent: 2,27 Vollzeit-Arbeitsjahre

- Verbrachte Lebenszeit bei 8 Stunden pro Tag: 1,62 Jahre

- Verbrachte Wochenendtage: 197

- Anteil der Spiele mit Hauptcharakter: 14 %

- Top-Spiele: Elite Dangerous, THRONE AND LIBERTY, PUBG: BATTLEGROUNDS, Counter-Strike 2, ELDEN RING

Scham-Score: 100/100

Die größte Überraschung war, wie viel „mein zukünftiges Ich“ für „irgendwann einmal“ gekauft hat.

Aus Neugier:

Wie hoch ist deine Zahl an ungespielten Spielen?

Welches Spiel macht den größten Teil deiner gesamten Spielzeit aus?

Glaubst du, dass das schlechte Gewissen wegen des Backlogs echt ist oder nur Teil der PC-Gaming-Kultur?

Du kannst dein Konto jetzt mit meinem neuen Online-Tool überprüfen (ich darf hier keine Links teilen)

Hey everyone,
I exported some stats from my Steam library and got mildly roasted by my own numbers.

My results:

Steam Reality Check:
- Total games: 341
- Never played: 96
- Completion rate: 72%
- Total hours: 4726
- Avg hours per game: 13.9
- Estimated total cost: €6820
- Sunk cost (0h games): €1920
- Time equivalent: 2.27 full-time work years
- Life burned at 8h/day: 1.62 years
- Weekend days gone: 197
- Main character game share: 14%
- Top games: Elite Dangerous, THRONE AND LIBERTY, PUBG: BATTLEGROUNDS, Counter-Strike 2, ELDEN RING

Shame Score: 100/100

Biggest surprise was how much “future me” has been buying for “one day”.

Out of curiosity:

• What’s your unplayed count?
• Which game dominates most of your total playtime?
• Do you think backlog guilt is real, or just part of PC gaming culture?

You can check your account now with my new online tool (I'm not allowed to share links here)

So long story short, you'll find it (won't post links here because its not allowed I guess) But i released a medium article about it:

Hi, I’m Felix Helleckes. A few weeks ago, I was sitting at my laptop, feeling nostalgic and slightly annoyed. Modern messengers often feel like bloated data farms: a single, monolithic tabbed app where everything is squeezed together, leaving you with zero overview. One ping from the wrong group is all it takes to completely destroy your focus.

I wanted something different — a small experiment to combine old-school comfort with modern tech.

The result? A desktop messenger with a classic ICQ 5 look, built using Electron + React. It features multi-window support, QR login for WhatsApp, and native Telegram integration. And yes, I actually use it every single day.

Why a Retro Design?

Because it’s incredibly practical. ICQ 5 had a beautifully clean feel: every conversation opened in its own window, so you always knew exactly who you were talking to. I brought that concept back — no tabs, no lost chats.

In daily use, this brings a surprising amount of focus. You can drag separate windows onto different monitors, focus on a single person, and keep your workspace perfectly organized.

Press enter or click to view image in full size

The Tech Stack (Quick & Concrete)

• Electron + React as the foundation — cross-platform, fast to develop.
• Multi-Window Architecture: Every chat opens its own BrowserWindow. These windows are managed in a Map and reused when reopened to prevent duplicates.
• Broadcast Pattern: All open windows stay synchronized via WebContents, ensuring updates land exactly where they belong.
• WhatsApp via whatsapp-web.js**:** Runs a headless Puppeteer instance to handle QR logins and persistent sessions (which are strictly gitignored).
• Telegram via GramJS: A real MTProto connection featuring native 2FA support.
• The UI: A dark-teal ICQ skin, custom title bars, stickers, images, an emoji picker, and font scaling (all styled using rem units).
• Windows Builds: Packaged as both an NSIS installer and a portable .exe for hassle-free distribution.

Small, Practical Decisions That Make a Difference

I kept the features intentionally simple:

• Font scaling via quick A- / A+ buttons.
• Contact windows running as independent BrowserWindow instances.
• Self-contained session folders kept out of the repository.

These tiny details ensure the tool stays stable in real-world use, rather than just looking good in a demo.

Press enter or click to view image in full size

Security & Limitations (Keeping it Real)

Let’s be transparent:

• WhatsApp is connected via a web API, which is unofficial. It works flawlessly, but there is always a minor risk that WhatsApp might flag or temporarily block sessions if automated rules are violated.
• Telegram runs through the official MTProto layer using individual API keys, making it highly reliable.
• Session files and .env configs are fully gitignored. You should never commit your session files or API keys to a public repository.

A Real-World Example: Partial Sells, Phantom Positions, and Balance Displays

During a test run, a trading bot running on my machine executed a few automated partial exits. On my stream overlay (yes, I stream the bot’s stats live), the numbers in the top-right corner lagged for a moment. This happened because the balance-fetching script aggressively limits requests to every 2 minutes to prevent hitting API limits.

The trade went through perfectly and the orders were correct, but the UI was out of sync for a few seconds — a classic case of async data lagging behind the interface.

>

The SmartScreen Hurdle on Windows

When you launch the portable .exe for the first time, Windows SmartScreen will likely show a warning. This is completely normal since the build isn't digitally signed (which costs a fortune for indie developers).

To run it, simply click “More info” ➔ “Run anyway”, or right-click the file, go to Properties, and check “Unblock”. It’s not pretty, but it’s entirely safe.

Why This Project Makes Sense in the Era of Signal & Threads

This tool isn’t meant to replace major platforms. Instead, it’s a productivity tool for creators, community managers, and power users who handle multiple accounts and contexts simultaneously.

The multi-window philosophy supports productive multitasking far better than an endless stack of browser tabs. Plus, nostalgia is a powerful UX tool — it doesn’t just look cool, it actually makes the software more enjoyable to use.

Key Takeaways (And What You Can Apply Today)

• Small UX choices matter: Giving each contact its own window and adding quick font scaling gives the user an immense sense of control.
• Session persistence is a game-changer: It makes for a seamless UX, but you must secure it properly via your .gitignore.
• Unofficial APIs are powerful but volatile: Always build fallback mechanisms in case an API structure changes.
• Decouple your data: If you are streaming or utilizing overlays, separate your data-fetching logic (like trades or balances) from your rendering engine to prevent UI freezes.

Give It a Spin — and Let Me Know What You Think!

The source code, the installer, and a short demo video are all available in the repository (link in the README).

If you want to try it out, grab the portable .exe, test the multi-window setup, and see how it fits into your workflow. I’m incredibly curious to hear your feedback—should we add better multi-device sync? Darker themes? Automatic window snapping for multi-monitor setups?

If you’re hesitant about the Windows SmartScreen warning, I’ve uploaded a quick walkthrough video on YouTube showing exactly how to safely unblock and run the app. Check it out, give it a try, and if you like the project, leaving a star on GitHub helps more than you think!

P.S. I didn’t build this purely for nostalgia. I built it to solve a real issue: How do I manage my chats without losing my mind in a sea of tabs? The result is more focus, less noise, and a nice touch of retro charm. Even if it sounds unusual at first, give it a try. Sometimes the simplest ideas bring the most joy.