After over a month of hosting this 3+ months old project on GitHub, this project seems to be finally gaining some user base

This is a prerelease version which i have tagged to be stable and slated for future release and add to main branch from the beta branch.

This highlight is less about asking you guys to try out the beta release but more in the honor of over 3+ months of development.
What makes me happy the most is that the project which i started even without a repository just to monitor my own system and usage has now come this far with over 50+ downloads 🎉☺️

This beta release now polishes on various little things which are actually necessary for a first time set up and proper user control as Now you can:

• carries forward the settings screen from previous beta release
• replaces notifications and sounds tab with general which now includes appearance settings
• you can now Stop , restart or RESET the Daemon and its preferences in settings
• Pomodoro settings which were half baked in the first release have now been added to settings to enable a looping focus mode for people at work with CUSTOM BREAK TIME
• Most Importantly (i feel) FIRST time setup issues have been fixed and in an attempt the first time ScreenGuard daemon setup pop up dialog (1st image) has been made

The Release v0.1.1 releases this October by second week, and I will continue testing the beta version to look for sectors that need polishing if any.

This is still limited to GNOME on wayland and x11 for other environments systems and primarily developed by me on my fedora 44 system and the project ScreenGuard still has a very Long way to go;

But working on it alone has given me much exposure to project sharing on platforms and most importantly a lot of invaluable experience and the true zeal of development instead of the boredom of being a 9 to 5 dev at a corporate who don't care for you.

Github beta release link: https://github.com/adityakrishnan005-a11y/ScreenGuard/releases/tag/v0.1.1-beta.4

The code for this is visible on the beta branch to keep the main working tree clean for new features additions.

Feedback from other desktop environments is widely appreciated, u can try the application out by switching to x11 session temporarily if you are using any DE which is not GNOME wayland or if u are on a DE which is primarily x11 based (Cinnamon, i3, etc) then u are good to go as they ARE FULLY SUPPORTED.

thank you everyone for your supports, criticisms and feedbacks ever since the project came online on github.

Hi all,

There are a number of apps on the Android App Store that enable you to lower the minimum backlight brightness (or claim to), but I'm looking for de-Googled FOSS options.

Any suggestions? Thanks

Nice timing for a project named after Mocha. ✊

BSD licensed 🙄

The man leading GhostBSD, Eric Turgeon, has come up with Mocka, a new desktop for this BSD distribution that would eventually replace MATE. So far, he has unveiled the dock that will go into it, as well as some preliminary concepts and specifications that show us where Mocka will head next.

Existing users of GhostBSD don't need to do anything now since nothing has changed on their machines. All of this is still under heavy development after all. 🤷

Grammar nazis won't like this

In his search for projects named "Mocha," the caffeinated drink, Eric made a typo and ended up naming his new creation "Mocka," where every component has been built from scratch, taking in nothing from the MATE project.

He plans to replace one component at a time, reverse-engineering what MATE already provides until full feature parity has been achieved. Once this is complete, I assume that GhostBSD will default to using Mocka as its default desktop environment.

And this is not his first time carrying out such a major change. In February, he came to the conclusion that MATE was not ready for Wayland and GhostBSD would switch to XLibre to keep its X11 session intact.

That line of thinking also checks out with what Eric's doing now.

The desktop's first component, a taskbar-style dock applet for the MATE panel called Mocka Dock, is already out now as an alpha for early testers. It lets you open apps, view their thumbnails, bring them forward into focus, and manage multiple windows of an app—basically doing what a dock worth its salt should do.

People who have the skills can build it from source right now to see what it offers, while the rest of us will have to wait for it to show up as an GhostBSD package update. Though it is not becoming the default experience yet, you will have to manually set it using the "Add to Panel" button on the taskbar.

If you take a look at Mocka's GitHub page, you will get a better understanding of what's being worked on apart from the dock. There's Mocka Menu, which has a proper PLAN.md file that lays out what work has already been completed and what's to be done.

The document shows us how a meson build and schema work has been done, with a long list of work yet to be carried out. This would give Mocka the ability to show a menu with listed items, the ability to handle search and keyboard inputs, integrate with the dock, and much more.

Eric has plans for a settings app too. Once complete, it would give users a single-access point for managing their GhostBSD machine's desktop appearance, network config, power management, keyboard layouts, and other UI-focused options.

There's also a separate repo that hosts the code for Mocka's official website. It is considerably behind in terms of development than the menu component we saw earlier and only contained placeholder content at the time of writing.

The project is hoping to ensure that these new Mocka components remain compatible with MATE so that users can mix-match during this transitional phase to a full Mocka desktop on GhostBSD.

I'm glad to announce v0.4.7 release!

Syncspirit is continuous peer-to-peer realtime syncrhonization tool. It implements BEP protocol and provides seamless interoperability with existing syncthing nodes and clients.

https://raw.githubusercontent.com/basiliscos/syncspirit/refs/heads/master/docs/fltk-overview.gif

You can download ready-to-use binaries for Linux x86_64 (AppImage), Windows 32 bit (WindowsXP is supported), Windows 64 bit and Mac OS X (Apple silicon).

Notable changes (since previous v0.4.5 announce):

• [core, fltk] allow to use file patterns (PCRE-syntax) accept or ignore local files into cluster
• [core] add start offline option
• [fltk, win32, os x] add system tray icon
• [fltk] use menu instead of toolbar
• [core] introduce services layer (allow stop/start/restart of networking)
• [core] dns resolver actor: randomly choose ip address of resolver server
• [core, fix] more reliably connect to relays.syncthing.net
• [core, win32, bugfix] use utf8 for displaying error messages
• [core, win32, bugfix] allow to use long file paths (260+ symbols)

Syncspirt source code uses GPLv3 license.

Any feedback is welcome!

WBR, basiliscos.

cross-posted from: https://lemmy.ml/post/53245270

Last post published was setting up Anubis (the bot protection) because I felt that documentation was lacking. This time I am publishing a "getting started" on Wayland for the same reason.

This guide is about programming a client application showing a window. It is coded in C++ but very close to C so hopefully anyone can read it and implement on their own.

If you find it nice please share the word around, this could help me a lot.

I feel their is not enough in-depth explanation of the whole protocol and there are some crazy caveats (like the most known article this is inspired from would not work on big-endian machine). This took me a lot of time to write and make a "simple" code to test (800 lines file).

I was just looking for a good Library of Things web UI for discovery and reservation and with some digging found this one from the Chicago Tool Library. Curious what other people have seen or used or if they had any experience with one before.

I didn't find a helm chart so that might become a project for me 😅 for whatever project I find. I'm just wanting something hands off, and straightforward for use with friends, my local maker space, municple library, and local college. So we can share/borrow stuff easier

cross-posted from: https://lemmy.today/post/56291625

I'm extremely happy to announce that Neighborgoods 0.1 has been released!

Neighborgoods is a platform which allows people and organizations to setup a #library of many different kinds, and federate them together to provide a large resource for borrowing, sharing, and giving.

This is our first release, which has basic setup of distributed libraries , which are groups in an area where people share goods.

About a week ago, I created a post detailing a web index I was working on.

I've implemented a few policy changes, after realizing I want this to be more like a library than a search engine.

I remember walking through library shelves as a kid, finding all the subjects I could learn about fascinating. And I'd really like to recreate that experience with this site. An infinitely scrollable catalog that transitions from subject to subject to subject, treating individual domains as books, with rankings (0-9) determined by a mixture of author authority and cultural relevance.

Current Plans:

• I'm removing the index.json requirement, and allowing users to simply submit domains for inclusion within the catalog.
• Domains are sorted via an alphanumeric XXX.XXX.XXX format (so cultural anthropology would be SCI.ANT.CUL)
• I also have plans to put the entire catalog on IPFS, for public accountability.
• I'm also no longer referring to it as an index, but a catalog.

You could even have a plethora of local results: USA.KTY.BWG, DEU.BER.MIT

Here is the current UX: https://imgur.com/a/QdXTmbz I'm looking for suggestions to make it a better experience. The name is just a placeholder.

Hello guys! I use Orbot in proxy mode but he keeps turning off. I tried use with RethinkDNS, but it happens the same thing. How can i fix this?

I wrote a blog post for the project this week detailing some of the challenges the QEMU project, in common with other FLOSS projects, are seeing with AI generated bug reports. The dilemma being that the LLM's have got to the point they generate better bug reports than a lot of humans do.

The latest versions of Common Voice datasets, Scripted Speech v27.0 and Spontaneous Speech v5.0, are available for download on the Mozilla Data Collective! A giant thank you to all of our contributors for their hard work putting together these datasets.

What’s new in this release:

Version 27.0 of Scripted Speech includes datasets for 295 languages. These datasets contain 32,349,999 voice clips, making approximately 42,593 hours of speech data available for developing and improving speech technology.
Version 5.0 of Spontaneous Speech includes datasets in 80 languages. These datasets contain 89,754 voice clips of free-form answers to questions, of which 302 hours have been transcribed and validated.

Since the last release, the Common Voice community has welcomed 1 language to Scripted Speech - Pa’O (blk) - and 6 languages to Spontaneous Speech - Chinese (China, zh-CN), Swahili (sw), Palauan (pau), Sundanese (su), Bengali (bn) and Shan (shn).

Manufacturing custom chips has become easier and cheaper during recent years. wafer.space is not the only one doing so.

They use a 180nm, which is meh. But still, it's an advancement towards making this accessible to everyone. Maybe in the coming years, we could see people easily doing so at home.

Also now, IMO, importance of open source hardware design has increased. 20 years ago, it wouldn't mean much if a CPU is open source or not. You could not produce a chip. And a discrete one is useless. Now it's different.

cross-posted from: https://lemmy.blahaj.zone/post/48313374

Promotional

Im not affiliated to Fermi/Harmony chat in any way, im just a user who liked it and want to share my experience of the app i find worthy of sharing

so i wanted to share a promising project that I have been using for a few months.

made this post to promote and share this platform since it needs more people, theres arent many atm and it deserves way more.

Fermi/Harmony Chat is free and open source discord like guild/community centered chat platform with most of the features that are expected from those platforms like message channels, vocal chats, threads, screensharing and more. Importantly the chat platform has a strict stance against LLMs AIs and AI generated slop like vibe coding and other abusive usage of AI that replaces human work and slop it in the process. sadly fermi/harmony is unique of having a strong stance against AI. (other similar projects sadly uses AI and excuses AI usage and vibe coding)

the platform also allows users to create their own client for the platform. harmony chat is the API and fermi is just the currently only working client on the platform (was a spacebar client previously until harmony was created as a spacebar fork with the goal of fixing the many issues and bugs present on spacebar) and in the future, instances are going to be federated and the process will be managed directly by the client (fermi and other clients) without being tidious and for advanced users like on matrix, so more easy and beginner friendly.

the platform also is more lenient on its acceptable policy and have a no bullshit moderation. (sadly not the case for other alternatives which sucks very much)

IMPORTANT

currently the project in its early stage and still has lots of bugs, glitches and various issues.

it is currently only accessible through a web browser (there is no app neither on desktop or on mobile)

lots of features are not finished and the platform still need major improvements. but i hope it is going to grow and become a viable alternative.

currently there are around 800 people are registered on fermi/harmony chat.

fermi.chat the main website currently (use this one to register) melodychat.org the organisation's website (its called melody on codeberg and on the website since harmony was taken)

codeberg link of both harmony and fermi :

https://codeberg.org/MelodyChat/Harmony https://codeberg.org/MelodyChat/Fermi

credit to Mathium5, eliza, devs and contributors for developping and maintaining fermi and harmony chat.

I have looked for SO long, I've tried every icon pack on f-droid, I've looked through the play store multiple times (either they were ugly or collected all of my precious data 🥹), I've even tried to make my own icon pack with renkin but it barely works (I'm not interested in fixing it) SO I just need some icon packs to look through

also I'm pretty picky, and I want either funny/kinda cursed or something that isn't flat design and monochrome

thank guy I love drew gooden

I work on OpenSubs, a free, open source (AGPL-3.0) subtitle tool that runs entirely in the browser tab.

You drop in a video file, and Whisper transcribes it on your own machine, using transformers.js with WebGPU where available and WebAssembly otherwise. The model (40–250 MB) downloads once and is cached. There is no upload endpoint in the product, so the video has nowhere to go.

After that you can:

• fix lines by typing over them (click a timestamp to jump to that moment)
• translate into 20 languages with Chrome's built-in on-device translator
• pick one of 12 caption styles, including word-by-word highlighting
• export SRT / VTT / ASS, or burn the subtitles into an MP4 (libass compiled to WebAssembly, encoded with WebCodecs)

A few things I learned building it:

• Whisper hallucinates on silence and music ("Thanks for watching!", or the Japanese equivalent). A Silero VAD pass runs before Whisper, and a cleanup step drops the known stock phrases.
• Singing doesn't count as speech for the VAD, so a music video gets a "no speech found" warning. You can still force it.

Honest limits: it only takes video files, not audio-only files. Cue timings can't be edited yet. Builds are release candidates. Everything that runs locally is free with no account; the only paid part is optional cloud translation on our backend (US$5 for 1000 credits), and you can bring your own Claude / OpenAI / DeepL key instead.

Site: https://opensubs.app/ Code: https://github.com/open-subs/opensubs

Feedback welcome, especially on languages where the transcription goes wrong.

Edit: multi domain assets would be nice. Many applications suggested here have only simple flowchart + UML diagrams.

Google's September 2026 Pixel Update Bulletin contains patches beyond what's in that month's regular Android Security Bulletin. According to GrapheneOS, some of those extra patches touch standard Android platform code, the kind that runs on non-Pixel devices, not just Pixel-branded hardware.

None of that platform-level code has reached the regular monthly bulletin or the private preview patches other manufacturers typically draw from to get their own patches ready.

And at this rate, these won't reach non-Pixel OEMs at all until Android 17 QPR2 ships later this year in December.

The project is characterizing this as Google "gatekeeping security patches to the standard Android platform code from Android OEMs." The complaints

GrapheneOS says Android 17 QPR1 shipped new developer APIs that never made it into AOSP. This is something they claim hasn't happened since Android's Honeycomb days.

Google's API diff report backs this up. Comparing Android 17 to QPR1 shows one new package, android.hardware.hid, plus changes across sixteen others, including android.media, android.os, android.provider, android.telecom, and android.view.

GrapheneOS has ported its code to QPR1 before Google even released it, but still doesn't have permission to ship that work. For now, the project is backporting Pixel firmware, kernel drivers, userspace drivers, and HALs from QPR1 onto Android 17 instead.

On top of all that, there's a compliance issue that seems to be recurring.

Google was slow to comply with a GPL source request. GrapheneOS requested sources for a build (CD1A.260905.001.A1) on September 1, and access only came through more than two weeks later.

Why this is worrying

None of these three issues is catastrophic by itself. A three-month patch delay, a paused API rollout, a two-week wait on source code—each is the kind of thing that could pass as a one-off.

Taken together, however, they point to a recurring theme. Google is holding security fixes back from the wider Android ecosystem, withholding new APIs from AOSP for the first time in over a decade, and slow-walking GPL compliance it's required to meet.

Don't even get me started on what they are doing to the Android app ecosystem.

Google is on track to require every Android app developer, whether on the Play Store, F-Droid, or anywhere else, to register with them. Come 2027, that means handing over legal identification and signing key evidence before an app can run on any certified device.

Sideloading an unverified app following this would mean enabling developer settings, waiting through a mandatory 24-hour cooldown, and clicking past several warning screens (classic scare tactics, btw).

GrapheneOS is one of dozens of organizations that signed onto the Keep Android Open campaign opposing this, alongside F-Droid, the Electronic Frontier Foundation, and the Free Software Foundation.

If you ask me, this Big Tech company is doing what's regrettably natural for it, clamping down open access to things so that its competition cannot benefit.

Running local LLMs on consumer AMD GPUs often comes with two pain points: configuring backend overrides (HSA_OVERRIDE_GFX_VERSION) and figuring out whether Vulkan or HIP/ROCm gives better token throughput on your setup.

I created two open-source tools to solve this:

1. ROCmFix Repo: github.com/xanpavle/rocmfix

Zero-dependency Python script runnable via single-line terminal command.

Detects GPU PCI IDs directly (Windows Registry / Linux lspci) to map the correct HSA_OVERRIDE_GFX_VERSION.

Automatically updates shell profiles (PowerShell, CMD, Bash, Zsh, Fish) and includes an undo command and driver diagnostic runner (rocmfix doctor).

2. InferBench Repo: github.com/xanpavle/inferbench

Automated benchmarking tool for local LLM servers (Ollama, LM Studio).

Rigorously compares Vulkan vs HIP/ROCm performance with warm-up passes, median of N runs, and cold-start VRAM unloading between test cycles.

Both projects are MIT-licensed. Check them out and let me know your benchmarking results!