r/opensource

So at work we need to do temperature checks on all of our fridges and freezers and write them down, in total there are 12 individual fridges and freezers that we need to check.

So I was wondering if there was an open source product or framework that would work on a raspberry Pi or similar that could upload data over an internal network every 10 minutes of the curent temperature on a sensor module.

I would like the ability to name each individual temperature probe as well and have it be able to be displayed on a Windows application (like a custom app that can turn the raw data into a more friendly format).

This would need to be able to auto reboot without human intervention in the event of a power outage as our backup is a manual process and isn't automated

If there is something that could do this already that would be great however if not I will probably build something from the ground up

I built a sign-up system that doesn't collect a single piece of personal data. No email. No password. No phone number. Nothing.

It's called Wisp - anonymous, email-free accounts a real person can return to. Drop a script tag on your site, and your users can create an account with a passkey, a copyable code, or just a guest session. The server stores a random ID and a public key or code hash. That's it. Nothing to leak because there's nothing there.

Here's the part where I'm supposed to pitch you on why this is the future. It's not. I know that.

The entire internet runs on a simple equation: you get a free service, they get your data. Every sign-up form with an email field isn't just authenticating you - it's the first step in a profile that gets sold, shared, breached, and sold again. Companies don't ask for your email because they need it to log you in. They ask because your email is the skeleton key that links you across their analytics, their ad network, their "partners," and eventually some database dump on a forum somewhere. We all know this.

Wisp breaks that equation. And that's exactly why almost nobody will use it.

Think about it. If you're a business, what does Wisp offer you? Anonymous users you can't retarget. No email list to sell to a "growth partner." No cross-platform identity graph. No way to spam them about a feature they didn't ask for. Just... people using your site. The horror.

So who is this actually for?

The small indie dev who runs a forum and genuinely just needs "can this person come back to their posts." The person building a poll site who doesn't want to become a data custodian. The hobbyist who knows that the best way to protect user data is to never have it in the first place.

What it actually does (honestly):

• User's browser solves a small proof-of-work puzzle (bot filter - not a wall, just a cost)
• User picks: passkey, copyable account code, or guest session
• Server stores a random user ID + public key or code hash. No email. No IP. No fingerprint.
• When they come back: same passkey or code, same account. That's the whole promise.

What it will never claim:

• "One account per person" - impossible without an identity anchor, and anyone who says otherwise is lying or fingerprinting you
• "Stops all bots" - the proof-of-work raises the cost, it doesn't build a wall
• "Replaces real auth" - if you need verified identity, this isn't your tool

It's free, MIT-licensed, self-hostable, and the entire honesty contract is in the README, including a claims table that says exactly what it can and can't do, with confidence labels instead of marketing promises.

I built the widget we all wish was just a normal part of the internet. It isn't, for reasons we all understand. But it exists now, and it works, and if you're one of the few people who actually don't need your users' data — here it is.

Links in comments.

note: Email Required to try it...

^jk obviously

TL;DR: Drop-in sign-up widget. No email, no password, no data collected. Passkey, code, or guest. Free, open source, self-hostable. Nobody will use it because there's no data to sell.

I’ve been working on TitaniumGuard DNS, an open-source Rust DNS server focused on operational control rather than being just a toy resolver.

It currently supports:

- DNS over UDP and TCP

- Optional DoT, DoH, DoQ, and DoH3 builds

- Authoritative zones for internal DNS

- Recursive resolution gated by trusted client CIDRs

- Policy enforcement across authoritative, cache, and recursive paths

- Memory or Redis-backed DNS caching

- Audit logging

- /live, /ready, and /metrics endpoints

- Prometheus-formatted metrics

- Docker

- A local-only MCP endpoint for status, metrics, zones, config summaries, and perform controlled DNS resolution through the same policy path

The MCP part is intentionally loopback-only right now. If someone wants to use it on a cloud host, the intended setup is SSH/VPN/proxy into the local MCP listener, not exposing it directly to the internet.

The project is still early, but the goal is to make DNS operations easier to reason about: explicit recursion authorization, policy-aware responses, scrapeable health/metrics, and container-friendly deployment.

I’m looking for feedback from folks who operate DNS infrastructure or write network services in Rust

Email and HTML have become excessively convoluted. To the point that it's difficult for new developers to get their feet wet with the underlying protocols without utilizing a library of some sort.

How would you design a new email protocol?

Current suggestions:

1. Easy to use for developers and users -- no huge servers required for sending basic messages
2. Encryption by default
3. Subject IDs for messages, so that they can contain threads
4. Voice messages
5. Federated, no central authority owns the technology
6. Protocol should be storage agnostic. Protocol should focus only on message delivery and receipt, with no concept of message storage.

I have developed an algorithm that I want to put into my open source project. However there is a commercial company in Australia that has the same type of algorithm (I don't know the details, but produces similar results) and they state "Patent Pending". I am in the US. Their AU provisional patent lapsed and I cannot find anything at the USPTO. I have searched for general terms, company name, inventor name, etc. However this has made me quite nervous of publishing my code. I am thinking of keeping that part of my application closed source and publishing a document describing my algorithm on my website. That way if they suddenly produce something I can pull the document. If I make the code freely available I lose control of copies, etc. Any thoughts on this? Also I emailed the company and they refused to give me a patent number. Thanks.

Thinking of building an old-school social network.

One central mail server, which allows users to subscribe to channels.

#channel@mailserver.com

Then broadcasts messages received to everyone on said channel. It also has an anonymous email for everyone on the server.

304954390@mailserver.com

So that you don't have to reveal your email to the group.

Anything like that open source at the moment?

I keep searching Google for open source mailing servers or listservs, and it keeps giving me one-to-many mailing list software.

tudo is a local, fast (built with Rust), keyboard (or mouse) driven todo list TUI.

I'm proud of this one, and I hope you find it useful! Let me know if you have any feedback or suggestions :)

• 10 different color themes
• Custom lists and tags
• Subtasks and notes within tasks
• Due dates and priorities
• Quick task search

I'm working on this regularly, and I'd love to hear your suggestions. Thanks for taking a look!

https://github.com/jolleyDesign/tudo

This one took a while, it's probably the longest thing I've written on this blog. I wanted to do a proper end-to-end walkthrough of cmd/compile: real package names, real data structures, diagrams for the AST and SSA CFG, and the flags you actually need (-m, -m=2, GOSSAFUNC, -S) to observe each phase yourself rather than just take my word for it.

Covers the full pipeline: lexer → parser → type checker → IR lowering → SSA construction → optimization passes (inlining, escape analysis, BCE, nil check elimination, register allocation) → architecture-specific code emission.

Hope it's useful — happy to answer questions or push back on anything that looks wrong.

Hello everybody,

So this is another post on how can I start on contributing to open souce projects... I've went through some of previous posts, recommended sites, tips but I felt a bit overwhelmed.

I have some background as a software developer in the industry (not much, around 3+ years) using C#/.NET but then decided to do a master degree in AI (before LLMs got popularised lol) and started using mostly python since around 4+ years ago, i still have much to learn... but still I belive helping others projects will help me improve my skills and understanding...

I never contributed before because I thought i never capable of (impostor syndrom? Maybe).

I just don't know where to start, of course the steps can be: pick a project that needs help, understand the problem and codebase, code away and practice.

I've seen there are some repos that add tags as "good first issue"... but I guess I’d love to know how y'all broke through that initial "impostor syndrome" (if you had it)... and found your very first project, I feel old and rusty with LLMs... but I'd love to help with AI tools, applications or similar things.

As soon as we make one honest mistake, sometimes due to a plain old and simple misundertsanding, or missing an important section in a lengthy documentation, reviewers immediately calls my hard work "AI-Slop".

I'm very close to give up now. Working so hard on the side with the very little time that we have, and getting slapped in the face like that almost every single day.

Code reviewers are burnt out with too much AI slop, and code submitters that are not even using AI are being labeled as using AI slop.

Is it happening to you? How do you cope with all of this?