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

1 sources
> One would be tempted to say that perhaps they have a vested interest in making it seem like Xorg can not be fixed, even though this patch was merged in 2022, normal users still cannot use this feature in 2025. This has passed into the "yes, it's happening, and here's why it's a good thing" phase of conspiracy-theory damage control: https://mastodon.social/@alatiera/114661446785833161 The Xorg developers do not want to maintain the legacy X codebase. They do not want to perpetuate the legacy X architecture. If withholding features is what finally gets people to suck it up and switch to Wayland, if it gets app and toolkit developers and fucking NVIDIA to drop their X codepaths and put all their development effort behind Wayland, that's what they will do. Apple, Microsoft, and Google do this all the time. They drop support for the old and
Read the rest
busted and put all their effort into the new hotness. By and large, their user bases do not complain. Only Linux users are autistic enough to go "but muh 40-year-old 'network transparent' [lol, not really, watch the Daniel Stone talk again please] display server written for 8bpp framebuffers long before modern fucking GPUs emerged". As for Xlibre... to give you an idea of how clownshoes the development community is on that thing... https://github.com/X11Libre/xserver/pull/56 Not to mention being a Nazi bar. People are starting to wake up and realize what a security risk Nazi- and far-right-authored code is. Alpine already has a security exclusion on it for that reason. Other distros will follow suit.
In Xorg Neglect and XLibre Slander

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.