Idk what to say about this one. It's very self-explanatory. Visit the official page for more information about the features I guess.

Also (according to the GitHub page) it's made by a 15 year old which is extremely impressive.

It started with me wanting to support Lemmy, my Lemmy instance and Voyager. Then I checked what other open source apps I had installed from F-Droid. It would exceed my budget to donate to them all, so I chose the 10 apps that I most frequently use.

• Lemmy
• My Lemmy instance
• Aegis
• DAVx5
• F-Droid
• Feeder
• HeliBoard
• KeePassDX
• Öffi
• Voyager
• Honorable mention to AntennaPod. It was on this list, but their contribution page states that their costs are already covered.

This is just my personal list, but I thought it's a nice idea to share it and maybe others will do the same and donate to their most used open source apps and projects.

Visit F-Droid to See Screenshot: https://f-droid.org/packages/com.eanema.graph89/

I click on "edit"

then am greeted by the 403 page, saying that the

item not available

the item is not available due to issues with the item's content.

even the newly uploaded items

First post on lemmy I dont really know how to use the ui sorry if the post ends up looking weird

https://gitlab.com/christosangel/genmon-mpv

This project is created for use with the xfce desktop environment, and the mpv media player.

With the use of the Generic Monitor panel plugin, it displays scrolling the name of the file or the stream playing with mpv.

If another instance of mpv starts playing, genmon-mpv will display the most recently opened title of file/stream.

As soon as an mpv instance displayed is closed, and another previous instance is still open, genmon-mpv will display the title of the still open file/stream.

This project is consisted of two scripts, one in bash, and one in lua. Any feedback is most welcome.

It's possible to submit questions already. Getting a feeling there'll be some uncomfortable ones; we'll see if they dare to engage with those.

A lot of the frustration that people have stems from Firefox's deeply flawed financing model, whereby the focus can never be solely put on the quality of the browser. Personally, with Google now being recognized as a monopolist and Mozilla in danger of losing 85% of its funding, I hope they can adopt Thunderbird's financing model (i.e. donations).

Now that they're not doing fundraising for lawmaking and/or grassroots activism because their advocacy team shut down, I hope they'll get a few people together and start to raise money from the user base.

This could be a very positive change for Mozilla if they play it right.

I thought this game was well known but I haven't seen almost any mentions of it recently. It's very weird for a FOSS enthusiast not to advertise one of the best open-source games of all time so here I am trying to make it spoken about again.

Disclaimer: this game may be addictive for some individuals. Player discretion is advised. If you notice any symptoms of addiction while and/or after playing the game, stop playing immediately and consult with your doctor. Untreated gaming addiction may result in severe consequences such as digestive disorders, social behavioral disorders, loss of job, and depression.

cross-posted from: https://beehaw.org/post/16923010

2024-11-06 by GIMP Team

We are very excited to share the first release candidate for the long-awaited GIMP 3.0! We’ve been hard at work since our last development update to get this ready, and we’re looking forward to everyone finally being able to see the results.

So, what exactly is a “release candidate” (RC)? A release candidate is something that might be ready to be GIMP 3.0, but we want the larger community to test it first and report any problems they find. If user feedback reveals only small and easy to fix bugs, we will solve those problems and issue the result as GIMP 3.0. However, we hope and expect a much larger audience to try out 3.0 RC1 - including many people who have only been using 2.10 up until now. If larger bugs and regressions are uncovered that require more substantial code changes, we may need to publish a second release candidate for further testing.

This the developers version so it probably comes with a bunch of bugs. test it and report back to the devs.

Discovering your application by usecase validation. Make test writing fast, understandable by any human understanding English or French. Open source under MIT license.

[Cross-posted from https://programming.dev/post/21401242]

Bitwarden isn't going proprietary after all. The company has changed its license terms once again – but this time, it has switched the license of its software development kit from its own homegrown one to version three of the GPL instead.

The move comes just weeks after we reported that it wasn't strictly FOSS any more. At the time, the company claimed that this was just a mistake in how it packaged up its software, saying on Twitter:

It seems like a packaging bug was misunderstood as something more, and the team plans to resolve it. Bitwarden remains committed to the open source licensing model in place for years, along with retaining a fully featured free version for individual users.

Now it's followed through on this. A GitHub commit entitled "Improve licensing language" changes the licensing on the company's SDK from its own license to the unmodified GPL3.

Previously, if you removed the internal SDK, it was no longer possible to build the publicly available source code without errors. Now the publicly available SDK is GPL3 and you can get and build the whole thing.

Unfortunately, due to the complexity and specialized nature of AVX-512, such optimizations are typically reserved for performance-critical applications and require expertise in low-level programming and processor microarchitecture.

cross-posted from: https://sh.itjust.works/post/27594376

https://github.com/umutcamliyurt/Amnesichat

The Abstract Wikipedia team is working toward a rewrite of our backend services in a different programming language, likely Rust. Node/JS has served us well, but we have run up against some [WebAssembly System Interface] limits that would be best dealt with by switching to a different ecosystem.