Another new release of the excellent open source video capture and streaming app OBS Studio is being prepared, with OBS Studio 32.1 Beta out now. You can get testing with a few new features and tweaks to existing features.

The main new features for this release include a new Audio Mixer, a new Add Source dialog, WebRTC Simulcast support and they added missing undo/redo actions for scene items. WebRTC Simulcast sounds like quite a fun one, allowing for multiple quality levels to be sent over one track in WebRTC. Similar in a way to what Twitch have with Enhanced Broadcasting.

cross-posted from: https://lemmy.bestiver.se/post/862489

Comments

cross-posted from: https://lemmy.bestiver.se/post/862961

Comments

Wireshark 4.6.3 has been released today as the third point release to the Wireshark 4.6 series of this popular network protocol analyzer, with support for new and updated capture file and protocol support.

Coming after Wireshark 4.6.2, the Wireshark 4.6.3 release updates support for the DCT2000, DHCP, H.248, H.265, HomePlug AV, HTTP3, IDN, IEEE 802.11, LTE RRC, NAS-5GS, PKCS12, QUIC, RTPS, SOME/IP-SD, SSH, and Thrift protocols, as well as capture file support for 3GPP TS 32.423 Trace, BLF, NetScreen, and Viavi Observer.

Wireshark 4.6.3 also fixes crashes with the BLF file parser, IEEE 802.11 dissector, and SOME/IP-SD dissector, an infinite loop issue with the HTTP3 dissector, a bug preventing RTP Player streams from being stopped, ABI/API compatibility issues, and a bug in decoding 5G NAS messages.

Nginx Proxy Manager, a popular web-based and user-friendly reverse proxy management interface for Nginx, has just released version 2.13.6. Although this is only a patch release to a minor version, it actually delivers some fairly significant improvements.

The most notable change is the addition of TOTP-based two-factor authentication, allowing administrators to protect access to the web interface with time-based one-time passwords, bringing a long-requested security feature to Nginx Proxy Manager.

Certificate management has also been expanded. When creating new certificates, users can now explicitly choose between RSA and ECDSA key types, offering greater flexibility depending on compatibility or performance requirements.

FFmpeg developer Lynne has landed a number of Vulkan-related imporvements to this widely-used open-source multimedia library. Over the past year FFmpeg saw Vulkan shader-based decoding for more video formats, AV1 and VP9 extension work, performance improvements, and other work around Vulkan Video. It will be very exciting to see how FFmpeg delivers in 2026 with Vulkan Video and how the software ecosystem as a whole begins taking up this cross-platform, open industry standard for video encode/decode.

Haraltd is a Bluetooth daemon that provides a JSON-based RPC over the native OS's Bluetooth stack. It currently only supports Bluetooth Classic, and runs on Windows and MacOS. Installation instructions are in the README.

It was created to reduce the pain points of dealing with the various Bluetooth stacks present in different operating systems, and to present a simpler API to handle Bluetooth (classic) based operations. It is intended for Bluetooth managers and possibly can be used for scripting purposes. See bluetuith for an application that interacts with Haraltd.

The RPC specification is published here.

A table of the daemon's features is posted here, but to summarise:

• Adapter/device management

• Automatic/manual profile-based connection

• Pairing with authentication

• OBEX profiles (currently only Object Push, but more OBEX profiles will be added later)

• Notifications for various Bluetooth events

• JSON-based RPC over a Unix socket

This was tested only with a sum total of 3 devices (2 Android phones and 1 Bluetooth earphones), so any feedback is appreciated, especially from users who can test with other kinds of Bluetooth classic devices.

Note: No AI was used to manage the codebase or generate code

I just open sourced my personal project for tracking relationships. It's like a CRM but for people you actually care about, not sales leads.

The problem: We all have hundreds of contacts scattered everywhere, but can we remember when we last talked to an old friend? Their birthday? How we met them?

The solution: Nametag helps you track people, map how they're connected, and visualize your network as an interactive graph.

Features:

• Track people with flexible attributes (birthdays, contact info, notes)
• Map relationships (family, friends, colleagues, custom types)
• Network graph visualization showing how everyone connects
• Custom groups for organizing contacts
• Birthday and contact reminders
• Dark mode, internationalization (EN/ES)
• Mobile-responsive

Tech stack:

• Next.js 16 with TypeScript
• PostgreSQL + Prisma ORM
• D3.js for graph visualization
• Redis for rate limiting
• Tailwind CSS
• Docker Compose deployment

Why AGPL-3.0?

I chose AGPL instead of MIT/Apache because I want to ensure that if someone modifies and deploys Nametag (especially as a hosted service), they have to contribute their improvements back to the community. Personal relationship data is sensitive - users should always have the right to inspect and modify the code handling their data.

Dual model:

• Hosted SaaS: https://nametag.one/ (free tier: 50 people, paid from $1/month) - sustains development

• Self-hosted: Unlimited contacts, complete data ownership, free forever

The SaaS helps fund development, but self-hosting is a first-class citizen with no compromises. Auto-verified accounts, no email service required, works completely offline.

Contributing:

Looking for contributors! Areas where help would be awesome:

• Additional language translations (currently EN/ES)
• Graph visualization improvements (performance with 500+ nodes)
• Mobile app (Native would be great, but also open to React Native or similar)
• Export/import formats (vCard, CSV, etc.)
• Documentation improvements

GitHub: >https://github.com/mattogodoy/nametag

I'd be happy to hear any suggestions you might have. Have a nice day!

Developer @SomeDudeFromSpace@lemmy.ml

The European Commission recently launched a call for evidence on a newer initiative about the importance of open source, and their reliance on non-EU countries. As covered by CADE, the initiative is called "Towards European open digital ecosystems", and it sets out how they're trying to sort their approach towards the open-source sector across the European Union.

From the official EU document they note how the new strategy will "address the economic and political importance of open source, as a crucial contribution to a strategic framework for EU technological sovereignty, competitiveness and cybersecurity" and that it will "set out actions to strengthen the broader EU open ecosystem of solutions and products in critical sectors, including internet technologies, cloud, artificial intelligence (AI), cybersecurity, open hardware, and industrial applications (e.g. automotive and manufacturing)".

Publication croisée depuis https://programming.dev/post/43956008

Microsoft has open-sourced XAML Studio, a visual development tool for building Windows application interfaces. The project is now available on GitHub under the MIT license and has joined the .NET Foundation as a seed project.

It is a rapid prototyping tool that lets developers design and test Windows app interfaces using XAML, the markup language for WinUI, before they integrate the work into Visual Studio.

Think of it like Qt Design Studio for Qt applications, but specifically for Windows apps. It provides live editing, meaning you can see your interface changes in real time without needing to recompile your application.

Brodie a Linux YouTuber uploaded a video about a project, I was not aware off: Software Heritage. It is basically for code, what Internet Archive is for websites. If you want watch Brodies video as an introduction: >https://inv.nadeko.net/watch?v=MUA9Fu4jNGY or >YouTube directly https://youtu.be/MUA9Fu4jNGY

• Archive: https://archive.softwareheritage.org/
• Mission: https://www.softwareheritage.org/mission/
• Features: https://www.softwareheritage.org/software-heritage-features/
• FAQ: https://www.softwareheritage.org/software-heritage-faq/
• Wikipedia Article: https://en.wikipedia.org/wiki/Software_Heritage

---

We are building the universal software archive

We collect and preserve software in source code form, because software embodies our technical and scientific knowledge and humanity cannot afford the risk of losing it.

Software is a precious part of our cultural heritage. We curate and make accessible all the software we collect, because only by sharing it we can guarantee its preservation in the very long term.

I posted this article, written by Paul Romer, because while it is a few years old, the questions it adresses are more actual than ever - it could have been written yesterday. It is about propietary systems slurping up and commecializing freely available content from an economy of freely sharing ideas and facts.

The article asks why Jupyter succeed where Mathematica failed. The obvious contrast is between the proprietary world of Wolfram and the open-source model of the software ecosystem that Jupyter mobilizes.

[...]

He goes on to detail how this was implemented concretely, and what were the practical effects.

Wolfram made it hard to share a readable PDF version of a notebook because it wanted someone like me to distribute content in its proprietary file format, the CDF.

By the way, Romer starts with mentioning an article in The Atlantic, which is worth reading as well, since it brilliantly describes the achievement of Wolfram, as well as its propietary model and the effects of applying it to science. That article may not be accessible to everyone any more. An archived version of that article is here.

All my new code will be closed-source from now on. I've contributed millions of lines of carefully written OSS code over the past decade, spent thousands of hours helping other people. If you want to use my libraries (1M+ downloads/month) in the future, you have to pay.

I made good money funneling people through my OSS and being recognized as expert in several fields. This was entirely based on HUMANS knowing and seeing me by USING and INTERACTING with my code. No humans will ever read my docs again when coding agents do it in seconds. Nobody will even know it's me who built it.

Look at Tailwind: 75 million downloads/month, more popular than ever, revenue down 80%, docs traffic down 40%, 75% of engineering team laid off. Someone submitted a PR to add LLM-optimized docs and Wathan had to decline - optimizing for agents accelerates his business's death. He's being asked to build the infrastructure for his own obsolescence.

Two of the most common OSS business models:

• Open Core: Give away the library, sell premium once you reach critical mass (Tailwind UI, Prisma Accelerate, Supabase Cloud...)
• Expertise Moat: Be THE expert in your library - consulting gigs, speaking, higher salary

Tailwind just proved the first one is dying. Agents bypass the documentation funnel. They don't see your premium tier. Every project relying on docs-to-premium conversion will face the same pressure: Prisma, Drizzle, MikroORM, Strapi, and many more.

The core insight: OSS monetization was always about attention. Human eyeballs on your docs, brand, expertise. That attention has literally moved into attention layers. Your docs trained the models that now make visiting you unnecessary. Human attention paid. Artificial attention doesn't.

Some OSS will keep going - wealthy devs doing it for fun or education. That's not a system, that's charity. Most popular OSS runs on economic incentives. Destroy them, they stop playing.

Why go closed-source? When the monetization funnel is broken, you move payment to the only point that still exists: access. OSS gave away access hoping to monetize attention downstream. Agents broke downstream. Closed-source gates access directly. The final irony: OSS trained the models now killing it. We built our own replacement.

My prediction: a new marketplace emerges, built for agents. Want your agent to use Tailwind? Prisma? Pay per access. Libraries become APIs with meters. The old model: free code -> human attention -> monetization. The new model: pay at the gate or your agent doesn't get in.

I tried LocalSend to send a photo from my phone to desktop, but the phone cannot detect any the desktop, possibly since the desktop is connected to the network via Ethernet.

I can post the photo to messenger, but that would be suboptimal privacy-wise. How do you guys move photos between phone and desktop? Thanks in advance!

EDIT: Sorry that I did not clarify, but the computer is shared for my family, so it has Windows (10) on it. Some country-specific proprietary apps do not like Linux :<

Relevant links and information:

Deadline: 3/Feb/26

The European Commission has opened a "call for evidence" to help shape its European Open Digital Ecosystem Strategy. The commission is looking to reduce its dependence on software from non-EU countries:

https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=intcom%3AAres%282026%2969111

https://ec.europa.eu/info/law/better-regulation/have-your-say/initiatives/16213-European-Open-Digital-Ecosystems_en

This call for evidence aims to gather feedback from different interested stakeholders, to enrich the strategy with various perspectives.

More specifically, stakeholders are invited to reply to the following questions:

1. What are the strengths and weaknesses of the EU open-source sector? What are the main barriers that hamper (i) adoption and maintenance of high-quality and secure open source; and (ii) sustainable contributions to open‑source communities?

2. What is the added value of open source for the public and private sectors? Please provide concrete examples, including the factors (such as cost, risk, lock-in, security, innovation, among others) that are most important to assess the added value.

3. What concrete measures and actions may be taken at EU level to support the development and growth of the EU open-source sector and contribute to the EU’s technological sovereignty and cybersecurity agenda?

4. What technology areas should be prioritised and why?

5. In what sectors could an increased use of open source lead to increased competitiveness and cyber resilience?