Here's my GitHub link:

https://github.com/ivan8100

I was recently in a startup and built many stuff but I don't really have a good open source project and I have always wanted to build something like that, so if anyone wants to create a new project or something interesting,hit me up or if any of yall already building anything, count me in

Hi everyone! I'm a second-year B.Tech student who is passionate about building software, web applications, and SaaS products.

I currently have three startup ideas that I believe have good potential, and I'm looking for like-minded people to build them with me.

I'm looking for developers, designers, or anyone interested in startups and product building. We can work together, learn from each other, and deploy a real project.

If you're interested in collaborating, leave a comment or send me a DM. Let's build something amazing together!

Salut la communauté,

Je vous écris aujourd'hui pour vous présenter un projet de smartphone sur lequel je travaille sur le papier (en phase d'idéation pour l'instant, avec 0€ de budget) : OnePhone, et mon tout premier concept, le OnePhone 1.

L'idée est née d'un ras-le-bol assez simple et partagé par beaucoup de monde : le manque de choix sur le marché actuel.

Aujourd'hui, si on veut un smartphone récent pas trop cher, on est presque obligés de se coltiner une brique géante, fragile, compliquée à réparer et bourrée de bloatwares (surtout pour les téléphones low-costs).

Et le meilleur : On nous retire le bloc d'alimentation de la boîte sous prétexte "d'écologie", tout en nous mettant des capteurs photo poubelles de 2 MP juste pour le marketing.

Avec OnePhone, j'ai voulu prendre le contre-pied total de ces tendances. L'objectif est de créer un smartphone honnête, durable, compact et vraiment réparable.

Voici la fiche technique globale que j'ai conçue :

Le Format & L'Écran :

Un écran plat de 6,2 pouces (AMOLED, 90Hz, FHD+). Un format compact et que je trouve confortable pour une utilisation à une main (très rare aujourd'hui dans la moyenne gamme), facile à remplacer en cas de casse.

La Conception & Réparabilité :

• Châssis en polycarbonate mat (robuste, ne glisse pas, ne raye pas) fixé par des bandes adhésives (IP67, facile à ouvrir au sèche-cheveux). Pas colle qui bave quand on essaye de l'ouvrir ou de galère quand on essaye de le fermer

Les Performances & Matériel :

• Processeur MediaTek Dimensity 7025 (compatible 5G, compatible avec SP Flash Tool pour pouvoir bidouiller facilement).

• 8 Go de RAM (LPDDR4X)

• 128 Go de stockage (UFS 3.1) + un port MicroSD pour étendre la mémoire jusqu'à 1 To.

• Batterie de 4500 mAh avec charge rapide 33W

La Boîte (Unboxing Généreux) :

Contrairement aux marques mesquines, tout est inclus d'office : un chargeur rapide 33W, un câble tressé solide (USB-C vers USB-A)

• Des écouteurs Jack 3,5 mm (car le futur téléphone aura (normalement) une prise Jack !)

• Un adaptateur OTG (USB-C mâle vers USB-A femelle) pour pouvoir brancher des appareils USB-A ou pour avoir un câble USB-C vers USB-C.

Côté Photo :

Deux caméras. Zéro gadgets.

• Capteur principal Sony de 50 MP (OIS, stabilisé physiquement) pour de superbes photos même de nuit

• Capteur ultra grand-angle de 8 MP.

Pas de capteurs "poubelle" de 2 MP.

Le Logiciel : OneOS

Android 16 Stock sans bloatware imposé (un écran de configuration au premier démarrage permet de les désinstaller).

• 5 ans de mises à jour de sécurité garanties.

• L'intégration de "Al Battery Assistant Manager 🔋" : une IA silencieuse en arrière-plan qui apprend vos habitudes d'utilisation pour mettre en veille profonde les applis inutilisées et optimiser chaque mAh de la batterie.

Exemple :

La 1ère semaine d'utilisation elle observe :

Vous n'ouvrez pas Instagram entre 23h et 6h, elle le retiens.

Vous n'ouvrez pas TikTok de 9h à 18h, elle le retiens

Et à partir de la 2ème semaine elle endort ces applications pendant ces tranches horaires et continue d'apprendre avec le temps

• Application de sauvegarde préinstallée

• Application d'aide avec FAQ et ressources...

• Sûrement quelques bloatwares pour réduire le coût mais qui seront totalements désinstallables.

• Bootloader déverouillable via les paramètres développeurs

J'ai mis en ligne une petite landing page avec mon manifeste et une liste d'attente pour ceux qui veulent suivre l'aventure de près, pour obtenir le lien demandez le en commentaire =)

Je suis ouvert à toute suggestion, critique technique etc

Qu'en pensez-vous ? Est-ce que ce genre de smartphone compact, éthique et transparent a encore sa place sur le marché actuel ? Je suis ouverts à tous vos avis, suggestions et critiques.

Guys, please suggest a good IoT-based hardware project that is a bit unique and solves an environmental or daily-life problem. My budget is up to ₹8,000–₹9,000.

Hey everyone!

I’m currently building a modern web app and I’m looking for people who’d like to join the project as contributors or teammates.

This is a great opportunity if you:
Want to get into web development.
Want to build a portfolio with a real project.
Want experience working in a team.
Enjoy learning by actually building something.

You don’t have to be an expert. Curiosity, consistency, and a willingness to learn matter much more than years of experience.

The stack is centered around modern web technologies (React, Next.js, JavaScript, Tailwind CSS, and Supabase with TanStack Query), so if you’re interested in those, you’ll fit right in.

You’ll have the chance to:
Work on real features.
Learn Git and collaborative workflows.
Participate in discussions about architecture and UI/UX.
Gain experience that you can showcase in your portfolio.

I’m especially looking for frontend developers, but anyone who’s motivated to contribute is welcome.

If this sounds interesting, leave a comment or send me a DM with a little about yourself, what you’ve worked on (if anything), and what you’d like to learn.
Let’s build something people will actually use. ❄️

I'm working on a personal project that retrieves biomedical papers from PubMed and bioRxiv/medRxiv and I'm using OpenAlex to obtain citation counts. the issue I'm running into is that many records don't include a DOI in the metadata I'm parsing since I'm currently matching papers in OpenAlex using the DOI, those papers end up with a citation count of "0".

these are some of the approaches I came accross:

1. searching OpenAlex by paper title. but is this reliable enough?

2. Use better alt API for retrieving citation counts when a DOI isn't available. (eg. scopus API or Web of science API) but I am looking something free

or if you have a better approach please help me out :)

I am spending my hobby creating support software for my self-use and ended up with two first local software for my own Kanban board, notes, and documentation. **Both software are AI-compatible, meaning that you can make your own agentic AI recognise them and work with them seamlessly.**

The first is **Tossakan** (20-hands titan) board: a Kanban board for your own project/task management. This software includes:

* Basic Kanban features (Trello-like features) * Quick view: drawing the cards from every project sorted by due date

The second **Genesha**: The application for Documentation, diagram drawing, and whiteboarding. This software includes:

Workspace management: keep your documents grouped by workspace

* Confluence-like note features * Excalidraw-like whiteboard features * Mermaid diagram drawing and preview

**Downloads:** Both are Windows only (x64), self-contained (no .NET install needed)

* Tossakan: [https://github.com/panason-m/tossakan\](https://github.com/panason-m/tossakan) (releases: [https://github.com/panason-m/tossakan/releases\](https://github.com/panason-m/tossakan/releases)) * Genesha: [https://github.com/panason-m/genesha\](https://github.com/panason-m/genesha) (releases: [https://github.com/panason-m/genesha/releases\](https://github.com/panason-m/genesha/releases))

**Fair warning:** builds are unsigned, so Windows SmartScreen will flag them as "unknown publisher". Click "More info", then "Run anyway", or just build from source if you'd rather not. Both are early beta, MIT licensed, contributions and issues welcome.

These projects are still in an early phase; comments and suggestions are welcome :)

I'm currently building ExpectException as a place to experiment with AI automation, developer tools, backend systems, and practical software engineering.The goal is simple: build useful things, document the process, share what works (and what doesn't), and learn from the community along the way.

I'll be sharing things like:

• AI automation experiments
• Python, Django & React projects
• Backend architecture and APIs
• DevOps & self-hosted infrastructure
• System design ideas
• Developer tools and productivity workflows
• Build logs, tutorials, and technical write-ups

If any of these topics interest you, I'd love for you to follow along, try what I build, and share your honest feedback. If something is useful, awesome. If something can be improved, tell me.

I'm still actively working on this project, so suggestions, feature requests, and technical discussions are always welcome.

A few questions to get started

• What workflow would you automate if you had the right tool?
• What's the biggest engineering challenge you're working on right now?
• Is there a developer tool you wish existed but haven't found yet?

Looking forward to building this with the community.

Do you guys recognise what is it?

Hey everyone, I’ve been working on a VS Code extension called FileInsight. The goal is simple: tell me exactly what a file does, what it depends on, and which file uses it, just by hovering over it in the Explorer sidebar (you dont need to open the file).
It builds a local dependency graph, parses ASTs (for TS/JS), and uses Regex for other languages to calculate file metrics. It categorises files (Core, Utility, Config, etc.), detects dead code, and checks Git history to see if a file is "hot" or "stale".
I need your honest, brutal feedback. I want to know where it breaks, if the UI feels clunky, or if the dependency graph chokes on massive repos, etc.

Core features:

• Rich Tooltips: Hover to see exports, imports, complexity, and TODO counts.
• File Classification: Automatically tags entry points, core modules, configs, etc.
• Dead Code Detection: Warns you if a file seems completely abandoned.
• Live Refresh: Re-analyses incrementally when you save.

Here is the link: https://marketplace.visualstudio.com/items?itemName=AdityaGupta0205.file-insight
Tear it apart. If it sucks, tell me why it sucks so I can make it better. Thanks!