#libxml2 — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #libxml2, aggregated by home.social.
-
Xmloxide – an agent made rust replacement for libxml2
https://github.com/jonwiggins/xmloxide
#HackerNews #Xmloxide #Rust #libxml2 #replacement #technology #open-source
-
Xmloxide – an agent made rust replacement for libxml2
https://github.com/jonwiggins/xmloxide
#HackerNews #Xmloxide #Rust #libxml2 #replacement #technology #open-source
-
Just learning of this when Unity randomly stopped working on latest Ubuntu 25.10 update. Latest Unity release expects XML2, and I presume Ubuntu no longer ships it.
(insert XKCD meme here)
https://www.youtube.com/watch?v=GDr4fKXmUvc #opensource #foss #unity #libxml2 -
Just learning of this when Unity randomly stopped working on latest Ubuntu 25.10 update. Latest Unity release expects XML2, and I presume Ubuntu no longer ships it.
(insert XKCD meme here)
https://www.youtube.com/watch?v=GDr4fKXmUvc #opensource #foss #unity #libxml2 -
Last time I wrote XML procesing in perl was years ago, so I did a quick search about the suggested approach as of now. Among the first results was a page suggesting XML-LibXML, because it "has good reference documentation and is actively maintained". I mean, I don't insist that there are good alternatives, but knowing XML-LibXML is a #libxml2 wrapper made me hurt inside a bit about the state of the world after what happened with libxml2.
-
Last time I wrote XML procesing in perl was years ago, so I did a quick search about the suggested approach as of now. Among the first results was a page suggesting XML-LibXML, because it "has good reference documentation and is actively maintained". I mean, I don't insist that there are good alternatives, but knowing XML-LibXML is a #libxml2 wrapper made me hurt inside a bit about the state of the world after what happened with libxml2.
-
@BrodieOnLinux made some nice video about the problems of funding infrastructure FOSS projects which nobody sees, mainly with the libxml2 example, but OpenPrinting is appearing twice, too:
https://www.youtube.com/watch?v=8PTlYeLBKvI&t=590s
Problem of finding volunteershttps://www.youtube.com/watch?v=8PTlYeLBKvI&t=945s
Long time at Canonical, then funded by @sovtechfund and supported by @linuxfoundation -
@BrodieOnLinux made some nice video about the problems of funding infrastructure FOSS projects which nobody sees, mainly with the libxml2 example, but OpenPrinting is appearing twice, too:
https://www.youtube.com/watch?v=8PTlYeLBKvI&t=590s
Problem of finding volunteershttps://www.youtube.com/watch?v=8PTlYeLBKvI&t=945s
Long time at Canonical, then funded by @sovtechfund and supported by @linuxfoundation -
RE: https://social.linux.pizza/@shanmukhateja/115759299268337435
I wish #libxml2 got the same love as #curl. It would’ve been much better then.
-
RE: https://social.linux.pizza/@shanmukhateja/115759299268337435
I wish #libxml2 got the same love as #curl. It would’ve been much better then.
-
The #libxml2 situation is a sad one. It sucks that big tech companies refuse to fund a library that is so critical to their products.
Let it be known that I support Nick, the now-former, original maintainer of the project.
-
The #libxml2 situation is a sad one. It sucks that big tech companies refuse to fund a library that is so critical to their products.
Let it be known that I support Nick, the now-former, original maintainer of the project.
-
So, libxml2 developer fed up with the lack of commitment from Google, Red Hat and Amazon.
A library used by Chrome, Windows, macOS, iOS, Linux, and most tech stacks in the world: now abandoned.
Seems that the only way to force big corpo to care is to offer an AGPLv3 version and a commercial version.
https://gitlab.gnome.org/GNOME/libxml2/-/issues/976
To me, that should be the base standard.
#Linux #FOSS #FLOSS #OSS #OpenSource #FreeOpenSource #OpenSourceSoftware #Software #libxml2 #XML
-
So, libxml2 developer fed up with the lack of commitment from Google, Red Hat and Amazon.
A library used by Chrome, Windows, macOS, iOS, Linux, and most tech stacks in the world: now abandoned.
Seems that the only way to force big corpo to care is to offer an AGPLv3 version and a commercial version.
https://gitlab.gnome.org/GNOME/libxml2/-/issues/976
To me, that should be the base standard.
#Linux #FOSS #FLOSS #OSS #OpenSource #FreeOpenSource #OpenSourceSoftware #Software #libxml2 #XML
-
In all seriousness, libxml2 situation is good example of this strange limbo state of all critical libraries. Companies are chasing quick money and zero spending, so they are absolutely don't want to spend even bare minimum on supporting libraries like this. Ok, possibly RedHat as always will pick up the slack, but overall, I agree with sentiment.
It is disheartening to see software industry in general being way worse shit house than it was before. It is creaking at seems #libxml2 #software -
In all seriousness, libxml2 situation is good example of this strange limbo state of all critical libraries. Companies are chasing quick money and zero spending, so they are absolutely don't want to spend even bare minimum on supporting libraries like this. Ok, possibly RedHat as always will pick up the slack, but overall, I agree with sentiment.
It is disheartening to see software industry in general being way worse shit house than it was before. It is creaking at seems #libxml2 #software -
This academic search engine relies on #libxml2 in several places. After harvesting bibliographic metadata (mostly OAI XML) from thousands of publication repositories, we process it using libxml2 and #libxslt.
We are operating on a tiny budget, so all we can do is to hope that the maintainer of libxslt will be able to cope with maintaining libxml2 as well (as he just offered) – and extend our gratitude to the #FreeSoftware community on whose shoulders we are standing.
-
This academic search engine relies on #libxml2 in several places. After harvesting bibliographic metadata (mostly OAI XML) from thousands of publication repositories, we process it using libxml2 and #libxslt.
We are operating on a tiny budget, so all we can do is to hope that the maintainer of libxslt will be able to cope with maintaining libxml2 as well (as he just offered) – and extend our gratitude to the #FreeSoftware community on whose shoulders we are standing.
-
🚨BREAKING NEWS🚨: Local hero bails on XML parsing! 🤯 The #libxml2 maintainer steps down, leaving the project in the capable hands of... absolutely no one. 🏃♂️💨 Meanwhile, fans express gratitude and promptly scatter to the four winds. 🌪️👏 #HeroToZero
https://discourse.gnome.org/t/stepping-down-as-libxml2-maintainer/31398 #BreakingNews #XMLParsing #HeroToZero #CommunityResponse #HackerNews #ngated -
🚨BREAKING NEWS🚨: Local hero bails on XML parsing! 🤯 The #libxml2 maintainer steps down, leaving the project in the capable hands of... absolutely no one. 🏃♂️💨 Meanwhile, fans express gratitude and promptly scatter to the four winds. 🌪️👏 #HeroToZero
https://discourse.gnome.org/t/stepping-down-as-libxml2-maintainer/31398 #BreakingNews #XMLParsing #HeroToZero #CommunityResponse #HackerNews #ngated -
Looking forward to seeing Chrome devs maintain #libxml2. /s
The reality is going to be they'll either just hope someone else does it or create a whole new lib which will be so minimalistic that this will be the justification used to drop even more stuff from the #web standards.
In any case, I can't blame Nick for wanting nothing to do with it anymore, and thanks for your service.
c.f. https://discourse.gnome.org/t/stepping-down-as-libxml2-maintainer/31398
-
Looking forward to seeing Chrome devs maintain #libxml2. /s
The reality is going to be they'll either just hope someone else does it or create a whole new lib which will be so minimalistic that this will be the justification used to drop even more stuff from the #web standards.
In any case, I can't blame Nick for wanting nothing to do with it anymore, and thanks for your service.
c.f. https://discourse.gnome.org/t/stepping-down-as-libxml2-maintainer/31398
-
🧵 For the record: The maintainer of libxslt and libxml2 is a bit tired of working for free for multi-billion dollar companies.
Both libraries are used in web browsers.
https://socket.dev/blog/libxml2-maintainer-ends-embargoed-vulnerability-reports -
Libxml2 proudly parades its "no #security embargoes" policy like a badge of honor, because who needs secrecy when #hackers can have a head start? 🚀 In classic open-source fashion, it's a shining example of #innovation and #chaos, proving once again that security is just a state of mind, right? 🔓✨
https://lwn.net/SubscriberLink/1025971/73f269ad3695186d/ #Libxml2 #open #source #transparency #HackerNews #ngated -
Libxml2 proudly parades its "no #security embargoes" policy like a badge of honor, because who needs secrecy when #hackers can have a head start? 🚀 In classic open-source fashion, it's a shining example of #innovation and #chaos, proving once again that security is just a state of mind, right? 🔓✨
https://lwn.net/SubscriberLink/1025971/73f269ad3695186d/ #Libxml2 #open #source #transparency #HackerNews #ngated -
Libxml2's "no security embargoes" policy
https://lwn.net/SubscriberLink/1025971/73f269ad3695186d/
#HackerNews #Libxml2 #no #security #embargoes #policy #security #libxml2 #open-source #software #development #cybersecurity
-
Libxml2's "no security embargoes" policy
https://lwn.net/SubscriberLink/1025971/73f269ad3695186d/
#HackerNews #Libxml2 #no #security #embargoes #policy #security #libxml2 #open-source #software #development #cybersecurity
-
About #Libxml2 usage in core products (macos, chrome, windows...) "The point is that libxml2 never had the quality to be used in mainstream browsers or operating systems to begin with. [...]. Originally it was kind of a growth hack, but now these companies make billions of profits and refuse to pay back their technical debt, either by switching to better solutions, developing their own or by trying to improve libxml2." https://gitlab.gnome.org/GNOME/libxml2/-/issues/913#note_2439345
-
The lone volunteer maintainer of #libxml2, one of the open source ecosystem’s most widely used XML parsing libraries, with an excellent rant about how Apple, Google, Microsoft and their BigTech Bros exploit #opensource software and the volunteers behind it:
https://gitlab.gnome.org/GNOME/libxml2/-/issues/913#note_2439345
-
The lone volunteer maintainer of #libxml2, one of the open source ecosystem’s most widely used XML parsing libraries, with an excellent rant about how Apple, Google, Microsoft and their BigTech Bros exploit #opensource software and the volunteers behind it:
https://gitlab.gnome.org/GNOME/libxml2/-/issues/913#note_2439345
-
libxml2 Maintainer Ends Embargoed Vulnerability Reports, Citing Unsustainable Burden
The lone volunteer maintainer of libxml2, one of the open source ecosystem’s most widely used XML parsing libraries, has announced a policy shift that drops support for embargoed security vulnerability reports.
I've taken heat in other venues for talking about this kind of thing when there's been an overreaction to a near miss caused by overreliance on a project that isn't getting support from the organizations that rely on it.
There's not one here yet. Maybe big tech can pay attention this time?
-
libxml2 Maintainer Ends Embargoed Vulnerability Reports, Citing Unsustainable Burden
The lone volunteer maintainer of libxml2, one of the open source ecosystem’s most widely used XML parsing libraries, has announced a policy shift that drops support for embargoed security vulnerability reports.
I've taken heat in other venues for talking about this kind of thing when there's been an overreaction to a near miss caused by overreliance on a project that isn't getting support from the organizations that rely on it.
There's not one here yet. Maybe big tech can pay attention this time?
-
What are we (NRENs deploying SAML) gonna do about libxml2? It is now sort of unmaintained and reading the announcement for it, I can totally understand why the maintainer wants to step away.
-
Went looking for why FreeBSD #libxml2 isn't fixed yet and hooooo boy... https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279705
I really don't like to push package updates with known vulnerabilities but this one doesn't look like it's going to be resolved any time soon.
-
Went looking for why FreeBSD #libxml2 isn't fixed yet and hooooo boy... https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279705
I really don't like to push package updates with known vulnerabilities but this one doesn't look like it's going to be resolved any time soon.
-
#libxml2 2.14.1 has been released (#Xmlsoft / #libxml / #XML / #ExtensibleMarkupLanguage / #CVE / #SecurityVulnerability) https://github.com/GNOME/libxml2
-
#libxml2 2.14.1 has been released (#Xmlsoft / #libxml / #XML / #ExtensibleMarkupLanguage / #CVE / #SecurityVulnerability) https://github.com/GNOME/libxml2
-
CVE-2024-40896 Analysis: libxml2 XXE due to type confusion
https://www.openwall.com/lists/oss-security/2024/12/25/2
#cve #linux #libxml2 #xxe #vulnerability #exploitation #bug #typeconfusion
-
CVE-2024-40896 Analysis: libxml2 XXE due to type confusion
https://www.openwall.com/lists/oss-security/2024/12/25/2
#cve #linux #libxml2 #xxe #vulnerability #exploitation #bug #typeconfusion
-
I tried validating #Docbook v5 using #xmllint from #libxml2 via #RelaxNG and #Schematron but wasn't successful. The RNG validation threw unexpected errors and the Schematron validation threw an internal error. It could be my source file, but it seems fine. Does somebody here have a working setup or tips to share?
-
At $DAYJOB, we have an admin #Rails app and one feature is displaying a large block of text to the user, akin to a log file. We run that through the `sanitize` helper in the view for safety. Yesterday I learned that the #libxml2 library used by #nokogiri has a soft-limit of ten million characters per text node. In this environment, excess text gets silently truncated. You can go higher, but the Rails/Loofah #api doesn't support that.
-
#libxml2 2.12 #broke the library for existing C++ apps: "To prepare for future improvements, some API functions now expect or return a const xmlError struct."
error: invalid conversion from 'void (*)(void*, xmlError*)' {aka 'void (*)(void*, _xmlError*)'} to 'xmlStructuredErrorFunc' {aka 'void (*)(void*, const _xmlError*)'}
🤦♂️
-
Hmm. Maybe I should attempt to make an automatically generated interface from #ATS to #libguile, as I did for an interface from #Dlang to #libxml2. (The latter is sitting somewhere in my ‘chemoelectric’ repository. It is constructed mostly by Awk scripts. But I’ll probably use Object Icon instead, this time.)