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.

Opensource geodata of celltowers, wifis and bluetooth beacons is crucial.

It allows apps like UnifiedNLP to give the OS the location data it needs, without relying on GPS Sattelites.

GPS can be tampered with, and A-GPS is not privacy friendly at all.

UnifiedNLP is only found included in microG, which is pretty insecure.

But GrapheneOS devs are working on a regular user app that serves network location data, using Apple, Apple (proxied) or a local BeaconDB database!

BeaconDB is a new service to replace MozillaLocationServices which has shut down unfortunately.

Apps like TowerCollector dont yet support it, but NeoStumbler does, and also has more advanced features.

Collect network info in your region, and in the future you (and everyone else using it) dont need GPS anymore!

(You can also use the screenshots in that mastodon thread as reference)

Saw this one in a YouTube video and found it pretty nice. I won't tell what video it was though because Lemmy doesn't like such kind of them.

This week, the Open Source Initiative (OSI) made their new Open Source Artificial Intelligence Definition (OSAID) official with its 1.0 release. With this announcement, we have reached the moment that software freedom advocates have feared for decades: the definition of “open source” — with which OSI was entrusted — now differs in significant ways from the views of most software freedom advocates.

Idk why I never heard of this one before but it got an update recently so it appeared in my Droid-ify feed and now I'm sharing it. Hopefully someone finds it useful.

I've tried Raven but it's archived and not maintained anymore, Fluent Reader and Feeds both of which doesn't feel smooth at all. Any recommendations? Preferably desktop and not a self-hosted service.

After almost 3 years of work, I've finally managed to get this project stable enough to release an alpha version!

I'm proud to present Managarr - A TUI and CLI for managing your Servarr instances! At the moment, the alpha version only supports Radarr.

Not all features are implemented for the alpha version, like managing quality profiles or quality definitions, etc.

Here's some screenshots of the TUI:

Additionally, you can use it as a CLI for Radarr; For example, to search for a new film:

managarr radarr search-new-movie --query "star wars"

Or you can add a new movie by its TMDB ID:

managarr radarr add movie --tmdb-id 1895 --root-folder-path /nfs/movies --quality-profile-id 1

All features available in the TUI are also available via the CLI.

Over the last few years, there has been a surge in interest and adoption of generative artificial intelligence systems, and a corresponding interest in clarifying and delineating what open source should mean for AI and how to ensure AI serves the public interest. The DPGA Secretariat has been an active part of these conversations. Recognizing the transformative potential of AI, we have explored ways to democratise its benefits, advocating for public spending on AI that prioritises public interest and equitable access. Additionally, we have been examining how the DPG Standard may need to adapt in order to better determine what constitutes AI systems as a type of digital public good, via a community of practice (CoP), co-hosted by UNICEF.

This work has been unfolding against a backdrop of other initiatives and organisations similarly addressing complex questions surrounding the future development and use of artificial intelligence in the public interest domain. One such particularly important initiative has been the work to define open source AI stewarded by the Open Source Initiative (OSI) with the involvement of a large number of stakeholders and experts. After a two year long process the Open Source AI Definition (OSAID) Version 1.0 was released on October 28.

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

KDE are kicking off their 2024 end-of-year fundraiser just in time for Halloween!

Even if the spine-tingling horrors of the long dark night of Walpurgis are mostly imaginary, the sinister threats of predatory proprietary software providers remain all too real.

Fear not! We, the KDE community, will help you, your friends, family, company, and community banish all the creepy and insidious proprietary software that haunts your computers, phones, and household appliances.

But we can't do it alone! We need you to help us fight the good fight against the tech-ghouls from beyond. Use the form to donate any amount to our fundraiser (or become a regular donor to our community) and help us keep the dark forces of proprietary software at bay.

I've been a big fan of the slick interface of Omnivore. It could process web sites, email newsletters and RSS feeds.

The users have just been informed that Omnivore has "joined" the AI startup Eleven Labs. It may be bitter how OSS projects are being sucked up by AI, but that alone sounds innocuous enough.

What is upsetting is that the users have only until the 15.11 to export their data, after which the service will be deactivated. The export format is only usable with Eleven Labs, and exports for Pocket, Instapaper, etc are not offered, which I find just insulting.

I use linux and android. So I don't need it. One of my windows friend asked me about it. As you known windows users are scared of terminal so GUI programme. I would also like it to be open source.

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

The Open Source Initiative (OSI) released the RC1 (“Release Candidate 1” meaning: This thing is basically done and will be released as such unless something catastrophic happens) of the “Open Source AI Definition“.

Some people might wonder why that matters. Some people come up with a bit of writing on AI, what else is new? That’s basically LinkedIn’s whole existence currently. But the OSI has a very special role in the Open Source software ecosystem. Because Open Source isn’t just based on the fact whether you can see code but also about the License that code is covered under: You might get code that you can see but that you are not allowed to touch (think of the recent WinAmp release debate). The OSI basically took on the role of defining which of the different licenses that were being used all over the place actually are “Open Source” and which come with restrictions that undermine the idea.

This is very important: Picking a license is a political act with strong consequences. It can allow or forbid different modes of interaction with an object or might put certain requirements to the use.

Here's Showcase

Not useful for us but very interesting.

Some part of Readme is in spanish.

Paginis is a flipbook viewer that turns your PDFs into interactive, flip-through books. You can load a PDF from a URL or upload a local file—all while pairing it with a YouTube playlist for a more dynamic experience.

What Makes It Great? I made this as a side project because I read a lot, and the typical PDF viewer always felt a bit dry. With Paginis, you can add, update, or delete quotes and notes, use the bookmark feature to easily navigate chapters and sections, and enjoy a big page preview to get a quick overview of the content. It’s all about making reading more flexible and engaging.

Libraries & Tools: PDF.js, Three.js, DFlip, JQuery_DFlip, CSS

Source Code : Paginis

https://gitlab.com/christosangel/chaftrix

This program written in C will render the matrix effect in the terminal window in the background, while rendering an image in the foreground, allowing animation of this image in one or two dimensions.

Image rendering is done with chafa.

This program is the continuation and evolution of other projects:

https://gitlab.com/christosangel/matrix_clone

https://gitlab.com/christosangel/ascii-matrix

https://gitlab.com/christosangel/animatrix

Drivers passing through San Francisco have a new roadside distraction to consider: billboards calling out businesses that don't cough up for the open source code that they use.

The signs are the work of the Open Source Pledge – a group that launched earlier this month. It asks businesses that make use of open source code to pledge $2,000 per developer to support projects that develop the code. So far, 25 companies have signed up – but project co-founder Chad Whitacre wants bigger firms to pay their dues, too.

I've heard the main two suggestions are Codeberg and Gitlab. However, there has been some mixed feelings about GitLab I've seen across the internet in regards to them being as FOSS as Bitwarden is with their "Open-Core" model. With Codeberg though, there was a recent major security issue.

I would just be curious to get other people's thoughts throughout the community, and then I can decide where I want to migrate my repos.

@brjsp thanks again for submitting the concern here. We have made some adjustments to how the SDK code is organized and packaged to allow you to build and run the app with only GPL/OSI licenses included. The sdk-internal package references in the clients now come from a new sdk-internal repository, which follows the licensing model we have historically used for all of our clients (see LICENSE_FAQ.md for more info). The sdk-internal reference only uses GPL licenses at this time. If the reference were to include Bitwarden License code in the future, we will provide a way to produce multiple build variants of the client, similar to what we do with web vault client builds.

The original sdk repository will be renamed to sdk-secrets, and retains its existing Bitwarden SDK License structure for our Secrets Manager business products. The sdk-secrets repository and packages will no longer be referenced from the client apps, since that code is not used there.

This appears at least okay on the surface. The clients' dependency on sdk-internal didn't change but that's okay now because they have licensed sdk-internal as GPL.

The sdk-secret will remain proprietary but that's a separate product (Secrets Manager) and will apparently not be used in the regular clients. Who knows for how long though because, if you read carefully, they didn't promise that it will not be used in the future.

The fact that they had ever intended to make parts of the client proprietary without telling anyone and attempted to subvert the GPL while doing so still remains utterly unacceptable. They didn't even attempt to apologise for that.

Bitwarden has now landed itself in the category of software that I would rather move away from and cannot wholeheartedly recommend anymore. That's pretty sad.