38 lines
1.3 KiB
Markdown
38 lines
1.3 KiB
Markdown
---
|
||
title: XLibre - FAQ & Privacy
|
||
layout: page
|
||
---
|
||
|
||
* * *
|
||
|
||
FAQ
|
||
---
|
||
|
||
**Q:** What is Xlibre?
|
||
|
||
**A:** Xlibre is a freshly created fork of the Xorg X11 server, initiated by Enrico Weigelt, aiming to provide a more actively maintained and modernized alternative to the aging X11 system.
|
||
|
||
**Q:** Why was it forked?
|
||
|
||
**A:** Xorg has been stifled by “toxic elements” and “BigTech moles” blocking significant contributions. A classic “embrace, extend, extinguish” pattern. Xlibre is presented as a pushback to revitalize the codebase.
|
||
|
||
**Q:** Who’s behind Xlibre?
|
||
|
||
**A:** The fork is led by Enrico Weigelt ([@metux](https://github.com/metux)), previously a prolific contributor to Xorg.
|
||
|
||
**Q:** What features or enhancements does Xlibre bring?
|
||
|
||
**A:** Code cleanups and modernization aimed at improved maintainability and performance. Support for Xnamespace (greater isolation) and updating nested Xnest to use libxcb.
|
||
|
||
**Q:** What about Nvidia compatibility?
|
||
|
||
**A:** We keep binary compatibility to proprietary Nvidia driver (Ver. 570 and newer).
|
||
|
||
* * *
|
||
|
||
Privacy
|
||
-------
|
||
|
||
**You** can check your cookies - if you want. You will not find any set by this page.
|
||
|
||
**This** page does not collect any data and neither does the underlying webserver. This page is only about Xlibre, not your data. |