#nlnet — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #nlnet, aggregated by home.social.
-
Got three(!) PRs merged today! 🥳
Next version of ejabberd will feature:
* new command `generate_reset_token` in case someone forgot their password
* web-admin interface for invite tokens, lists all existing invites, lets them browse, sort and filter, execute commands
* if landing page configured there’s now a start page that lets any user create invites using their account name and password (if allowed) -
On a récemment publié #authlib 1.7, et on a été accepté dans le programme #ngi0 de la fondation #nlnet. La version 1.7 apporte l'intégration à #joserfc et l'implémentation de la RFC #oidc #rpinitiated. Encore plus de choses sont à venir...
https://blog.authlib.org/2026/authlib-release-version-1-7-and-get-support-from-the-nlnet-foundation -
On a récemment publié #authlib 1.7, et on a été accepté dans le programme #ngi0 de la fondation #nlnet. La version 1.7 apporte l'intégration à #joserfc et l'implémentation de la RFC #oidc #rpinitiated. Encore plus de choses sont à venir...
https://blog.authlib.org/2026/authlib-release-version-1-7-and-get-support-from-the-nlnet-foundation -
On a récemment publié #authlib 1.7, et on a été accepté dans le programme #ngi0 de la fondation #nlnet. La version 1.7 apporte l'intégration à #joserfc et l'implémentation de la RFC #oidc #rpinitiated. Encore plus de choses sont à venir...
https://blog.authlib.org/2026/authlib-release-version-1-7-and-get-support-from-the-nlnet-foundation -
We recently released #authlib 1.7, and got support from the #nlnet #ngi0 grant. Version 1.7 brought #joserfc integration and #oidc #rpinitiated RFC implementation. More is to come...
https://blog.authlib.org/2026/authlib-release-version-1-7-and-get-support-from-the-nlnet-foundation -
We recently released #authlib 1.7, and got support from the #nlnet #ngi0 grant. Version 1.7 brought #joserfc integration and #oidc #rpinitiated RFC implementation. More is to come...
https://blog.authlib.org/2026/authlib-release-version-1-7-and-get-support-from-the-nlnet-foundation -
We recently released #authlib 1.7, and got support from the #nlnet #ngi0 grant. Version 1.7 brought #joserfc integration and #oidc #rpinitiated RFC implementation. More is to come...
https://blog.authlib.org/2026/authlib-release-version-1-7-and-get-support-from-the-nlnet-foundation -
New progress note available (after 3 years during which I posted here on ActivityPub instead of on the blog):
https://www.goffi.org/id/libervia-progress-note-2026-w16-ooph
I'm talking about current work on installation/configuration simplification and the new forge, focus on web frontend and redesign and work done with current metadata reduction and serverless XMPP (Tor, contacts e2ee, new pubsub implementation).
#Libervia #progress #XMPP #NLnet #NCI0 #Tor #pubsub #decentralized #forge #metadata #serverless
-
Indeed. And we see what the result is. After various supply chain attacks and whole range of other software supply line related issues that typically are not well handled in most #FOSS projects, the 'market' (need not be commercial clients per se) start demanding all kinds of quality compliance guarantees.
In the new and upcoming #HorizonEurope grant programs by @EUCommission I heard - there was much discussion about this - on changing nature of #NGI0 #grants as provided by @nlnet whereby the #EU mandate shifts towards placing bigger focus on these concerns.
Though I admit that I'm not fully in the loop, and neither do I know if things were already all clearly communicated to the public. Perhaps @michiel or someone else at #NLnet might point to the most relevant info resource atm.
Other than that, the misunderstandings which lead to perceived #entitlement (client/customer) or #privilege (creator/devs) are expectation mismatch, solvable by better comms practices.
-
Indeed. And we see what the result is. After various supply chain attacks and whole range of other software supply line related issues that typically are not well handled in most #FOSS projects, the 'market' (need not be commercial clients per se) start demanding all kinds of quality compliance guarantees.
In the new and upcoming #HorizonEurope grant programs by @EUCommission I heard - there was much discussion about this - on changing nature of #NGI0 #grants as provided by @nlnet whereby the #EU mandate shifts towards placing bigger focus on these concerns.
Though I admit that I'm not fully in the loop, and neither do I know if things were already all clearly communicated to the public. Perhaps @michiel or someone else at #NLnet might point to the most relevant info resource atm.
Other than that, the misunderstandings which lead to perceived #entitlement (client/customer) or #privilege (creator/devs) are expectation mismatch, solvable by better comms practices.
-
Indeed. And we see what the result is. After various supply chain attacks and whole range of other software supply line related issues that typically are not well handled in most #FOSS projects, the 'market' (need not be commercial clients per se) start demanding all kinds of quality compliance guarantees.
In the new and upcoming #HorizonEurope grant programs by @EUCommission I heard - there was much discussion about this - on changing nature of #NGI0 #grants as provided by @nlnet whereby the #EU mandate shifts towards placing bigger focus on these concerns.
Though I admit that I'm not fully in the loop, and neither do I know if things were already all clearly communicated to the public. Perhaps @michiel or someone else at #NLnet might point to the most relevant info resource atm.
Other than that, the misunderstandings which lead to perceived #entitlement (client/customer) or #privilege (creator/devs) are expectation mismatch, solvable by better comms practices.
-
Indeed. And we see what the result is. After various supply chain attacks and whole range of other software supply line related issues that typically are not well handled in most #FOSS projects, the 'market' (need not be commercial clients per se) start demanding all kinds of quality compliance guarantees.
In the new and upcoming #HorizonEurope grant programs by @EUCommission I heard - there was much discussion about this - on changing nature of #NGI0 #grants as provided by @nlnet whereby the #EU mandate shifts towards placing bigger focus on these concerns.
Though I admit that I'm not fully in the loop, and neither do I know if things were already all clearly communicated to the public. Perhaps @michiel or someone else at #NLnet might point to the most relevant info resource atm.
Other than that, the misunderstandings which lead to perceived #entitlement (client/customer) or #privilege (creator/devs) are expectation mismatch, solvable by better comms practices.
-
Indeed. And we see what the result is. After various supply chain attacks and whole range of other software supply line related issues that typically are not well handled in most #FOSS projects, the 'market' (need not be commercial clients per se) start demanding all kinds of quality compliance guarantees.
In the new and upcoming #HorizonEurope grant programs by @EUCommission I heard - there was much discussion about this - on changing nature of #NGI0 #grants as provided by @nlnet whereby the #EU mandate shifts towards placing bigger focus on these concerns.
Though I admit that I'm not fully in the loop, and neither do I know if things were already all clearly communicated to the public. Perhaps @michiel or someone else at #NLnet might point to the most relevant info resource atm.
Other than that, the misunderstandings which lead to perceived #entitlement (client/customer) or #privilege (creator/devs) are expectation mismatch, solvable by better comms practices.
-
I've just pushed a new pubsub implementation (basically a reimplementation of SàT/Libervia Pubsub on top of Libervia Backend).
May not sound exciting like that, but it's a major thing for many reasons, I hope that I can find time to blog about that tomorrow.
Also it implements XEP-0496 (Pubsub Node Relationships) and XEP-0499 (Pubsub Extended Discovery) which means node hierarchy, useful for things like forums.
This is context of https://nlnet.nl/project/ServerlessXMPP/
-
I've just pushed a new pubsub implementation (basically a reimplementation of SàT/Libervia Pubsub on top of Libervia Backend).
May not sound exciting like that, but it's a major thing for many reasons, I hope that I can find time to blog about that tomorrow.
Also it implements XEP-0496 (Pubsub Node Relationships) and XEP-0499 (Pubsub Extended Discovery) which means node hierarchy, useful for things like forums.
This is context of https://nlnet.nl/project/ServerlessXMPP/
-
I've just pushed a new pubsub implementation (basically a reimplementation of SàT/Libervia Pubsub on top of Libervia Backend).
May not sound exciting like that, but it's a major thing for many reasons, I hope that I can find time to blog about that tomorrow.
Also it implements XEP-0496 (Pubsub Node Relationships) and XEP-0499 (Pubsub Extended Discovery) which means node hierarchy, useful for things like forums.
This is context of https://nlnet.nl/project/ServerlessXMPP/
-
I've just pushed a new pubsub implementation (basically a reimplementation of SàT/Libervia Pubsub on top of Libervia Backend).
May not sound exciting like that, but it's a major thing for many reasons, I hope that I can find time to blog about that tomorrow.
Also it implements XEP-0496 (Pubsub Node Relationships) and XEP-0499 (Pubsub Extended Discovery) which means node hierarchy, useful for things like forums.
This is context of https://nlnet.nl/project/ServerlessXMPP/
-
I've just pushed a new pubsub implementation (basically a reimplementation of SàT/Libervia Pubsub on top of Libervia Backend).
May not sound exciting like that, but it's a major thing for many reasons, I hope that I can find time to blog about that tomorrow.
Also it implements XEP-0496 (Pubsub Node Relationships) and XEP-0499 (Pubsub Extended Discovery) which means node hierarchy, useful for things like forums.
This is context of https://nlnet.nl/project/ServerlessXMPP/
-
Apply for funding before June 1st 2026
Do you have a valuable idea in the area of digital commons and networked technology, that will contribute towards achieving a more open information society and brings the next generation of the internet closer? We are interested in further developing open solutions that empower users on all layers of technology.https://nlnet.nl/news/2026/20260401-call.html
#nlnet #NGI #NGI0 #NGI0CommonsFund #NGITaler #NGIFediversity
-
Apply for funding before June 1st 2026
Do you have a valuable idea in the area of digital commons and networked technology, that will contribute towards achieving a more open information society and brings the next generation of the internet closer? We are interested in further developing open solutions that empower users on all layers of technology.https://nlnet.nl/news/2026/20260401-call.html
#nlnet #NGI #NGI0 #NGI0CommonsFund #NGITaler #NGIFediversity
-
Apply for funding before June 1st 2026
Do you have a valuable idea in the area of digital commons and networked technology, that will contribute towards achieving a more open information society and brings the next generation of the internet closer? We are interested in further developing open solutions that empower users on all layers of technology.https://nlnet.nl/news/2026/20260401-call.html
#nlnet #NGI #NGI0 #NGI0CommonsFund #NGITaler #NGIFediversity
-
Apply for funding before June 1st 2026
Do you have a valuable idea in the area of digital commons and networked technology, that will contribute towards achieving a more open information society and brings the next generation of the internet closer? We are interested in further developing open solutions that empower users on all layers of technology.https://nlnet.nl/news/2026/20260401-call.html
#nlnet #NGI #NGI0 #NGI0CommonsFund #NGITaler #NGIFediversity
-
Apply for funding before June 1st 2026
Do you have a valuable idea in the area of digital commons and networked technology, that will contribute towards achieving a more open information society and brings the next generation of the internet closer? We are interested in further developing open solutions that empower users on all layers of technology.https://nlnet.nl/news/2026/20260401-call.html
#nlnet #NGI #NGI0 #NGI0CommonsFund #NGITaler #NGIFediversity
-
@deepjoy
Yes, I participated in two projects funded by #NLnet
First, #CAcert (I was on the board from 2012 to 2016, most recently as Vice President). Then, from 2016 until its unfortunate discontinuation in 2022, I worked on the #WPIA project, again as Vice President and also as Managing Director.I have to say that the email server actually requires the least work of all.
I use the #MailCow Suite @doncow , and a lot of it is already automated, and the individual components work together seamlessly.
My mail server "serves" almost the entire family network, as well as 4 small businesses and a handful of clubs. So, about 10 or 12 "main domains", and around 20 or 25 alias domains.IP reputation hasn't worried me much either; I've only had one blacklisting issue in the last five years, but the hosting provider resolved it within a few hours. And of course, you have to ensure that #DKIM, #DMARC, #SPF etc. work together correctly. Then it becomes quite easy.
So I'd say things have gotten easier since I started #selfhosting e-Mail years ago. (#mDaemon was my first hosting suite for e-Mail).Edit: I should also mention that I run an email setup with a primary mail server and a backup mail server.
-
OK so e2ee contact are implemented in Libervia, only in the CLI for now. Here are 2 screenshots:
- in the first one contacts are retrieved and rendered for the terminal. We can see contacts and groups IDs and that they are encrypted (which is optional but default).
- in the second one we see what is stored on the PEP service, so what your XMPP server admins can see, an encrypted blob.
This is highly experimental.
-
Here is the capture of the tree-like hierarchy of pubsub nodes I talked about yesterday, but this time rendered as forum categories in Libervia web. I’ve added an "XMPP" category and set descriptions (all part of pubsub node metadata). All of this benefits from pubsub permission and subscription mechanisms.
Note that this is done thanks to the NLnet Email Gateway grant.
-
-
-