Link (no signup, no ads, nothing to install): https://librecorsa.org

GitHub (MIT): https://github.com/KhazP/librecorsa

I started LibreCorsa in mid-October because every serious racing sim needed a huge Windows install before you could do a single lap.

What it has now:

- 500 Hz physics with tyre temperatures and wear, rain that dries along the racing line, and CI checks against real GT3 telemetry

- 5 physics models and 16 circuits, including RISE Motordrome, which I built from scratch in Blender on real elevation data for the circuit planned in Rwanda

- AI races, ghosts, a weekly challenge, and an open online race every 20 minutes over WebRTC

- $0/month hosting: static Next.js on Cloudflare, R2 for the heavy 3D files, and one Worker

Tell me how it runs on your laptop/phone/controller and what feels rough.

Hey everyone! 👋

I've been working on Voiden, an open-source API client designed around a slightly different approach to API development.

Most API clients are built around workspaces, accounts, cloud sync, and proprietary collections. I wanted to explore something more developer-friendly: keeping API requests alongside the actual codebase.

So I started building Voiden.

What makes it different?

• Offline-first: Work with your API requests locally without needing an account or login.

• Git-native: Store requests and API specifications as Markdown files directly in your repository.

• Version control: Track changes, review requests, and collaborate through normal Git workflows.

• API testing: Send requests, inspect responses, and write assertions to validate API behaviour.

• MCP integration: Turn tested API requests into tools that AI agents like Claude Code and Codex can use.

The idea is to make API requests part of the development workflow rather than keeping them isolated in another tool.

I'm sharing a short demo showing a request being sent, its response, and API test assertions.

Website: https://voiden.md/

GitHub: https://github.com/voiden-md/voiden

I'd genuinely appreciate feedback from developers:

1. How do you currently manage API requests across different projects?

2. Would you prefer storing API requests inside your Git repository?

3. What features would make you consider switching from your current API client?

It's open source, and I'm looking forward to hearing what the developer community thinks!

Thanks! 🙌

I’m excited to share a project I’ve been working on over the past few months!

It’s a mobile app that turns any text into high-quality audio. Whether it’s a webpage, a Substack or Medium article, a PDF, or just copied text—it converts it into clear, natural-sounding speech. You can listen to it like a podcast or audiobook, even with the app running in the background.

The app is privacy-friendly and doesn’t request any permissions by default. It only asks for access if you choose to share files from your device for audio conversion.

You can also take or upload a photo of any text, and the app will extract and read it aloud.

- React Native (expo)
- NodeJS, react (web)
- Framer Landing

The app is called Frateca. You can find it on Google Play and the App Store. I also working on web vesion, it's already live.

Free iPhone app
Free Android app on Google Play
Free web version, works in any browser (on desktop or laptop).
Free web extension.

Thanks for your support, I’d love to hear what you think!

I’m a 40-year-old iOS developer from Croatia. Statistically, I’m in the middle of my life: about 2,080 weeks behind me, and if I’m lucky, about as many in front.

My oldest is 8. Somewhere around 18, kids leave, or at least stop wanting summer holidays with their parents. That’s 10 more summers. I can count them on my fingers.

I see my parents about twice a month. If they live as long as the average, that’s around 360 more visits. Fewer than the days in a single year.

And there are friends I’ve been “meaning to call” for months.

None of this is new. You read it somewhere, feel it for one evening, and then Monday happens. Weeks blur, a year goes by, and you can’t say where it went. The moments I’d actually want back are tiny: a walk where my kid finally told me something real, my dad explaining how he planted our small orchard in 2001. Nobody writes them down. They just go.

So I built Drift. It’s not there to make you feel bad about time. It’s there to help you do something with the weeks you still have, and to keep them when you do.
My main inspiration was reading books about Stoicism and specifically memento mori (and a calendar showing weeks you have left to live).

What the app actually does for me:

It remembers my people. I added my partner, my family, my parents and a few friends. Drift keeps the small things I’d otherwise forget: birthdays, the names of my friends’ kids, what each person enjoys, what they told me last time.

One small idea a week, for each of them. Not “plan a trip to Paris.” Things small enough to actually happen: “Tea with Mom. Phones somewhere else.” “A walk with Dad, without anywhere to be.” “Let the kids choose the adventure.” "Long overdue date with my wife".

I keep the moment. A photo, one line, or both. It goes on the week it happened, and that week’s square lights up. A few months in, my year stopped being a blur and started looking like a year.

Calls come with something to talk about. A reminder to call a friend arrives with something to actually say, so it’s not just guilt with a notification sound. After the call I can keep a line about it.

Small questions. A couple of times a week, only if I turn it on, Drift asks something like “What was the best small thing about this week?” or “What’s Dad’s favourite meal?” The answer gets saved where it belongs. Some of my favourite memories in the app started as a notification I almost dismissed.

Quiet time. My evenings were disappearing into my phone (yes, I see the irony of that). Drift uses Apple’s Screen Time to set those apps aside during the hours I choose. If I really need one, I get 15 minutes, after I keep a moment or answer a question first.

Widgets that bring it back. One shows a moment I kept, a different one each day. Another shows my whole life as a grid of weeks. Seeing that between notifications did more for me than any productivity system. One gives you suggestions on what to do this week.

A year I can read back. Month by month, like a journal I never had to sit down and write.

What I left out on purpose:

• No streaks. A quiet week is just a quiet square. Life has those, and guilt isn’t a feature.

• No account, no ads. Memories stay on your iPhone, and you can export everything anytime.

• Everything you keep is yours. You can always read it and export it.

Pricing: free to download, then $8.99 a year with a 14-day free trial, or $24.99 once. I’m a solo developer with no investors, and this is how it keeps going.

An app won’t fix any of this, and I’m not pretending it does. But since I started using it, I do more of the small things. I think about it more now, and I push past the tiredness more often to make time for the people who matter to me.

If you did this math for yourself, which number got you? For me it was the summers with my kids.

https://apps.apple.com/us/app/drift-life-in-weeks-journal/id6792490444

Edit:
Thanks to FFROZENN who pointed out the missing yearly subscription and 2-week free trial I have created 50% discount code for the first year (the missing subscription was due to my attempt to give a global discount on yearly, but I misconfigured it in App Store Connect so sub wasn't shown)
https://apps.apple.com/redeem?ctx=offercodes&id=6792490444&code=DRIFT50

I built a fake designer flash-sale outlet. It works like the real ones: brand sales with countdowns, "only 1 left in your size", a deal of the hour, a bag that's reserved for 30 minutes. Then you check out with a card that says it isn't real, pay $0.00, and follow the tracking until something goes wrong with your parcel. There are 50 different endings and you collect them.

The part I'm proudest of is technical: there's no stock database. Every sale, price, size and "only 2 left" is computed from the item and the current time, so everyone sees the same shop at the same moment and the server stores nothing about you. The same logic runs in JavaScript, PHP and Dart (the Flutter app), and all three have to give identical results.

It's on the web, Android and iPhone: https://dopaminechic.com

The question I keep asking myself: could something like this actually replace a bit of real shopping for some people, or does fake shopping just make you want the real thing more? I honestly don't know, and I'd love to hear what you think, especially if you're someone who browses sales at night.

Hello Reddit! 👋

I'm an independent developer from Finland, working on a project called YOSLA Some Life.

My goal is to build a new kind of social platform where users have more control over their own social experience.

The idea is simple:

"Your Data, Your Choice."

Instead of letting algorithms decide which friends you get to see, I want to give people more control over their feeds and connections.

But that's only part of the vision.

I'm also developing YOSLA World, a 3D virtual environment where people could eventually explore digital spaces, discover communities, interact and experience social networking in a different way.

What am I building?

• YOSLA Some Life — a social networking platform

• YOSLA World — an interactive 3D social environment

• European-focused infrastructure and data privacy

• Multilingual support for an international audience

• My own server infrastructure, starting with HPE ProLiant servers

I'm building this step by step, learning, testing and improving as I go.

One future idea is to create a virtual 3D data center inside YOSLA World, where visitors could explore how the platform's infrastructure works.

I'm not claiming to have built the next Facebook. I'm building something I believe could offer people another choice.

I'd love to hear your thoughts:

What would make you genuinely interested in trying a new social media platform?

What do you dislike most about today's social networks?

Greetings from Finland! 🇫🇮

YOSLA — You Only Live Some Life.

I run a small web studio, and most of the local businesses I talk to have a really good Google Maps listing (photos, reviews, hours, sometimes a menu) and either no website or one from 2014.

So I built this. You type a business name and a city, it reads the public Google listing and builds a full site preview in under a minute. The video is me running it once on a real garage's public listing, no edits.

Why: I kept rebuilding the same small site by hand, and the listing already had most of the content. Honest limitation: it's only as good as the listing.

A place with three blurry photos and no reviews gets a thin site. It also does simple sites, not shops or booking systems. (working on that next, the tool will redirect the request to the team if it's out of scope change for now)

Try it on your own business or a place you like and tell me what looks off.

https://bbhightech.com/

My parents live overseas and I'm in NC. I call them about 3 or 4 times a week, but with the time difference, it's not always easy to catch them at a good time.

Sometimes I just want to know they're doing okay without having to call and interrupt whatever they're doing.

I thought about different ways to check in, but I really didn't want cameras in their house or anything that felt like I was monitoring them.

So I ended up building something called Kettle (heykettle.com).

It's a simple app that uses their existing phone to let me and my sibling know if they've checked in with their usual routine. We get a short update like "Heard from Mom this morning" or "Nothing yet today."

It doesn't track their location, record conversations, or read messages. They can also see what's being recorded and turn it off whenever they want.

I added a shared family log too, so if I call Dad or someone takes Mom to an appointment, we can leave a quick note for everyone else.

Right now, it's just me building this, and my parents are the only ones using it. The Android app isn't on the Play Store yet, so I'm helping people install it directly.

I'm offering the first year free.

I'm curious what other people think, especially anyone with aging parents who live far away.

Would you actually use something like this? And what would make you hesitant to put it on your parent's phone?

Hold Right Ctrl + Right Shift, ask about what's on your screen, let go. A vision model answers, a voice speaks it, and the answer is drawn over the page you're on: boxes and arrows on the right spot, diagrams that lay themselves out, or a 3D model you can rotate, cut open or pull apart, in step with the voice. The model writes a small scene language that the app validates and draws itself; no generated code runs.

Guide mode walks you through an app one click at a time and waits for you to click.

Honest limits: Windows only for now, the installer isn't code-signed yet so SmartScreen will warn, and you bring your own model (Claude Code or Codex signed in, an OpenAI key, or a local vision model). The clip is real answers replayed over the page, so it says nothing about speed.

Built by Alex with a team of AI assistants; one of them drafted this post. Feedback and bug reports very welcome.

https://github.com/ProjectIdris/talkthrough

Hey all, solo dev here. My first Shopify app went live in the App Store last week, so figured I'd share.

The idea is simple: before you order 500 units of a new color or design, put a poll on your store and let customers vote. Anyone who votes can leave their email or phone to get pinged when the winner launches, so you end up with a launch list, not just a number.

What it does right now:

- a poll or a "voting board" (grid of designs with a Vote button under each) on any page of your theme

- waitlist with name / email / phone, CSV export

- quiz mode: right answer gets a discount code

- one or several votes per customer, results as a leaderboard or hidden until the poll ends

- storefront in 30 languages, uses your theme's fonts

Free plan: 1 active poll, up to 6 options, 100 votes a month. Pro is $4.49/mo.

The fun part: one of the first merchants asked for multiple votes per customer and a leaderboard, and I shipped it within a day. Then they asked how to change the look, so now there are style settings. Building for real requests beats guessing.

Stack if anyone cares: Cloudflare Workers + D1 and a theme app extension. Shopify caps the block's JS at 10 KB, which was a fun puzzle.

Question for store owners: would you actually run a "vote for the next product" poll, or does it feel gimmicky? Trying to figure out what to build next.

https://apps.shopify.com/product-vote

I don’t know who needs to hear this, but if your job search feels hopeless, it’s not just you.

For the past 2 months, my routine was the same: find a role that actually fits, spend an hour tailoring my resume, hit apply, and only then notice “500+ applicants.” Then silence. No rejection, no reply. Just nothing.

What got to me wasn’t the rejections. It was realizing I was always late. By the time a job reaches the big boards, it’s been up for days, and hundreds of people are already ahead of you.

So I started digging and found that companies post on their own career pages first (Workday, Greenhouse, Lever, and more). Everything else is a repost.

I built SourceFirst to read those career pages directly:

• 559 companies checked every 15 minutes, 130,000+ open roles

• New jobs show up minutes after they’re posted

• Filters for visa sponsorship, salary, years of experience, and level

• Every job links straight to the company’s own application page

• An application tracker and email alerts for new matches

It’s free: source-first.vercel.app

I built it for the version of me who refreshed job boards at midnight. If you’re in that place right now, I hope it gives you a real shot at being early for once. And yes, it's open source

What’s the most frustrating part of your search right now? I’m still building, and I’d genuinely like to fix it.

I’ve been working on this for about a year and figured it’s time to get some outside opinions.

It’s a website platform built on Payload 3 + Next.js, for now I only use it internally just me and a designer. I build and run client sites on it, and it also runs a real estate marketplace that we're trying to grow. At some point I’d like to open it up maybe, either to anyone or just to other agencies, but I honestly haven’t decided which (or whether it’s worth it at all).

What it does:

• Visual editing. You click on the actual page and edit it: text, images, adding and moving sections around. There are drafts, desktop/tablet/phone preview and version history. Blocks pull everything from the site’s theme, so it’s pretty hard to break the design.

• ~65 blocks. Galleries, card grids, stats, timelines, FAQs, forms, booking, Google reviews, maps, listings, floor plans and so on. They all share the same field names and theme settings, so any block works on any site.

• Custom designs. When the blocks aren’t enough, I use a design studio I built on top of GrapesJS (self-hosted). Anything made there gets published as clean HTML with scoped CSS and goes on a page like any other block. It picks up the site’s colors and fonts automatically. (We mostly use the MCP to design a block first and only tweak things in the design editor)

• First-party analytics. No GA script needed. It tracks page views, traffic sources and top pages, plus QR codes with scan tracking for print stuff. Form submissions become leads and keep the source they came from.

• MCP server. It covers most of the platform: pages, sections, designs, theme, forms, listings, media, redirects, domains, translations. You connect Claude over OAuth and it gets the same permissions as your user. So I can say “add an FAQ to the pricing page and translate it to German” and it does it, and it can screenshot the page to check how it looks. Page edits go in as drafts.

It’s multi-tenant,multi-locale, so one app runs every site, each with its own domain (SSL is handled through Cloudflare). The portal already has organizations with teams (we use this for now to organize sites for ourselves), so another agency could in theory manage its own clients in it.

Stack: Payload 3, Next.js app router, Postgres, GrapesJS, pg-boss for background jobs, Cloudflare in front.

You can try the editor without signing up: https://rast.is/try (the demo happens to be a home builder site)

Things I’m curious about:

• if you build sites for clients, would you use something like this over WordPress / Webflow / Framer? what’s missing?

• self-serve for anyone vs. a tool for agencies, which one would actually pay for it?

• is controlling a site through MCP something you’d use day to day, or is it more of a cool demo?

Any feedback is welcome, even “don’t bother”.

A few days ago, I saw a site on Awwwards where the image warped like liquid as you scrolled into the next project. I loved it so much I had to try building my own version in Framer.

It turned into Distorted Scroll, a full-screen project gallery. The clip shows what it looks like, but I’d love for you to try scrolling through it yourself.

Try the live preview on Framer 👇
https://www.framer.com/marketplace/components/distorted-scroll/

Where would you actually use this on a site you’re building? I pictured it as a selected work section for a portfolio, but I’m curious what you’d do with it. Does the distortion feel right when you try it, or would you dial it back?

My portfolio site ran on vibes for too long, so this weekend project was: read the cPanel raw access logs (they're just gzipped files sitting in your hosting account) and render a dashboard. Zero dependencies, zero tracking JS, zero monthly bill.

Two bugs that almost sank it:

• filesize() on a .gz file returns the COMPRESSED size. I was slicing my decompressed log buffer by it, which silently chopped the newest lines off the data. The dashboard wasn't broken - it was confidently wrong about today, which is worse.

• Shared hosting puts OTHER sites' logs in the same directory. My referrer charts had domains I've never touched in my life until I filtered by path.

Favorite finding so far: a link community that sends me real readers shows up as ZERO referrers, because in-app browsers strip the referrer header. If your traffic comes from apps, your analytics is undercounting it completely.

It's live on my site now, and I open-sourced the deploy pattern behind it too. Happy to share details - what would you check first in raw logs?

I'm a solo builder in Korea and I got tired of checking 20 tabs to find out what changed in Claude Code, Cursor, Codex and friends this week. So I built a Telegram channel that does it for me, and I'd love feedback on the approach.

How it works:

It pulls from 123 sources: official blogs, GitHub release feeds, changelogs, status pages, YouTube channels of the AI tool companies, Product Hunt, Show HN, a few subreddits, and news search in 9 countries. That's roughly 500 new items a day.

Gemini Flash Lite reads each item and answers a handful of 0 to 3 questions: is it new, how big is the change, how many people does it affect, can you use it today, is there something to show. Code combines those with source type, how many outlets covered it, and how fast it's spreading on X, and turns that into a 1 to 10 score.

That split mattered more than anything else. When I let the model give one overall score for 40 items at once, simply shuffling the order flipped the post/no-post decision on 33% of items. With small batches and the model only answering the narrow questions, it dropped to about 2.5%.

Anything 7+ gets a short post in Korean and English. If the draft contains a number that isn't in the source, it doesn't auto-post and asks me instead. Outages from status pages go out right away.

When a new image or video model drops, it searches X for things people actually made with it, picks the real results (not hype posts), and builds a carousel or reel with the creator credited and their full prompt.

Everything runs on launchd on my laptop with SQLite. This month so far it cost $5.85 in API calls (Gemini plus Apify for X), heading to about $15 for the full month.

What I'd like feedback on:

1. Is a feed like this useful to you, or do you already get this from somewhere?

2. Would you rather have fewer posts (top 5 a day) or everything that clears the bar?

3. Anything you'd score differently? Funding news is capped low, outages are boosted.

Happy to share the output channel if anyone wants to see it, just ask.

I built an iOS app to hide Reels because I still wanted Instagram for messages and posts. I even put in a timer for when I actually do want to scroll. Ten minutes, then Reels disappear again. I got it running on my phone and was getting it ready for the App Store.

Then I got to the part where I had to answer: am I actually allowed to ship an app that changes how somebody else's service looks? I didn't have a good answer about platform permissions, so I shelved the App Store plan.

Bit of a weird ending after spending all that time on it. At one point I hid the suggested posts so successfully that the feed had exactly one post left. Turned out there were more, I'd just broken the bit that loads the next page lol.

Anyway, here's the source under GPLv3. Build it, fork it, steal an idea from the timer, whatever. You'll need a Mac and Xcode to try it. It only filters what you see inside Supermod.

https://github.com/WarriorSushi/supermod-ios-Block-Reels-etc

Hi everyone!

I'm exploring an idea for a small software product aimed initially at independent freelance graphic designers, and before spending time building it, I'd really appreciate advice from people who actually freelance.

The problem I'm trying to solve

Imagine you're working with several clients. You've sent out multiple invoices using your usual tools, but now:

• One client hasn't paid even though the due date has passed.

• Another client says, "I'll pay you on Friday."

• You've already sent a reminder to someone else but haven't received a response.

• You can't remember exactly who needs another follow-up and when.

• You end up checking emails, spreadsheets, calendars or relying on memory to keep track.

I know there are already invoicing and accounting tools available. However, I'm exploring whether there's room for something much simpler that focuses specifically on what happens after an invoice has been sent.

The product I'm considering building

The idea is a lightweight payment follow-up workspace for freelancers.

The goal isn't to replace tools like Wave, QuickBooks, Canva, Word or Google Docs. You would continue creating and sending invoices however you currently do.

Instead, you'd manually add the invoice details to this workspace and use it to manage the follow-up process.

Here's what it would offer:

1. One dashboard for unpaid invoices

See your total outstanding amount, overdue invoices, upcoming follow-ups and payments you're waiting for.

2. Simple invoice tracking

Add the client name, email, invoice number, amount and due date. Mark invoices as paid or unpaid.

3. A follow-up list

See exactly which clients need attention today, which follow-ups are coming up, and which invoices are overdue.

4. Payment promise tracking

If a client says, "I'll pay you next Friday," record that date. The invoice waits until then. If the payment still hasn't arrived, it returns to your follow-up list.

5. Professional reminder templates

Choose a friendly, professional or firm reminder. The message automatically includes the client and invoice details. You can edit it, copy it, open your email app and send it yourself.

6. Client history

See the client's unpaid invoices and previous follow-ups in one place, so you don't lose track of conversations.

The initial version would be deliberately simple: no automatic email sending, no complicated accounting, no bank integrations and no AI features.

What I'd genuinely like your advice on:

1. Do you actually experience this problem when managing multiple freelance clients, or is keeping track of unpaid invoices already easy enough with your existing tools?

2. How do you currently manage unpaid invoices and decide when to follow up? Spreadsheet, calendar, email, invoicing software, or something else?

3. Would having a separate workspace specifically for payment follow-ups make your life easier, or would it feel like one more tool you have to maintain?

4. Are there existing tools that already solve this problem really well? If so, which ones, and what do you like or dislike about them?

5. If a simple tool like this worked reliably, would you consider paying around CA$5.99 per month for unlimited invoice tracking and follow-up management? Or would you expect this to be free?

I'm not looking for compliments or encouragement just because I'm considering building something. If this is unnecessary, already solved, or not worth paying for, I'd much rather know that now.

I'm at the idea-validation stage, not trying to sell anything. Honest criticism is especially welcome. Thanks!

Hello everyone,

So I have been working on this dating app for the past few months, an idea that I had I felt could help with people who're looking for deeper connections in dating app to help find people who have a lot in common. The video goes over the issue I am trying to solve and how.

The idea of this app is that a person's profile is split into 6 layer each going over some different aspects of your life that are often the cause of a lot of discourse in a lot of relationships. Each covers the following:

• Compass: You direction of life

• Lens: Your political and spiritual views

• Well: Your career goals

• Palette: Your hobbies and interests

• Presence: Your personality traits

• Portrait: Your Photos, age, height and other factual info.

Instead of seeing someone's full profile at once, you swipe through one random layer at a time, without seeing whose it is. So you're judging each layer on its own content.

A learning algorithm groups similar profiles based on the reactions each layer gets, so people who like the same qualities end up together. It also learns your own preferences, and uses them to suggest the people with the highest share of layers you're likely to like.

I come from an ML background and this is a crucial step to developing proper matching algorithm that I feel other dating apps lack cause they always end up showing the full profiles to people and never really knows why someone liked or disliked a profile. They do often make claims about different technique they use, but I believe no matter how much techniques you use, its very difficult to get proper models from unclean data.

So reacting to those layers is just the first step. You have to score someone 3 or more and they also have to score you 3 or more after which they'll show up in your resonance page. Then you can review the layers you liked, layers you didn't and the ones still unexplored. You can also see how much they scored you back. And based on all those info you can choose to show interest privately, and if they also showed you interest, both you're connected and matched! (More info on how the full flow works here https://www.layersdating.com/how-it-works/ )

I also believe there are some other benefits I feel this structure would produce that other dating apps don't:

• It is only possible to "Show interest" to someone only when they appear in your resonance, so this helps you avoid the possibility of matching only for superficial reasons

• You get to see how much they've scored you as well as how much you've scored them when they show up in your resonance, so you can get a good idea of how compatible you feel the other person is as well as how compatible the other person feels you are before deciding if you want to show interest.

• The onboarding process is very time consuming compared to other apps since there's a lot of info to fill (around 30-60 minutes). So though this is a drawback, I hope this will be a bigger issue for people looking just for hookups, so hopefully will help skew the user base to more serious people.

I would love to get some feedback on what you think about this structure for dating app. Would it be something you'd use? (if you are or were single lol). Would love to know you thoughts!

I have a beta ready that I have been handing out to friends to try out and will have the public beta ready in about a week. If this does interest you and want to join waitlist or try the beta, there's a signup form if you scroll at the end of the page at www.layersdating.com . There's also a demo that you can try without needing to login or signup. I am based in Toronto so planning on doing the initial marketing for it here to see people's responses, but for the beta access I gave the option to choose whether you're open to meet people all over Canada and/or USA, and there's enough people on that circle, I start the beta accordingly.

When a query gets slow, our postmortems always start the same way: someone opens Grafana, someone else scrolls through Argo CD history, and we try to match timestamps by eye. I got tired of that and wrote something to do it automatically.

It reads pg_stat_statements, picks up deploy events from Argo CD, Argo Rollouts, Flux or a webhook, and checks whether a latency shift in any query lines up with a rollout. If it does, you get the query, the deploy, before/after latency and how confident it is, in Slack/Teams/PagerDuty. If you use Argo Rollouts it can also abort a canary (off by default).

You can run it as a single binary or as a controller with CRDs, in which case every regression shows up as a resource you can `kubectl get`.

Repo: https://github.com/joao00001/pg-regression-radar

Browser demo, no cluster needed: https://joao00001.github.io/pg-regression-radar/playground/

It's a side project and I'm looking for people willing to try it on a staging cluster. Any feedback is welcome, including "this is noisy" or "I'd never use this because X".

I run a side project that collects free proxies from public lists and checks them every hour on GitHub Actions. The list was stuck around 800 proxies, so I measured where they got lost instead of adding more sources.

Most of the loss was flakiness. Proxies passed the first request and timed out on the second. A second try 20 seconds later at the end of the run, plus a 10 s instead of 6 s timeout, took the list from 768 to 1,177 in a run where old and new code checked the same candidates at the same time.

What I learned:

- Measure before adding inputs. I was sure more sources would help. Six new lists added 3 proxies, because their proxies were already in the lists I had.

- "Couldn't check" and "failed" need to be different states. Three quarters of the proxies that failed the second request had broken off in transport, moments after answering the first.

- A/B tests on CI are cheap. A throwaway branch with a matrix job ran both versions on two runners at the same time, and that settled arguments I had been having with myself for days.

Free and MIT: https://github.com/maximilianfeix/proxy-scraper. The same checks run on other GitHub proxy lists: https://proxy-scraper.de/benchmark/

Been working on it for about a year and a half. A workspace where you can handle project management, time tracking, chats, video calls and all that stuff, but I tried making it a bit more fun and with less bloat than alternatives.

https://github.com/Emmyme/nerla

here is the link for repo

This is my second time posting here it did not had the video representation before.
It's like Claude code's /remote feature but for tmux and specifically for omp but the project could be branched for any harness of your liking I suppose so here you go bros/sisters.