So I'm very much in favor of the recent ban on AI from this sub, after having first hand seen the outcome of an all-in strategy on a codebase for nearly a year. I wrote an essay about it, and I think some folks in this sub may find it resonates.

I've been seeing some articles come about that people have removed and replaced many TV's Operating systems, primarily to remove ads.

I would like to do this to remove issues I am having with a 2024 (2025?) Samsung Tizen Smart TV. It's obviously a software error (Or a failing entirely TV) as I have tested it with multiple devices, (Computers) and all of them produce the same issue.

TV randomly turns off, sometimes entirely, sometimes certain functions. At first it would be sound, and the sound just stopped playing for some odd reason, while video continued. Then just now, it was picture only. I thought the sound was coming from another device, turns out it was still playing the most recent video's sound through the TV, just no picture.

Sometimes it just won't respond to the remote too, I have to hard reset it and am disabled with active fractures in my back. It's not easy reaching down to unplug it and plug it back in.

Either way, I come here as I don't trust everything I see on the internet. I'd like to see what other input others have for replacing the software on your TV. I have hard reset this one, and don't even agree to their terms. The issues are completely random seeming, and have no real rhyme or reason. It also returns to full functionality after a reset, for sometimes days, sometimes hours.

Hi guys,

I figured it was time to actually announce the existence of my project.
It's been well over 10 years since the last commit, so you can be sure that not a single LLM token was used in development of this code.

What does it do?

It's a full LANparty management suite, from seating plan, food ordering and notifications to seeding, hosting tournaments, making teams, voting maps.

The code is barely functional, it's full of bugs, it's outdated and not up to the most recent conventions at all, so I thought it feels perfect in the current state of this subreddit.

I want to recreate the database since the old schema was never committed, but since speaking about automated ways of doing this is not allowed on this subreddit, I will take that question elsewhere.

Let me know what you guys think!

https://github.com/sander110419/LANCMS

like

what if i use it for documentation only because my communication is horrible

and yes this is literally my first post here lmao

sorry if anyone else asked about this in a post i couldnt find one so i had to ask because thats kind of what i do and i would like to post some projects i make here

(not the best time of the year to suddenly appear in a sub about projects huh)

AI usage is everywhere in dev, and it's not going away. But AI makes trusting open source... complicated... (arguably in a good way though).

A big part of open source projects (particularly solo projects) was that they were typically someone's passion project. They cared about what they made, and that extended to the code too. with attention to detail to make it easily maintainable (i.e. legible to other humans), performant, and free of anything malicious. A big part of the trust associated with open source is trust in the maintainers. But when those maintainers aren't actually writing the code themselves, that trust is shaken.

I have no specific objection to open source maintainers using AI though, as long as they know what they're doing. AI is a tool after all. But it's a tool that should be used responsibly, and with appropriate oversight. In the same way as I wouldn't trust a random 12-year-old to responsibly use a chainsaw, my trust in open source projects disappears when I see that it's been written by a non-dev relying entirely on AI.

I've been a dev for over a decade (always in commercial settings, so my contribution to open source has always been financial, rather than through contributing code). I'm fortunate that my team's attitude is that even if AI wrote the code, it's still that person's code, so they better be damn sure that it's written well, and performs well. Code quality is extremely important to us, and we know that even with the most detailed prompts and surrounding context (instructions, skills, etc.), that AI sometimes spits out absolute crap. So if AI writes our code, then the time we would have spent writing it is expected to be spent on planning, reviewing, and confirming its output.

The situation is muddied by more and more people using AI to churn out code without really understanding what that code is doing. Those sorts of projects can be genuinely dangerous too. Especially in a world of automatic updates, I'm not going to trust an app from a maintainer that won't understand when an LLM has just put ads and trackers (or more malicious things, like external executables) into their project. I'm still perfectly happy to use and support projects that were made with AI help, but I have less (or usually no) trust in them by default, and need to spend the time to review what I can of the code myself first.

I guess what I'm trying to say is: for all the AI slop out there, there are also a lot of devs out there who know what they're doing. Devs who still care about what they work on, and who may be (and probably are) using AI tools to help them do it, whether that's personal choice, or their company expecting/requiring them to. AI has really highlighted the importance of human critical thinking, which is a good thing. Please don't immediately disregard a project because AI was used. Instead, approach it critically, and sceptically, as you always should have been doing. Continue to call out the slop, but also praise what's been well-reviewed and made with care and attention (regardless of the tooling that was used in its creation).

Disclosure: with the recent rules being changed, I debated whether to share this here. Swytch has been in R&D since 2019 and commercial for years, but only recently open-sourced earlier this year when my cofounder and I incorporated to land a large client. We're still open-sourcing parts of the commercial engine. We use AI where we can, but AI fails to work on Swytch properly as it falls back on 40 years of distributed systems that Swytch basically rejects. 2P commits aren't a thing. Leaders aren't a thing. Clock sync isn't a thing. Transaction aborts ... you guessed it, not a thing. So, mods, feel free to kill this post if you want.

Today, I'm happy to announce Swytch 1.6!

For anyone unfamiliar with Swytch, it's an open-source, Redis-compatible, leaderless distributed database. You can run it on one machine or across multiple regions in active-active mode, with serializable transactions and no CRDT shenanigans.

So, what's new?

First: interactive transactions.

You know how Redis returns QUEUED for commands inside MULTI?

With --ssi enabled, Swytch returns the actual results immediately, using a consistent MVCC snapshot.

You can read a value, make a decision in Go, Python, PHP, or whatever you're using, and issue additional commands before calling EXEC to commit.

No need to move your application logic into Lua just to perform a transactional read-modify-write. Lua is still supported if you prefer it.

Second: disk durability.

One of our most requested features since launching six months ago.

With --data-dir, Swytch can restore its local state after restarting, even if the network is unavailable.

This is particularly useful for edge deployments and offline-first applications.

A note: local disk durability isn't a backup. Swytch retains a mirror of resident effects, so we recommend Swytch Cloud for full-history backups and point-in-time recovery.

Third: choose how to handle network partitions. Per key.

Swytch defaults to safe mode, prioritizing consistency for transactions when peers become unavailable.

With 1.6, you can configure unsafe mode globally or for individual keys and key patterns.

Unsafe mode allows transactions to continue in disconnected parts of the cluster, with deterministic reconciliation when connectivity returns.

For some applications, losing availability is far more expensive than reconciling inconsistent data afterward.

Imagine a multiplayer game across several regions. Players should be able to keep exploring, collecting rewards, and playing even if regions become disconnected. But operations requiring stricter consistency, like trading a unique item, can wait for connectivity to return.

Swytch lets you make that decision per key instead of taking the entire game offline.

And when competing transaction histories are discovered after reconnecting, Swytch exposes conflict reports containing transaction evidence so your application can decide whether compensation is needed.

Finally: bug fixes.

So many bugs. As you'd expect.

We've been testing some particularly awful network topologies, and quite a few subtle consistency issues turned out to be one-line fixes.

The source is available here:

https://github.com/swytchdb/swytch

I'd love to hear what you think, especially if you're building something with Redis today.

When it's built by a team or a dev who understands the technology they're working with. When they're solving a problem that exist that does not have a solution.

The issue with all the garbage people are producing right now, is that, it doesn't solve a problem. It's reinventing the wheel with flashy stickers, with assumptions and then calling it good.

I have nothing against AI, I have something against pure AI code, because AI 100% makes mistakes, how can you tell its AI code? There's repeated codes everywhere, codes that could have been unified in a simple function, function and naming are a meter long, massive blocks of code that no one can review and no one wants to review, but that's okay the hacker's bots will review that for you.

If you're going to make something with AI, atleast review the code, rewrite it, optimise it, improve it, outline a problem your app solves, not because "I think it looks good" half these projects are what up for a week, maybe 3 4 hours and then already in maintenance mode. Also no one wants to use it, because it's too dangerous to use so why are you wasting time building garbage.

Building something others have built, okay there's more to this, if you're going to go reverse engineering, go see how many people your slop is going to affect, how many jobs and how many families those people's job support.

They're going to have to get a new job, maybe take your job, if you're a dev generating slop at scale, and decided, why code, just vibecode it. You're replaceable, now your boss can just drop you and send the prompt to AI themselves. If you're looking for work in IT, these are the guys killing the job market for you. Why do companies need you when everyone is building stuff for free, when you have no experience, you won't be getting any either, because no one wants to see what you vibecodes, they want to see if you can do the work without AI if sh.t hits the fan.

Remember AI isn't going to cost 20 bucks forever, it needs to be several grand to be a realistic cost proportionate to the hardware it uses.

Anyways keep killing the job market, less clients, less work, less jobs, less income.

This subreddit's description currently states:

A subreddit for everything open source related (for this context, we go off the definition of open source here http://en.wikipedia.org/wiki/Open_source)

I'm hoping this inquiry/discussion is in-line with that, even given the recent planned updates in the currently pinned post and the barrage of backlash currently happening, which may be affecting the judgments for post removals.

I'm around 5 YOE professionally in the SWE space, but have only meaningfully contributed to a handful of open-source projects (some with hundreds of active end-users) over the years, so I'm genuinely unfamiliar on what people more involved in the open-source community space (here in this subreddit and also more broadly) actually value in something being "open source" and the general culture/spirit behind the community.

To me, as a bit of a newbie, "open source" simply brings to mind sharing, transparency, collaboration, and freedom of use/modification. I was admittedly unfamiliar with formal OSI licenses until reading through the mod post, but I thought the "absolute non-discrimination" aspect of it was an interesting pillar establishing freedom of use and creative expression without gaurd-rails against the "good" or "bad" derivative works that branch off from it.

So my impression then is that this subreddit is meant to be a broad umbrella entry-point "for everything open source related," but some of the points outlined in the recent modpost after a few passes seems to be at odds with that. I do fully understand moderating out the 10,000x "I used AI to build a todo app" and wanting to curate high-effort discussions, but the upcoming restrictions seem incredibly gate-keepy to establishing what is classified as "the right type of open source project/contributors". Also with regards to this comment, pointing out some aspects seem to be poking at orthogonal directions to something being in the bucket of "everything open source related"

So, with all of this in mind, I was just genuinely curious to hear from others more involved in the open source space (in and out of this subreddit) if my read on the culture/spirit of open source is correct or if I'm muddling some of the points of it. Thanks in advance ^^

(and thanks for reading through my wall of text)

If your Razer mouse isn't supported by the new Synapse cloud and/or you'd rather not run heavier software than you need, there are other options:

• OpenRazer + Polychromatic: full Razer support on Linux
• libratbag + Piper: Razer and Logitech mice on Linux
• OpenRGB: lighting on Windows, Linux and Mac
• secbird: mice, keyboards and more on Windows, with profiles, per-game switching and button remapping (more than I need, but great if you want those)
• SignalRGB: lighting synced to games, on Windows
• X-Mouse Button Control: per-app button profiles on Windows
• AutoHotkey: macros and remaps on Windows
• razer-macos: lighting and DPI on Mac
• usemice: runs in the browser, nothing to install
• dawctl and open-razerkit: command line tools

Believe it or not for my basic use case of gaming on a shitty computer I still couldn't find a solution. So Snakecharmer was born. It's based on OpenRazer's protocol work and sets:

• DPI
• Polling rate, up to 8000 Hz on mice that support it
• Button binds, including the DeathAdder Elite's two DPI buttons, which Windows doesn't receive on its own. On the V3, binds can be stored on the mouse, so they work when the app isn't running, in games that block injected input, and on other PCs.
• Lighting, per zone: static, breathing, spectrum, or off

It's a single exe with a tray icon and a settings window. There's no installer, no account and no telemetry. It's GPL-licensed, same as OpenRazer.

Safety: it only sends commands documented in OpenRazer, never touches firmware, never rebinds left or right click, and only opens mice on its supported list. Other devices are ignored.

Supported mice:

• DeathAdder Elite
• DeathAdder V3 (wired)
• DeathAdder V4 Pro, wired and wireless (first contributor <3)

Adding more mice: I am so so so grateful for any and all contributions!!! OpenRazer documents the protocol for 100+ other Razer mice, including the Viper, Basilisk, Naga, Cobra, Mamba, Lancehead, Orochi, Abyssus, Pro Click and older DeathAdders. Adding one mostly needs someone who owns it to test on real hardware. It's as easy as pointing your robot of choice at the repo and going for a walk. There's a wishlist, a guide, and a prompt for AI coding assistants if you want to use one. If you own a mouse but don't want to write code, you can open a request and someone else can write it.

I already set up immich (I love it, Now i dont have to pay for google storage)

I am looking for something just as good as immich but for Music. I currently have spotify premium, but I wanna not pay for it if i can... But having a polished UX is absolutely non negotiable for me.

Do not recommend plex or similar stuff, we (our whole family) is not a fan of re-watching shows, So it's better for us to pay for OTTs.

(I looked at the current beef, please don't bring that into this post, let us keep this as a typical "Helping a newbie out" kindof thingy...)

I contribute to Omi, an open-source AI wearable. I write my PRs with AI help and say so in each one.

Twice now, an agent run by the team opened the same fix as one of my open PRs. Theirs got merged. Mine was closed or left open, with no credit either time.

The first time, I opened #19658 on Sep 28 and it was reviewed on Sep 29. On Oct 3, a team AI account (Git-on-my-level) merged #20431, a bigger PR that includes the same fix and test. Mine was closed as a duplicate.

The second time, on Oct 21, I filed an issue and opened the fix, #22998, at 08:01 UTC. At 08:53, an "hourly watchdog" bot running on the founder's account opened #23010 with the same fix. It was merged at 11:18. Fourteen minutes later, the team's own review agent rated my PR "correct and well scoped".

I also have 10 PRs open since Sep 28 that their review bot tagged "positive-signal". CI has never been approved for any of them, because I'm a first-time contributor.

I opened a public issue about this, #23430, with two suggestions: agents should search open PRs before writing a fix, and add a Co-authored-by line when they overlap. The triage bot moved it to "Someday". I tagged the founder directly, and I couldn't reach a maintainer on Discord. No human has replied.

The team does merge a lot of community work, around 1,269 PRs in two weeks, and duplicates happen in any busy repo. What bothers me is that the agents never check open PRs, and nobody gets credit when they overlap.

Has anyone else run into this on repos where agents write a lot of the code? What would be a reasonable thing to ask for here?

Amazon Link

Just seems like the old texts have been forgotten. Highly recommended for mods and members alike.

‎ On GitHub, the creator of NotProton asked the maintainer of Bridgeplay, a fork of NotProton, to stop distributing it because they believed it weakens the funding behind Wine on macOS. The owner refused to take the repository down. He kept it public, added a "Support Wine / Buy CrossOver" line to the README and website, and closed the issue as completed. The discussion is in Bridgeplay Issue #79: "This should not exist."

Running Windows games on macOS, especially on Apple Silicon, depends almost entirely on Wine. The main company funding full-time Wine work for macOS is CodeWeavers, which pays for it through sales of CrossOver and contract work such as Valve's Proton. When the Whisky project was discontinued, its maintainer said they did not want to take more than they gave or weaken CodeWeavers' ability to keep Wine going. NotProton, which connects native Steam to Windows runtimes, was built to require CrossOver for the same reason.

Raymond Chin, an Indonesian tech influencer and entrepreneur, forked NotProton as Bridgeplay and replaced the CrossOver requirement with a free Wine engine built from source. He promoted it on social media:

Windows games on Mac? Done ✅ I open-sourced the most seamless free way to play Windows games on your Mac Steam. bridgeplay.dev, go star/contribute

NotProton's creator opened Issue #79 with three objections:

• A free alternative that skips CrossOver could cut the license sales that fund Wine on macOS.
• The fork merged unreviewed work-in-progress PRs from NotProton that its maintainers did not fully understand.
• The fork was an opportunistic "slop fork" built for personal branding rather than technical contribution. The maintainer wrote:

Stop. These slop forks are not helpful. They harm the Wine Project.

The owner admitted he had pulled unmerged WIP PRs and acknowledged that the project depends on NotProton and CodeWeavers. He did not agree to stop:

Where I see it differently: Bridgeplay will stay free and non-commercial... I understand if you still disagree with that.

He said the slop-fork argument would never be settled and that he would keep working on the project as an open-source side project.

Commenters said the CrossOver line looked like a gesture while the request to stop was ignored, and that closing the issue ended the criticism. daudonhere wrote:

Stick to what you understand before lecturing others about open source. Your handling of this situation has exposed a serious misunderstanding of the ecosystem you're operating in.

The main objections were that the fork kept being distributed after its upstream author said it harms the software it runs on, that sustainability was handled as a marketing item while the free engine stayed available, and that closing the issue ended the criticism while the fork kept benefiting from upstream work and the owner's personal brand.

The case leaves some questions open. Does an upstream maintainer's request to stop distributing a fork carry weight, and if so, when should a fork comply even though the license permits it? Does a "Buy CrossOver" line actually address the sustainability concern, or is it only a partial step? And what do forks of niche developer tools owe the projects they build on, especially when they are promoted mainly as personal brands rather than as technical work?

Issue: https://github.com/raymondchins/Bridgeplay/issues/79

This was deleted from r/learnprogramming, so I'm reposting here.

I've been thinking about how cool it would be if we could categorize internet domains in the same way the Dewey Decimal System categorizes books. Such a system would allow independent search engines and directories to compete with Google again.

We live in a time where you can spin up as many VPSs as you need. Where data can be distributed in all sorts of ways, among those machines. And on the cusp of the fastest processing power in history (quantum).

I'm honestly looking for a discussion on extending this:

https://github.com/ki4jgt/Open-Catalog-System/blob/main/OCS.json

It's a taxonomy for classifying and grouping domains of similar topics and interests (Facebook, Google, programming, YouTube, etc). As I cannot possibly think of all the subjects contained on the web, I would love some open discussion, here on Reddit -- if that's OK, on how you guys think this should be structured, what subjects you think are missing, and your general feedback on what would make it better.

For those of you who don't know, taxonomies are how we used to find information before Google. To find an atlas at your local library, you'd go to the Information desk, then the reference area (things you can look at in the library but can't check out), then the particular reference type you were looking for.

So, INF.REF.DIC would give you a bunch of dictionaries. Since you're looking for information (a definition), and need a reference, I thought it only fitting to keep the convention. In web terms, Webster, Cambridge, and Urban Dictionary would be listed here.

RFCs are listed under INF.COM.RFC because RFCs extend beyond programming, and are used in a wide range of communication and data formats.

Feel free to share any suggestions you have in the comments below. Thanks. I am desperately seeking to expand this. The goal here is inductive, not deductive. We want to group domains together, with useful categories, instead of splitting them apart.

I have always had this thought that if your software or business makes money while leveraging open source, I think it's a great culture to dedicate a portion of your earnings to supporting the maintainers behind those projects.

Think about it. Many businesses rely on open-source libraries, frameworks, and tools to build products, save time, and reduce development costs. Some even build entire businesses around them.

Yet, the people maintaining these projects are often doing so with limited funding, in their spare time, or alongside other jobs. Meanwhile, businesses can generate real revenue from the work these maintainers make available to everyone.

I believe that when your business starts making money from these tools, giving something back should be part of the culture. It doesn't have to be a huge amount. It could be a percentage of your revenue, regular donations, sponsoring a maintainer, or even paying for work that helps keep a project healthy.

Of course, open source doesn't mean you owe every project money, and not every business can afford to contribute financially. Contributions can also come through code, documentation, bug reports, and helping other users.

But if a business can afford to give back, why shouldn't it?

We all want open-source projects to remain available, secure, and actively maintained. Supporting the people behind them is one way to help make that happen.

I believe we are all aware of all the recent vulnerabilities reported lately across various domains and this should be a signal.

So, if your business makes money using open source, don't you think giving back should be part of your responsibilities, or should it remain entirely optional?

EDIT: Oops, I thought I was posting this on r/fossdroid. Apologies, I was doing it from a mobile browser.

Are there any FOSS launchers that have highly customizable homescreens like Nova (e.g. freely resizing/overlapping widgets), and also support displaying Private Space apps?

If you suggest one, please say why! Does it do something better/differently than the other options?

I'm looking for a script that uses arp poisoning to impersonate the network DNS server and blocks all requests to ad servers.

Connect the device to any network and you've automatically got ad blockers for all devices without configuring anything.

Hacking for good.

The champions of the new KDE Goals for the 2026-2028 cycle will be answering your questions live!

KDE for Enterprise and Deployments: Ask David Edmundson, Kevin Ottens, Neal Gompa, and Kai Uwe Broulik about how they plan to make KDE a viable choice for businesses and public institutions.

Better documentation: Check in with Nate Graham, Thiago Masato Costa Sueto, and Joseph P. De Veaugh-Geiss about improving KDE's documentation.

Next Generation Styling for KDE: Find out how Arjen Hiemstra, Akseli Lahtinen, and Andy Betts are working to implement a unified styling system.

Leave your questions in the comments or in the KDE Forum post!

The champions will answer them live on on Youtube and Peertube on October 29 at at 17:00 UTC.

Hi,

A senior dev left left my team and with them left a lot of the code standards. Previously code review was painful and took hours and sometimes it would require a rewrite. However, that was the best code I have probably ever written. I genuinely enjoyed learning coding principles from someone who had been doing it for 20+ years and had reasons behind their principles. Its hard to find discipline these days.

Are there any projects that come to mind that have strict longstanding maintainers? My preferred languages are Python and Go but I'd be willing to learn something new.