#agpl — Public Fediverse posts

Cairn OBS is live: Kubernetes-native log aggregation and observability.

One query language over two engines — pipe syntax over ClickHouse, full-text over embedded Tantivy, same execution plan. Dashboards, alerting, a statically linked Rust agent, multi-tenant RBAC + SSO, self-hosted AI query assist via Ollama.

AGPLv3, the whole thing. No open core, no carve-out, nothing held back for a paid tier that doesn't exist.

https://linuxexpert.org/announcing-cairn-obs/

#Kubernetes #Observability #SRE #AGPL

Ich nehme mir die Freiheit, dir die Freiheit zu nehmen, anderen die Freiheit zu nehmen.

Lizenz: #AGPL

Did PieFed ‘steal code’ from Pylova? Let’s look at what happened

This is my first open source project, apart from tiny bits of code that no one ever paid any attention to. Maybe I don’t know how to do open source properly, maybe I made a mistake here. Let’s find out.

A few months ago, someone made a new fork of PieFed, which they called ‘Pylova‘. In the first few days of it’s existence the developers of the fork were very enthusiastic about it and did a lot of interesting and useful work.

I had a browse of what they’d done and saw something cool that I wanted PieFed to have too – some improvements to cross-posting functionality and two new themes. Thinking “we’re both open source projects here, it’s fine to copy code between AGPL open source projects, right?” I went ahead and did exactly that. I genuinely believed I was exercising the rights that the AGPL grants us.

Here is the cross-posting code I copied, by generating a .patch file from the pylova repo:

https://codeberg.org/rimu/pyfedi/commit/4020ca1688069adf74c682fc9ca89adfee09e4c9

See how it has quokkau in the top left? That’s the original author there. I guess that was embedded in the .patch somehow. I didn’t give it too much thought as it didn’t seem important at the time.

Then straight afterwards I copied the themes:

https://codeberg.org/rimu/pyfedi/commit/785b15fde4a439c8a92f16eea5c2ff166fe3b7a5

This time I copied the code using copy and paste, by selecting the text in the browser and pasting it into my IDE. Unlike the complicated code in the first batch, I really just wanted the entire contents of the two styles.css files and it seemed simpler to do it that way. Unlike the first batch, this didn’t put quokka as the author in the git repo. Thinking nothing of it, I deployed the code and got on with other things.

Both the .patch with the cross-posting functionality and the themes were done within minutes of each other, as one piece of work. See the git history below:

There is not enough time between those two commits for the various events that some people allege took place to have occurred. In those 8 minutes I was busy doing the work there was no time to do anything else. I won’t go into those allegations here.

Time passes…

A week later a third party told me that the Pylova developer(s) were very unhappy that I had copied some code. Something about not giving proper attribution and that I stole code. I was very surprised and a bit confused. The header of the theme files I copied didn’t have any attribution/copyright/author statement (and still don’t) so there was no attribution statement to preserve.

Seeking to avoid any problems and angst I immediately removed that code from PieFed. Here are the commits where I did that:

Removed ‘allow cross-posting of images’: https://codeberg.org/rimu/pyfedi/commit/fcac0f20b65a782c3fe73dd2b6fa985b8a2f152a

Removed quack and groovebox themes: https://codeberg.org/rimu/pyfedi/commit/616375673795e0fa86fb79bd8ecfb2ff982e4b59

I copied code from an AGPL repository, into my AGPL repository, believing I was permitted to do so. The original files contained no attribution notices. When I learned that the author objected, I removed the code. I still believe that calling that “stealing” gives a very misleading impression of what happened.

Verdict?

Perhaps I was clumsy and ham-handed with my work in this situation? Perhaps I didn’t follow social conventions about how FOSS projects are supposed to work together? I hope my corrective action was enough. What do you think?

Regardless, I am sorry for any problems I caused for the Pylova project and will not be doing that again. I wish them well with their fork.

📬 Mirall: So funktioniert die neue Filesharing-Software
#Filesharing #Szene #AGPL #EndezuEndeVerschlüsselung #Keet #Mirall #OliverKohl #P2PTransfer #SharedSpaces https://sc.tarnkappe.info/5fd486

pmg-userprefs-sync is now public

📬 We have published pmg-userprefs-sync:
https://code.awit.at/D3/pmg-userprefs-sync

This small tool keeps per-user welcome/block lists from quarantine digests in sync across two standalone Proxmox Mail Gateways. A recipient’s decision therefore applies regardless of which equal-priority MX receives the next message.

The design is deliberately restrictive:

- Read peer data only through the PMG API with an Auditor role
- Write changes only locally via pmgsh
- Add-only: no automatic removals and no data loss
- No PMG cluster, no pmgcm, and no SSH between gateways
- Dry-run is the safe default; the systemd timer is optional

It deliberately does not synchronise filter rules, transports, TLS policies, spam scores, or quarantine contents. Those are separate concerns with different risks.

Tested with PMG 9.1.2 across two production gateways. 🔧

#Proxmox #ProxmoxMailGateway #PMG #Mailserver #SelfHosting #OpenSource #Linux #Sysadmin #DevOps #EmailSecurity #AGPL

pmg-userprefs-sync ist jetzt öffentlich

📬 Wir haben pmg-userprefs-sync veröffentlicht:
https://code.awit.at/D3/pmg-userprefs-sync

Das kleine Tool hält auf zwei unabhängigen Proxmox Mail Gateways die persönlichen Welcome-/Blocklisten aus den Quarantäne-Digests synchron. So wirkt die Entscheidung eines Empfängers unabhängig davon, über welchen gleichpriorisierten MX die nächste Mail ankommt.

Der Ansatz ist bewusst restriktiv:

- Peer-Daten nur lesend über die PMG-API mit Auditor-Rolle
- Änderungen ausschließlich lokal über pmgsh
- add-only: keine automatischen Löschungen, kein Datenverlust
- kein PMG-Cluster, kein pmgcm, kein SSH zwischen den Gateways
- Dry-run als sicherer Standard, systemd-Timer optional

Nicht synchronisiert werden Filterregeln, Transports, TLS-Policies, Spam-Scores oder Quarantäne-Inhalte. Das sind bewusst getrennte Themen mit anderen Risiken.

Getestet mit PMG 9.1.2 auf zwei produktiven Gateways. 🔧

#Proxmox #ProxmoxMailGateway #PMG #Mailserver #SelfHosting #OpenSource #Linux #Sysadmin #DevOps #EmailSecurity #AGPL

 O Proxmox VE fornece uma camada de virtualização de alta disponibilidade para o plano de gerenciamento do NVIDIA Mission Control, permitindo que as empresas implementem uma infraestrutura virtualizada e resiliente para o gerenciamento de fábricas de IA em plataformas aceleradas pela NVIDIA, incluindo os sistemas NVIDIA Blackwell e NVIDIA Vera Rubin.

Além disso, o Proxmox VE é um  hipervisor oficialmente compatível com NVIDIA vGPU . Ao integrar o software NVIDIA vGPU, as empresas podem executar cargas de trabalho de desenvolvimento de IA e com uso intensivo de gráficos em ambientes Proxmox virtualizados.

https://www.proxmox.com/en/partners/find-partner/all/partner/nvidia

#proxmox #ialocal #CodigoAberto #agpl

Almost all functions on my blog (https://blog.phoenix616.dev) now work without JavaScript!

Previously the anchors and the image links were added inside the browser with JavaScript after translating markdown to HTML but this is now done on the server-side.

For anyone wondering how my blog works: This is done by a very simple php script which renders text files as posts. You can now view the source of my blog here: https://codeberg.org/Phoenix616/blog.phoenix616.dev

#webdev #webdevelopment #blog #blogging #opensource #freesoftware #agpl #ccbysa #php #javascript

O ambiente virtual Proxmox agora está disponível para ARM de 64 bits (arm64)! | Fórum de Suporte do Proxmox

https://forum.proxmox.com/threads/proxmox-virtual-environment-now-available-for-64-bit-arm-arm64.185527/

#proxmox #agpl #CodigoAberto #arm64

«This library is licenced by AGPL-3.0»

#Programming #SoftwareDevelopment #WebDevelopment #PHP #JavaScript #Rust #Python #AI #JS #Go #Golang #Laravel #Nuxt #Astro #Svelte #NextJs #Vue #React #WebDev #Coding #Code #GPL #AGPL

No reason to deviate from #AGPL for this, @me.

The document has an obvious source form. It consists (in part) of program code. There should be no problem applying AGPL conditions for recipients.

Do you anticipate any specific problems with that plan?

I am pleased, terrified, and slightly unnerved to announce the relaunch of my blog, and the beta release of MiDy! Yes, another site generator in PHP, but this one is special. (Trust me.)

https://www.garfieldtech.com/blog/garfieldtech-v3

Feedback welcome, mainly through the MiDy issue queue but also in the PHPC chat room.

#PHP #Release #OpenSource #AGPL

The open source lover in me is most excited about an AGPL project I forked and stripped down to a handful of functions while adding a bunch more.
Despite it being built to be easy to set up, I believe a large percentage of my target demographic may not own a computer (using their phone instead).

I think the business model there is selling them a little cluster of mini computers they can self host that back each other up in case one of them is compromised. They could use the same cluster to host other phone accessible little webapp tools.

#selfhost #opensource #AGPL #copyright #advice

Things are happening... Btw... when I feel somewhat happy with it I will drop it as #AGPL on my forge.

@cy I don’t think you can neutralize people who control hundreds of billions of money.

Most important is to be aware of them, and to know that they fight copyleft, because it works.

⇒ use #AGPL where you can. Its effect:
https://opensource.google/documentation/reference/using/agpl-policy

And any time you see someone work for pay to replace a copyleft tool with a lax licensed one, you know that they are partly paid to undermine Free Software.

And that they often still mean well personally. Reality often doesn’t permit perfection.

🔧 Stack: #Nextjs dashboard, #Fastify event API, #Postgres for basic data, #ClickHouse for events, #Redis with #BullMQ for queues, #tRPC, #Tailwind and #Shadcn

📦 Self-hosting via #Docker Compose, #AGPL 3.0 license, ~5.9k stars, mostly #TypeScript

🌐 https://github.com/Openpanel-dev/openpanel

Repowise: حل مشكلة استهلاك التوكنات في وكلاء البرمجة بفهرسة ذكية للمستودع

Repowise هو مشروع مفتوح المصدر (AGPL-3.0) يحل مشكلة الاستكشاف المتكرر للمستودع الذي يستهلك ميزانية وكلاء البرمجة، عبر فهرسة المستودع مرة واحدة وتوفير طبقات ذكاء متعددة عبر بروتوكول MCP، مما يخفض اس...

🔗 https://salehgnutux.github.io/GT-NEWSTECH/ar/ai/repowise-mcp-codebase-intelligence/

#Repowise #MCP #وكيل_برمجة #توكنات #كفاءة #ذكاء_اصطناعي #AGPL #gnutux

How I Learned to Stop Worrying and Love AI

Obviously all "AI"/LLM models are trained using GPL and even better
AGPL code. Code derived from GPL/AGPL code is also GPL/AGPL code. That
means all LLM generated Code is automatically GPL/AGPL code. All those
lovely companies out there use LLM generated code. Time to request and
publish the source code under GPL/AGPL. They have nothing to hide
anyways. *plop!*

All code is free at last, now only the people must follow.
Free software for free people.

#goodnews #ai #llm #gpl #agpl #freesoftware #freedom #copyright

RT @[email protected]
I'm considering adopting the anti capitalist software license: #ACSL in preference to the #AGPL which I use currently.
Thoughts, #FOSS folk?
anticapitalist.software

The Anti-Capitalist Software L...

🧵 Η επιλογή σουίτας γραφείου για οργανισμούς στην ΕΕ είναι πλέον θέμα αρχής, όχι απλά προτίμησης!

📌 Στο νέοάρθρο:
• Σύγκριση ανοιχτού κώδικα λύσεων: #ONLYOFFICE, #Collabora, #LibreOffice, #Etherpad

🔓 Το @ONLYOFFICE Docs είναι AGPL v3, αυτο-φιλοξενούμενο και με έδρα στην ΕΕ – η επιλογή που σέβεται την ελευθερία σας.

👉 https://www.onlyoffice.com/blog/el/2026/06/best-eu-compliant-office-suites

#GDPR #NIS2 #DataSovereignty #OpenSource #FOSS #AGPL #SelfHosting #EU #Privacy #OfficeSuites #DigitalSovereignty #Tech

Voici #Euro-Office, la nouvelle #suite #bureautique #souveraine #européenne Suite au débat provoqué avec #OnlyOffice, la #Free #Software #Foundation ( #FSF), gardienne historique de la licence #AGPL, a tranché en faveur d' #Euro-Office, mettant fin au débat www.commentcamarche.net/applis-sites...

Voici Euro-Office, la nouvelle...

CCM - Comment Ça Marche: Voici #Euro-Office, la nouvelle #suite #bureautique #souveraine #européenne

Suite au débat provoqué avec #OnlyOffice, la #Free #Software #Foundation ( #FSF), gardienne historique de la licence #AGPL, a tranché en faveur d' #Euro-Office, mettant fin au débat.

https://www.commentcamarche.net/applis-sites/bureautique/38127-euro-office-la-suite-bureautique-souveraine-europeenne/

#gpl #opensource #agpl #gnu

The problem with hosting code on #Codeberg is deciding on a license. I have to, but the #AGPL seems to grand for my code, and #MIT is too permissive (I want to enforce attribution and maybe restrict 1:1 reproduction).
#foss #licensing