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

The European Chips Act has set ambitious goals and its implementation is a significant pan-european effort. From an academic perspective, last year we published an open letter emphasizing the critical importance of open-source EDA for academia in Europe. We were excited and grateful to see that this initiative triggered the definition of a European roadmap in this area, and a matching Chips JU call for project funding. We believe that the projects funded by this call will have a significant impact. Moreover, we already see rising interest from many EU stakeholders, with increasing investments into open-source chip design, especially in open source IP development (e.g. RISC-V cores), and open source EDA tools.

One additional critical barrier remains toward the end-goal of building real open-source chips, especially for prototyping and education: namely, streamlining the access to open source chip production facilities (foundries) is essential. Programs like ChipIgnite, Tiny Tapeout and IHP’s open source program have become “guiding stars” that demonstrate that everyone with a computer can build chips. We believe that having low-cost, regular and easy access to chip production is critical to create excitement and build up expertise, widening the pool of chip designers with tape-out experience: a true silicon democratization and a further de-mystification of chip design.

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

Qt 6.9 is here! This release brings exciting innovations, enhanced graphics performance, and new platform capabilities to help you build exceptional applications.

Highlighted improvements in Qt 6.9 include:

• Qt Graphs: Interactive 2D panning, zooming, and dynamic 3D graph injection. Printing support now available!
• Qt Quick: GPU-accelerated SVG animations and Variable Rate Shading for improved graphics performance.
• Qt Quick Controls: New context menu support enhances desktop integration and user experience.
• XR Enhancements: Haptic feedback added for creating richter immersive virtual interactions.

The list of changes is too extensive to summarize here.

TLDR

Create an email mapped to your webhook, the webhook will be called when an email will be received. It reacts instantly to emails. Check out the 1min demo in odysee

• https://odysee.com/@jostiniane:a/gossip_dispatch:3

Long Story

I tried to share this previously in Reddit & HN but got 0 attention. I was hoping I could get some feedback here.

When I created this, I envisaged at least two use cases:

1. (main one for my workplace) Plug the generated email(s) into the monitoring system to create tickets in the project management software you are using when an alert is triggered
2. (for open source projects) Embed/Share the generated email with your users and have the email bug reports transformed into gitlab/gitea/github issues
3. (it could serve as a starting point for an open source business automation software)

This is in a very early stage, I am more than open to feature requests. I have have a bunch of improvements planned but would like to see if there's some interest first.

The project source is in gitea.v3m.net which is not public, I am open to creating a public mirror in your favorite public place (gitlab.com, github.com, ...).

I am also open to having the current instance serving right from your open source subdomain for those interested.

registration link: https://g.v3m.net/user/register (zero tracking just plain golang + htmx)

This is part of the cross-platform work for bluetuith, and is essentially a demo of the bluetooth-classic library.

This daemon provides a REST API interface to control Bluetooth Classic functions.

Features are:

• Pairing (with authentication)

• Connection (automatic and manual profile based connection)

• Object Push (Send and receive files)

And currently only on Linux, it additionally supports:

• Bluetooth network tethering (PANU/DUN)

• Media playback control (AVRCP)

It also provides an interactive API viewer (courtesy of Scalar Docs) via the "/docs" endpoint. Also, it provides an openapi command to output the entire OpenAPI specification of the REST API.

This is currently in preview (i.e. alpha).

Any feedback is appreciated.

Hi. Any suggestions for password managers which are made and mantain in UE? Share your opinions.

WDYT? For me Open-Source is the proof another model exists.

So, over the last week, Europeans discovered we are depending on US big techs (you know the ones behind trump) 🫢

So I saw some "EuroStack" stuff trying to see what we can build to reclaim sovereignty, I engaged in a kind of unformal non-academic epistemological work about economics, anthropology, climate science, business management, and a lot of other things.

The more I worked, the more I realised that's it's not just about tech, this is not just an engineering problem. It is a fundamental, systemic collapse.

So my paper is in two section:

1. An anthropological essay on neoliberalism, examining how capitalists were cunning enough to throw us social scraps to keep the gears of their operating system functional, but how they failed to anticipate the planetary limits.
2. A naive attempt to propose something for Europe.

I just realized how Open-Source is the best argument against neoliberalism.

To my friends in the United States: my heart is with you. Know that humanity has always emerged victorious against tyranny. Nobody is freestanding; we are all part of something greater.

Here are some partisan songs from my terroir, just so you can be an international fighter for peace:

• https://www.youtube.com/watch?v=cbehEj_LcCk
• https://www.youtube.com/watch?v=cUAP-fE81zs

Keep fighting on, comrades. ✊ 🟥

Camel Chat

Camel Chat is a feature-rich Flutter application designed to provide a seamless interface for communicating with large language models (LLMs) served via an Ollama server. It offers a user-friendly way to interact with open-source AI models on your own hardware.

Features

• Connect to Ollama Servers: Easily connect to any Ollama server with optional basic HTTP authentication.
• Multiple Model Support: Chat with any model available on your Ollama server.
• Complete Chat History: View and manage your conversation history.
• Dark Mode Support: Switch between light and dark themes for comfortable viewing.
• Custom System Prompts: Define system prompts to set the AI's behaviour and context.
• Export Conversations: Export your chats as markdown files for sharing or archiving.
• Chat Organisation: Auto-generated meaningful titles for your conversations.
• Responsive UI: Works seamlessly on both mobile and desktop devices.
• Code Formatting: Proper rendering and formatting of code blocks in responses.
• Local Storage: All your conversations are stored locally for privacy.

Getting Started

Prerequisites

• A running Ollama server (local or remote).

Installation

Android

Download and install the APK from the releases page.

Linux

Choose one of the following packages from the releases page:

• Debian/Ubuntu: Download and install the .deb package.
• Fedora/RHEL: Download and install the .rpm package.
• Arch: Download and install .zst package.
• Other distributions: Download the AppImage, make it executable and run it.

Setting Up Your Ollama Server

1. Install Ollama from https://ollama.com/.
2. Pull the models you want to use (e.g., ollama pull gemma3).
3. Run the Ollama server.
4. Connect Camel Chat to your server by entering the URL (e.g., http://localhost:11434/).

Roadmap

Here are some features and improvements planned for future releases:

• Stream Responses: Implement streaming responses for more interactive conversations.
• File Attachments: Upload and process files during conversations.
• Chat Statistics: View usage statistics and performance metrics.
• Release on Flathub
• Windows & macOS Support

Trusting Open Source: Can We Really Verify the Code Behind the Updates?

In today's fast-paced digital landscape, open-source software has become a cornerstone of innovation and collaboration. However, as the FREQUENCY and COMPLEXITY of UPDATES increase, a pressing question arises: how can users—particularly those without extensive technical expertise—place their trust in the security and integrity of the code?

The premise of open source is that anyone can inspect the code, yet the reality is that very few individuals have the time, resources, or knowledge to conduct a thorough review of every update. This raises significant concerns about the actual vetting processes in place. What specific mechanisms or community practices are established to ensure that each update undergoes rigorous scrutiny? Are there standardized protocols for code review, and how are contributors held accountable for their changes?

Moreover, the sheer scale of many open-source projects complicates the review process. With numerous contributors and rapid iterations, how can we be confident that the review processes are not merely cursory but genuinely comprehensive and transparent? The potential for malicious actors to introduce vulnerabilities or backdoors into the codebase is a real threat that cannot be ignored. What concrete safeguards exist to detect and mitigate such risks before they reach end users?

Furthermore, the burden of verification often falls disproportionately on individual users, many of whom may lack the technical acumen to identify potential security flaws. This raises an essential question: how can the open-source community foster an environment of trust when the responsibility for code verification is placed on those who may not have the expertise to perform it effectively?

In light of these challenges, it is crucial for the open-source community to implement robust mechanisms for accountability, transparency, and user education. This includes fostering a culture of thorough code reviews, encouraging community engagement in the vetting process, and providing accessible resources for users to understand the software they rely on.

Ultimately, as we navigate the complexities of open-source software, we must confront the uncomfortable truth: without a reliable framework for verification, the trust we place in these systems may be misplaced. How can we ensure that the promise of open source is not undermined by the very vulnerabilities it seeks to eliminate?"

Hi. Since I moved to Vivaldi from duckdcukgo browser I’m searching app that will create aliases of my email address. I don’t want to use proton pass because this option is limited for free users. Any suggestions?

I don't know what excatly my question is, because of that I would like to explain my concerns and will see what you all think about it.

It seems like the american actions to come are getting more and more unpredictable or just more assaultive. Especialy the tech scene seems willing to ignore inconvenient laws of foreign countries they operate in. While I can adapt to that by simply use other services, there are a few fields no real option is available.

While having Android as an unavoidable OS for mobile devices (at least when one still wants to use payment services like paypal and google pay) my main concern is about Open Source or better saying the place where most projects are stored: Github.

Did MS said something regarding their intentions for github and europe? While Meta, Google, Ebay etc. for example published updated general terms and conditions and clearly communicated they are unhappy with a bunch of things, MS was not that open and did not take postion as far as I know.

How likely it is to become a problem for europe to access github/gitlab/bitbucket you name it and the hosted FOSS and open dource projects lying there?

I am not that deep into the rules of FOSS and open source, so please lighten my up If I missed something essentialy or provide information about initiatives.

Maybe out there poeple are already creating a clone from github to another archive like it is done with other american public domain data stated here? (Sorry in advance, its a german article. TLDR: its about saving the public domain data of america as it is done for ukrainian data too)

TLDR:

I want to produce a markdown, HTML or PDF file for every fetched article of an RSS feed for archival purposes. If we fetch new articles with RSS, why not have the option to produce a local copy of the articles while we are at it?

Currently, most RSS readers fetch the articles and save a database of articles as some kind of file such as SQlite. This database file is specific to the software in use (Liferea, etc.), therefore not portable. Also, images files are either only temporarily saved as a cache and are therefore not visible when viewing the articles offline, or they are saved in an unorganized way (and often renamed).

This is fine for people who just want to read the news or new blogposts. But I want to save those new blogposts in a portable format and be able to read them whenever from any offline device. Basically, I want something like "SingeFile" (github.com/gildas-lormeau/SingleFile) for RSS feeds, automatically (or manually but easily) making a new file for every new article when fetching an RSS feed.

So, is there any open-source RSS software that saves the articles as separate, portable files (such as markdown, HTML, PDF, epub), or at least allows bulk exporting the articles as such?

So close yet so far:

"Newsflash" (from Flathub) allows exporting a HTML file of an article (without the images). This is almost what I want, but Newsflash doesn't allow selecting multiple articles and queing them to make HTML copies (tedious to do it one by one), nor does it save the images like SingleFile does.

Rationale:

The desired mirroring/scraping function (producing the Markdown/HTML/PDF file from an article) can piggyback from fetching the RSS feed, instead of having to scrape a site/blog separately. Since we already fetch an article when we use RSS, we should be able to locally parse the article to produce a markdown (if text only), HTML or PDF file. This saves both bandwith and hardware ressources.

It also allows to easily produce a file only for new articles, because RSS inherently appends new articles to your feed list, instead of having to manually specify what to download or not download if scraping manually.

https://gitlab.com/christosangel/deshuffle

deshuffle is a terminal word puzzle game, written in Bash.

The simple aim is to put all the given letters in order to find the shuffled word against the clock. The time available after a number of words also reduces, so the game gets harder as it goes.

There is not only one solution to every puzzle. If the user find a word with the same letters, the solution will be accepted.

By default, the adjusted definitions of the words appear in the end of each round.

The game ends when the user fails to find the word in time, or fails to create an acceptable solution altogether.

If the score is among the 10 best scores achieved, it makes it in the Top Ten Highscores.

This game was inspired by https://wordnerd.co/23words/.

Up until recently there used to be these special batteries you could put in your fire/smoke/CO alarm that would contact you on your smartphone if the alarms went off while you were away.

They don't make them anymore, and if you want anything equivalent, it seems like you have to buy into an entire "smart home control system" or whatever they're called, and I don't need or want that.

It doesn't have to be a battery, but is there some way I can set up my alarms to contact me without surrendering all my privacy? The alarms I have now also aren't hard-wired into the house, which could present a problem, but that's why the Roost batteries were so nice!

I often see Rust mentioned at the same time as MIT-type licenses.

Is it just a cultural thing that people who write Rust dislike ~~Libre~~ copyleft licenses? Or is it baked in to the language somehow?

Edit: It has been pointed out that I meant to say "copyleft", not "libre", so edited the title and body likewise.

Let's immediately acknowledge that the title is lighthearted, and that "communist company" is an oxymoron. The better choice would've been, "which is the most worker-owned, egalitarian, power-structures-free cooperative?", which SEO experts told me was too long of a title. With that said, let me tell you about Igalia and other tech cooperatives

I'm a FLOSS/linux enthusiast. Over the years I have learned some scripting, and can get around in git. Occasionally I fork someone else's project to suit it to myself. Shell scripts, webapps, browser extensions etc. The kind of thing you can work in the source of without actual programming knowledge by just looking at text files.

Recently I modified a C program to have more legible/useful (to me) terminal output. I gave it a slightly different name and for compatibility have both versions running on my system. For my use-case it is a huge improvement over the original so I want to have it publicly available where I can install it from any system. And to share in case anyone else would enjoy it.

I don't think my changes would be appreciated by the original maintainer. For one thing, no changes have been made to the code in >10 years. The dev is still active so I guess the program is considered complete. For another, my changes are breaking and specifically disrupt the "linux philosophy" aspect of the program. I think having both version co-exist is the best way.

• I don't want to confuse anyone who is trying to find the repo of the original program.
  • The original is hosted on github whereas I use codeberg; so the "forked from" relationship is not as clear as if I stayed on github
• I ?do? want to update documentation such as README in the repo to describe my changes and relationship to the original
• I ?do? want to update and --help/man in the terminal to reflect the fork's name and possibly clarify how it works
• Should I make some sort of courtesy PR or repo issue offering my changes even though I think it would be (even should be) rejected/ignored? It seems kind of time wasting.
• In the case where the original upstream was being updated, how do I integrate those with my changes? I've had some luck so far with doing my best to guess about the git process, I think using branch, sync, merge. But I couldn't tell you more than that. Any insight on how this is supposed to go? I have spent lots of time wading through git's documentation but still find the main ideas kind of confusing.
• Anything else to consider?

Since I'm just dabbling, I try to stay away from more complicated workflows, or those which require specific system set up, when possible. My experience is that when I come back to it in a few months, a year or two years, I will have forgotten a lot; it might be a different system environment. I need to be able to re-learn everything at a later time. Simple solutions that are widely-compatible, and do not rely on my memory are preferred.

I don't mind doing a bit more work than is strictly required to learn about the FLOSS process. I've done it a few times before and it is useful to me to understand things.

I suspect that since a quarter of my fellow co-workers got the pink slip a few weeks ago, tat I too will get one soon. I haven't updated my resume in a while and would love if there was a self hosted LinkedIn alternative or something. Anyone got any idea if that's a thing yet?

imagine an app that is sort of like a panic button. You get pulled over, you open the app and hit the button which then (depending on your preferences), starts recording/streaming video and audio, locks the phone, and maybe starts recording accelerometer/gps data, etc.

It would need to be thoroughly developed/tested before actually it could be ethically recommended.

What do you think? Good idea? Bad idea? unfeasible? Already existing?