HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
X11Libre
xserver
C2025–2026
X11Libre / xserver

xserver

XLibre Xserver

33Distinct people
47Mentions
0Explicit recommenders
4.8KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

XLibre Xserver

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

Favorable Commenters describe the x11libre/xserver fork as an active alternative to Xorg that offers features like easy restart and avoids corporate control. One user notes it is currently useful but requires more polishing and development effort.

This week’s discussion is favorable. This is not a standing endorsement. Read the supporting reply

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Favorable

Commenters describe the x11libre/xserver fork as an active alternative to Xorg that offers features like easy restart and avoids corporate control. One user notes it is currently useful but requires more polishing and development effort.

Supporting reply 1 · Supporting reply 2 · 1 discussions summarized

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 6:01:32 PM UTC.

IceWM direct repository linkDebated

Commenters debate whether modern display resolutions and refresh rates necessitate GPU offloading for transparency effects or if CPU performance should suffice, while simultaneously arguing over the viability of Wayland versus X11 and the role of GNOME/GTK in the Linux ecosystem.

52 readable replies · Supporting reply 1 · Supporting reply 2 · Supporting reply 3 · Supporting reply 4

Mentions over time

HN mentions by month47 dated mentions

Observed mentions: 2025-06-06 10:35:10 UTC to 2026-10-12 17:27:30 UTC.

0510152025-06-01 00:00:00 UTC to 2025-07-01 00:00:00 UTC (exclusive): 14 mentions; 3 submissions, 11 commentsJun 20252025-07-01 00:00:00 UTC to 2025-08-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-08-01 00:00:00 UTC to 2025-09-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-09-01 00:00:00 UTC to 2025-10-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-10-01 00:00:00 UTC to 2025-11-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-11-01 00:00:00 UTC to 2025-12-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2025-12-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2026-01-01 00:00:00 UTC to 2026-02-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments2026-02-01 00:00:00 UTC to 2026-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsFeb 20262026-03-01 00:00:00 UTC to 2026-04-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2026-04-01 00:00:00 UTC to 2026-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-05-01 00:00:00 UTC to 2026-06-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments2026-06-01 00:00:00 UTC to 2026-07-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments2026-07-01 00:00:00 UTC to 2026-08-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-08-01 00:00:00 UTC to 2026-09-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2026-09-01 00:00:00 UTC to 2026-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-10-01 00:00:00 UTC to 2026-11-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsOct 2026

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jun 20252025-06-01 00:00:00 UTC2025-07-01 00:00:00 UTC14311
Jul 20252025-07-01 00:00:00 UTC2025-08-01 00:00:00 UTC101
Aug 20252025-08-01 00:00:00 UTC2025-09-01 00:00:00 UTC101
Sep 20252025-09-01 00:00:00 UTC2025-10-01 00:00:00 UTC101
Oct 20252025-10-01 00:00:00 UTC2025-11-01 00:00:00 UTC101
Nov 20252025-11-01 00:00:00 UTC2025-12-01 00:00:00 UTC404
Dec 20252025-12-01 00:00:00 UTC2026-01-01 00:00:00 UTC404
Jan 20262026-01-01 00:00:00 UTC2026-02-01 00:00:00 UTC514
Feb 20262026-02-01 00:00:00 UTC2026-03-01 00:00:00 UTC000
Mar 20262026-03-01 00:00:00 UTC2026-04-01 00:00:00 UTC303
Apr 20262026-04-01 00:00:00 UTC2026-05-01 00:00:00 UTC000
May 20262026-05-01 00:00:00 UTC2026-06-01 00:00:00 UTC413
Jun 20262026-06-01 00:00:00 UTC2026-07-01 00:00:00 UTC514
Jul 20262026-07-01 00:00:00 UTC2026-08-01 00:00:00 UTC101
Aug 20262026-08-01 00:00:00 UTC2026-09-01 00:00:00 UTC202
Sep 20262026-09-01 00:00:00 UTC2026-10-01 00:00:00 UTC000
Oct 20262026-10-01 00:00:00 UTC2026-11-01 00:00:00 UTC101

What Hacker News says

14 sources
I got curious and found a ton of red flags in about half hour... Summary of the drama that resulted in Xlibre: - https://discuss.pixls.us/t/weekly-recap-8-june-2025/50638 From the README at https://github.com/X11Libre/xserver: > This is an independent project, not at all affiliated with BigTech or any of their subsidiaries or tax evasion tools, nor any political activists groups, state actors, etc. It's explicitly free of any "DEI" or similar discriminatory policies. Anybody who's treating others nicely is welcomed. This exchange between him and Torvalds in 2021: - https://lkml.org/lkml/2021/6/10/903 - https://lkml.org/lkml/2021/6/10/957
In Open source can't coordinate?
There is lots of work no ones wants to do in their free time. That is why you pay people money. And why wouldn't someone be happy working on X11? It is an open source project, it is high impact work. I would jump at it instantly if someone paid me a competitive wage to do it. Or honestly even a bit under my normal expectation. Not every person wants to work on some ego-driven rewrite of a rewrite. Some people are fine working with legacy code. Also there is a counter example right above my post. Someone was so motivated to work on it, they even forked it: https://github.com/X11Libre/xserver Granted the fork seems weirdly ideologically motivated but anyway, case in point.
In Introducing stronger dependencies on systemd
> but banning someone who cares about it and removing > their proposed contributions, feels hostile. I was curious about this so I did a little digging. It looks like the other developers were not happy with the quality of his contributions. Reading the discussions in https://gitlab.freedesktop.org/xorg/xserver/-/issues/1760 and https://gitlab.freedesktop.org/xorg/xserver/-/issues/1797 sheds a lot of light on the problems. Quoting two comments from the dozens there: > @metux i appreciate you maintaining and trying to improve Xorg but > this is the second time you break it recently, you really should > implement more testing... and > Honestly, I would strongly recommend just not merging anything @metux > does from now on. I do not feel that their presence here has been a net > positive -- I have seen zero actual bugs solved
Read the rest
by any of their code > changes. What I have seen is build breakage, ABI breakage, and ecosystem > churn from moving code around and deleting code. > Xorg could use some actual maintenance, but that means fixing actual > bugs and solving real problems. In my search I also found that the XLibre project description mentions "BigTech moles killing Xorg", XLibre being "free of DEI discrimination" and wanting to "Make X great again!" (https://github.com/X11Libre/xserver). And he posted an antivax conspiracy on the Linux kernel mailing list (https://lkml.org/lkml/2021/6/10/903). And he appears to be a German WW2 apologist (https://web.archive.org/web/20190404153507/https://lists.dyn...). So... there's that too.
In XLibre Xserver: Banned by Red Hat Developer Plans Revival of X11

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.