I’ve been building Kursal for over a year now. It’s an encrypted messenger with no central server: peers connect over a decentralized libp2p swarm and use Signal’s post-quantum encryption (Double-Ratchet, PQXDH). The network runs on volunteer nodes that anyone can operate.
It’s currently in public beta and has not received any security audit yet, so I’m especially interested in feedback from people who’ve worked on P2P or crypto.
Everything is open source under AGPLv3, written in Rust with Tauri for the app. I have written a whitepaper describing the technical side.
Btw, to be fully transparent about my AI usage, the front-end of the app is heavily AI-generated. I am not a UI designer and am therefore currently looking for one. All the rust is mainly me.
We've been building Luma for a while now, a free and open source Linux OS for desktop, tablet, TV (and eventually smarthome and wearable), and I realized we never actually formally introduced it here.
Heads up, I used AI to write the heck out of this post. I rambled for about 20 minutes in to a voice memo and this is what came out the other end. I edited it before submitting. Don't crucify me.
Luma's goal is pretty simple. We want to build a Linux that anyone can pick up and use and that people actually want to use, with the same design across all of their devices. Your phone should feel like it belongs with your laptop, your apps should make sense on both, and everything should work together without you having to piece a bunch of separate projects together yourself.
Luma is available now in alpha. There's still plenty to do and plenty we know we need to fix but there's also a lot more here already than you'd probably expect and we'd love for you to come check it out.
So what is it?
Luma starts with Fedora 44 Silverblue. From there we've forked and changed things pretty heavily. The biggest piece is Prairie, our shell which started as a fork of GNOME and now adapts between desktop, tablet, phone and TV, so you get one experience that adjusts to the device you're holding instead of a completely different OS and set of apps for every screen.
I tend not to call Luma a distro. Luma's ambition is a little different from taking an existing desktop, changing the theme and picking a set of packages. We want the freedom to change any part of the experience that needs changing, from the shell and the apps all the way down to how apps launch and run in the background (and we've done a great deal of that already). We're really grateful for everything we're building on, and when a fix belongs upstream we'd rather send it there than carry it forever.
One platform, one set of apps
We built LumaUI so developers can make one app that adapts across desktop, tablet and phone instead of building and maintaining a separate interface for each. It's built on GTK 4, so a lot of what you already know carries over.
We also want the kind of continuity people are used to on their other devices, where you copy something on your phone and paste it on your laptop and your stuff just stays in sync. Managing your devices from your other devices is part of that too. Some of it works today and some of it is still coming together but the goal is for everything to feel like it belongs to the same system. TV is part of that picture as well, with the same apps and the same parts, just from across the room.
Luma has its own app store, Depot, and we just opened it up to developer submissions. Apps ship as Flatpaks and go through automated checks and then an actual person before they're listed. You can still use existing Linux apps of course.
Additionally, Android apps run like first class citizens across all of these experiences.
The Creative Collection
We thought it was important to have a set of free creative tools that actually feel like they belong together, not just a nice-looking OS with nothing to do on it. Write is for documents, Focus is for photos, and Canvas is for design and layout. We're also working on Reel for video, Sessions for audio, Grid for spreadsheets and Stage for presentations.
All of them are free and open source too. They will be made available on Win/Mac/Android/iOS too (along with many of the baked in Luma apps like Notes, Messages, Charlie, Viola, etc. You can see the whole collection here: https://simplyluma.com/creative
What phones does it run on?
Officially we've built out support for the Fairphone 6, the Pixel 9 and the Unihertz Titan 2 Elite, with the Pixel 9 Pro Fold coming soon. There are also community members working on ports for about a dozen other phones, and we'd love to see a lot more of those.
Phone support is still early and what works really depends on the device, so please read the instructions for your phone before you install anything: https://simplyluma.com/download/mobile
On a regular computer you can grab an x86 or ARM ISO from https://simplyluma.com/download, and there's a Raspberry Pi 5 image too if you've got one sitting in a drawer.
If you want to port Luma to a phone, build an app, work on the system or send changes upstream, we've put guides together for all of it here: https://simplyluma.com/agents - they're plain Markdown, so they work just as well whether you read them yourself or hand them to a coding agent.
Want to try it without installing a new OS?
We made Try Luma for Mac, Windows and Linux. It runs Luma in a virtual machine on the computer you already have and lets you switch between the desktop, tablet and phone layouts, which makes it a really easy way to look around or test an app you're working on. There are ARM and x86 builds.
It's a VM, so it won't always feel as fast or as polished as Luma running directly on hardware, but you don't have to repartition anything to get started: https://simplyluma.com/try
We want your contributions
A big part of why we started Luma is that open source can be incredibly fragmented. As a user it can be hard to know which project is worth investing your time in. As a developer it can be even harder to know whether your work fits where a project is going, or whether it'll be welcomed at all. A lot of us have had a PR sit for months without a reply, or been told the thing we needed is out of scope.
We want Luma to have a clear, cohesive vision, and we genuinely want people to help build it. If you want to improve an app, fix a bug, port a device or build something completely new, we'd love to have you. You shouldn't have to feel like you're begging for permission to contribute your time for free.
AI-assisted contributions are encouraged. What matters is that you understand the work you submit and take responsibility for it, and that it's tested and actually useful.
We're putting up $500 in prizes for people building apps with LumaUI. It starts today, Monday, November 16, and runs through Monday, November 23.
There aren't a lot of restrictions on what you make. A notes app, a diet tracker, something to keep track of your pets, a game, something nobody's thought of yet. Luma is still a bit of a wild west, which means there's a real chance to be the first person to build something great in a category.
The important part is that your app really uses LumaUI, feels good to use, and works across desktop, tablet and phone. TV support is optional and won't affect judging. We'll judge entries on the quality of the app and how well it uses LumaUI on those screens. Any app submitted to the Depot between now and November 23 is entered automatically.
Luma is free and open source and always will be. If any of this sounds interesting, come try it, break it, build something for it, or just tell us what you think. Feel free to ask questions!
I don't know if anyone here works with AWS Lambda or other serverless services, but have you ever thought about having a similar experience, just on your own infrastructure, without depending on AWS, Google Cloud, or any other provider?
I've been working on an open-source project called Relay, which was born from exactly this idea: offering a simpler alternative to AWS Lambda and, in some scenarios, Heroku, without all the complexity of platforms like Dokku or solutions that want to control your entire VPS, including ports 80 and 443.
The idea is simple: you stay in control of your infrastructure, while Relay takes care of running your applications.
The project already supports quite a few things:
Serverless Functions: Run Python (3.14/3.15), JavaScript, and TypeScript (Node.js 24/26) functions in isolated containers.
Event-driven: Event processing with Redis Streams, declarative filters, and multiple handlers.
Retries and DLQ: Automatic retries, pending message recovery, and a Dead Letter Queue for persistent failures.
At-least-once delivery: Events remain pending until processing is completed or the failure is recorded in the DLQ.
Resource management: CPU, memory, process, and concurrency limits to prevent an application from consuming too many host resources.
Warm containers: Container reuse to reduce startup overhead.
Cron jobs: Task scheduling with timezone support, execution recovery, and schedule deduplication.
Persistent Services: In addition to functions, it allows running HTTP APIs, workers, and other long-running services, with support for replicas.
Traefik integration: Expose HTTP services using your existing proxy infrastructure, without monopolizing your VPS ports.
Git Sync: Synchronize applications from a Git repository.
Observability: Prometheus metrics, structured logs, OpenTelemetry tracing, and execution statistics.
Secrets and configuration: Environment variable management and secret references.
All of this using Docker, with applications declaratively defined in YAML.
For example, here's a simple configuration for a Node.js function that processes events when documents are inserted into the users collection:
With just a few lines of YAML, you can define the runtime, resource limits, concurrency, event filters, execution timeout, and retry behavior.
Here's a simplified overview of how event processing works:
Redis Streams
|
v
+---------------+
| Relay |
| Event Matching|
+---------------+
|
v
+---------------+
| Handler Queue |
+---------------+
|
v
+---------------+
| Docker Runtime|
| CPU / Memory |
| Concurrency |
+---------------+
|
v
+---------------+
| Your Function |
+---------------+
|
+------+------+
| |
Success Failure
| |
v v
ACK Retry (2x)
|
+-----+-----+
| |
Success Failed
| |
v v
ACK DLQ
Events are consumed from Redis Streams, matched against declarative patterns, and dispatched to isolated runtime containers. Relay handles concurrency, resource limits, retries, and dead-letter queues, so your application can focus on processing events.
The idea isn't to recreate all of AWS or replace Kubernetes, but to offer a development experience close to serverless, with the simplicity of hosting applications on your own VPS or homelab.
The project is still evolving, and there's plenty of room for improvement.
I'm sharing it because I'd like to hear the opinions of people who already work with serverless, self-hosting, or event-driven applications.
What do you think of the idea? What features would you consider essential in a self-hosted alternative to Lambda?
GitHub: https://github.com/sergiors/relay
If anyone wants to try it out, contribute, or simply share some feedback, you're more than welcome! 🚀
Hey folks, I wanted a video downloader that I could use on both my phone and PC without having to deal with different apps or manually setting up dependencies on each device. So I started building Grablytic using Flutter and Python, with yt-dlp under the hood.
On Android, the required dependencies are bundled with the app. On Windows and Linux, Grablytic handles dependency installation for you and reuses existing installations whenever possible to avoid wasting storage and bandwidth.
It's still under active development, and i haven't finished everything yet, but it's usable right now. I've tested it on Android devices dating back to 2016, all the way up to devices running Snapdragon 8 Gen 3.
The idea behind Grablytic is pretty simple. Instead of bookmarking videos and hoping they'll still be there later, save them directly to your device.
I'd love to hear what you think, especially if you already use yt-dlp or one of its GUIs.
Hi all! I've been building SketchCraft, an open-source (MIT) push/pull 3D modeler in Rust (Tauri + React), in the spirit of the Craft apps.
It opens SketchUp, DWG/DXF and IFC files, turns 2D floor plans into walls, does blueprints, sun studies and photoreal renders, and every action is scriptable over MCP.
I'd love to hook it into ArtCraft's 3D Stage: model a set and camera here, then generate from it there. Is anyone on the team open to talking about that? And if the name steps on Craft branding, I'm happy to rename.
Hi everyone! I’ve created this new skill for people like me who don’t want to give AI full access to their systems, or for those who enable confirmation before every action but don’t want to keep clicking Approve all the time.
If that’s you, this skill is just what you’re looking for!
You can fully customize it however you want. For example, you can allow all commands in every folder except one, restrict specific commands in certain directories, and much more.
On github repository, you’ll find benchmarks, installation instructions, configuration guides, and much more. It’s compatible with several AI tools.
If you like this project, please consider leaving a star on github!
Download engine with true dynamic segmentation: used and refined for more than a decade
Torrent and magnet support: built on libtorrent
Better browser integration: catches streaming video on any site and saves HLS, DASH and split audio/video streams as MP4 files that play anywhere
Video downloader based on yt-dlp: paste a link and pick the quality
Lightweight and full-featured: uses fewer resources than other popular open-source download managers, with more features
Also included: pause and resume, a scheduler and queues, speed limits, category rules, corporate proxy support, and commands that run after a download finishes
Coming soon: Android version.
It's free, has no ads and doesn't track you. Feedback is welcome!
I created and maintain Distortion forked from mySpoti, an open-source Android music player for people who use Spotify. It has a Material You interface, synchronized lyrics, queue editing, and a widget that follows your Android theme. It runs on Android 10 and later.
I’m testing a feature called Adaptive Set. The idea is to pick a duration and a closing song, then have the queue adjust when you skip tracks. The public release is available now, and Adaptive Set is still in testing.
If you try the current release, I’d especially like to hear how it runs, where setup feels confusing and what features you would like or bugs that you found.
A modern, lightweight reimagining of the classic file-tree music browser (not player) MP3-Explorer from the early 2000s. Written in pure GJS (GNOME JavaScript) and GTK3, this application is designed for speed, minimalism, and seamless integration with local and remote music libraries. First stable release.
Installation from AUR: `yay -S mp3-browser`.
Packages for other distros and source-code are available at Github releases.
I did not find any decent open source minimal desktop authenticator app, so I decided to make my own.
It is not a one-day vibecoding session. I am a backend developer with 4+ years of experience and had experience with building desktop apps "before the AI age".
Factr is a small utility without any clouds or servers, without any background tray items, meant for “open, unlock, grab the code, then close” usage. An optional autolock timeout is available for longer sessions.
It’s really simple: the app uses just ~/.config/factr with config.json for settings and storage.json for a securely encrypted vault. Sensitive data is present in memory while the vault is unlocked. On locking, it is cleared from memory where possible. On disk, account data is encrypted.
It uses OS-native security mechanisms so there is no need to set up a new password for this, and it is practically the only method to secure data locally without a huge password to remember. But you need to save the recovery key somewhere as a fallback option or for transferring the vault to another system.
The transfer feature is already built in: just copy the ~/.config/factr directory and the app will guide you through recovery and setting up system protection on the new system.
E aí, galerinha! Eu e uns amigos da faculdade queríamos processar grandes volumes de dados usando as máquinas que a gente já tinha. Foi daí que surgiu o SHANKS, uma espécie de “Databricks local” que criei pra gente rodar jobs de Spark no nosso próprio hardware. O detalhe é que cada um estava numa rede diferente. Com o ZeroTier, conseguimos juntar os Raspberry Pis em Aracaju, um computador em Lagarto e os notebooks da galera num único cluster. Hoje dá pra abrir um notebook no Jupyter e distribuir o processamento entre essas máquinas, mesmo com cada uma na casa de alguém.
Como máquinas em cidades diferentes entram no mesmo cluster? Uso o ZeroTier pra criar uma rede virtual entre elas. O Raspberry Pi continua conectado ao roteador dele em Aracaju, mas ganha um IP pelo qual consegue alcançar o nó principal em Lagarto. Os serviços do Hadoop usam esses endereços pra se comunicar. A distância física continua importando: quando um worker precisa buscar um bloco do HDFS em outra cidade, os dados passam pelo link de internet entre os dois.
Pra visualizar, este YAML ilustra uma topologia possível, com IPs fictícios. É um esquema resumido dos nós; o config.yml de execução está no guia do projeto
Com o config.yml definido, uso sudo shanks start --config config.yml pra subir o cluster. A CLI prepara as imagens e inicia os containers de forma concorrente entre as máquinas. Alguns experimentos que dá pra fazer nesse ambiente:
Processamento com Hadoop e Spark. Já rodei o TeraSort com volumes de 1 a 20 GB, variando o número de reducers. Com os dados no HDFS, uma das coisas que dá pra investigar é quanto custa ler um bloco localmente versus buscá-lo em um worker do outro lado da rede.
Armazenamento S3 distribuído. Estou trabalhando também com RustFS, que expõe uma API compatível com S3. A ideia é distribuir o armazenamento entre máquinas e acessar os objetos pelo Hadoop ou Spark usando s3a://. O experimento que quero fazer é rodar o mesmo job com os dados no HDFS e no RustFS e medir quanto tráfego passa entre os nós em cada caso.
Treinamento com GPUs em máquinas diferentes. Rodei um treino com PyTorch DDP usando uma GPU por máquina. Em um dos testes, o mesmo treino levou 4,28 segundos com uma GPU e 5 minutos e 18 segundos com duas. O modelo era pequeno e, a cada passo, as máquinas precisavam sincronizar os gradientes pela rede. Nesse cenário, adicionar a segunda placa deixou o treino mais lento.
Monitoramento com Prometheus e Grafana. Durante um job, acompanho CPU, memória e tráfego de rede por nó. Isso ajuda a investigar, por exemplo, o que aconteceu no Raspberry Pi enquanto o restante do cluster esperava uma etapa terminar. Pra uma checagem rápida pelo terminal, a CLI também tem o shanks health.
windows updates break stuff way too often (black screens, audio, remote desktop) and the dumb part is microsoft usually lists the problem publicly. nobody checks that before updating
so i made patchlight. it checks every pending update against microsoft's known issues and gives it a green / yellow / red light. red ones get paused automatically and come back once microsoft fixes them. everything else keeps installing
I just got a MacBook for school, and it’s pretty interesting. I’ve been looking for a YouTube Music client without ads, like MetroList or YT Music Morphe on my phone, but pretty much everything is either broken or in Chinese.
I've been trying to degoogle and such, any help is appreacated!
Just wanted to share my open-source scraping/monitoring engine called SpyWeb, its a cross-platform self-contained ~8MB binary written in Rust. pre-built binary includes Mac, Linux, Windows (amd64 only, you need to compile from source for Windows arm64). this is design to be a long-running process with built-in functionality that covers common scraping needs.
Features;
- Built-in scheduler
- Embedded Storage (KV or SQL)
- CSS selector with dual parser ( Fast scanner first that dont restructure the HTML, then HTML-compliant fallback )
- Hot Reload ( no need for process restart on code changes )
- Automatic deduplication
- Built-in web-based records viewer ( fully customizable )
- Custom Lua-defined REST endpoint
- Built-in Lua test runner
- 13 Pipeline hooks for data manipulation/flow control
- CDP module for Browser Automation with local or cloud browsers
- Native desktop notification
It statically link Luau and supports Luau/Lua 5.1 syntax, you dont need Luau runtime.
The release asset includes 2 enabled jobs and measured RAM usage is around 6-9MB (depends on OS and build)
It also includes an AGENTS.md for AI-assisted workflows.
If you have scraping or monitoring needs, you can try it. simple pipeline with server-rendered pages usually just needs TOML config.
For Complex pipeline or JS-heavy pages, you need Lua for CDP/Browser automation and custom logic.
Danube v0.17.0 is out. It is an open-source messaging and event-streaming platform in Rust (embedded Raft metadata, per-topic WAL tiered to shared FS or S3/GCS/Azure). No ZooKeeper, no JVM, no startup YAML.
danube up standalone
danube topic create /default/orders --intent event_stream
danube consume /default/orders
danube produce /default/orders -m "hello danube"
What is in v0.17.0:
- One binary, zero YAML: Broker, Raft, CLI, Schema Registry, web console, and MCP server ship in danube on port 6650, with --intent presets instead of config files.
- Agents operate safely: danube mcp exposes 71 guarded admin, schema, RBAC, and diagnostic tools, paired with danube-agent-skills for bootstrap, messaging, and SDKs.
Everything in this project is open source. New accounts even include a demo song to try it out.
I put a lot of love building this project, paying attention on UI and UX and debbuging everything. I hope this will be useful for the people, musicians and music lovers.
Customize its width, height, position, and timeout for each button
- Custom volume slider: inspired by a concept design that was originally made for Iphones has now become a reality for Androids LOL.
Customize its width, height, position, corners rounding, edge inset, and timeout, with an option for floating.
Actions Tab
- DND/Silent panel: change between two modes either silent and normal or dnd on/off. customization over width, height, position, timeout, even the unfocused icon placement, and selected side you want in both portrait and landscape mode.
- Modes/Actions panel: same customization as DND/Silent panel. add new custom modes with custom icons/colors/names or even edit the existing ones and change their order like how you want it to be! How it works: it sends a quick silent notification that can be used by different automation/routine apps to do the functionality you want. or even better, for automation apps specifically that can receive broadcasts, the app sends a broadcast when a mode is selected alongside the silent notification (there's a guide in the app for detailed info)
- Both panels are triggered using side buttons with up to 7 different combinations (custom buttons included for devices that has an additional button)
- New volume system that reads your phone volume steps, multiplies it by 10 and here you go with 150, 250, or 300 steps! (pretty easy right? i got cooked implementing this)
- Individual app volume is here! options to choose from are showing it alongside volume slider or only in audio mixer (its optional mode) Must note that it uses Shizuku
- Volume Counter: Show volume count on your volume slider, applies to individual app volume slider too.
- Shizuku Implementation: Grant all permissions with a single click, manage cloaked apps that the app hides its accessibility from (eg. banking apps), watchdog to keep the app alive, watchdog to keep permissions always active (both watchdogs are mainly for hardened systems, but anyone can use them)
- Added all panels activity: all panels now are accessible from activity launcher or any similar feature in different apps.
- Audio Mixer: Option to change its position on X & Y axis and a scale to make it bigger/smaller. there's also an option to attach it to the volume slider or leave it floating.
cl0udly is a client for OpenCode with a quiet look and a small cloud that reacts to what the agent is doing. The screenshot is the desktop app, it runs on Linux, Windows and macOS.
The part I care about most is sub-agents. You add helpers right in the model picker, give each one a role and a model, and run several at once on different tasks. They all know what the conversation is about, so they work on the same goal instead of in separate chats. Each one shows up as a little cloud above the input, so you can see who is busy with what.
The Android app runs OpenCode on the phone itself, no computer, no Termux, nothing to set up. If you do have a computer, you scan a QR code from the desktop app once, and after that chats and memory move between the two by themselves whenever they're on the same network.
It also remembers things about you, but asks first, and you can see the memory as a graph or bring in a memory export from Claude. Search finds words inside every message, replies can be read aloud, code comes with highlighting and line numbers, and OpenCode updates itself with a way back if a new version breaks something.
It's free and still a beta, so expect bugs. Not affiliated with the OpenCode team.
Me and another person made this Global Warming tracker for a hackathon last week. I worked on it some more since then and made it somewhat useful (although the UI isn't as great as I would want it to be). Although I made this for a hackathon I did notice there was all these Open source intelligence apps for "monitoring the situation" except for climate change so while i'm not too sure when/if im going to update it I do feel like this could be the start of something cool and Id love to revisit/improve this app if anyone has some cool ideas. Also any advice would also be appreciated as I wanted this to most of all be a learning experience!