{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiea3djr2mjubme2z34ttmzh5iq4h2mhxgeohsvgpfditpmn4k2y5e",
    "uri": "at://did:plc:4n6wgsqsqm6q2hjncgwmreey/app.bsky.feed.post/3mf4psem2qeb2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreibv3znl6l5i4jnpnblcg6ypkixwtxppo6obijmrvmw6jzphhdcidy"
    },
    "mimeType": "image/jpeg",
    "size": 22208
  },
  "path": "/post/45865304",
  "publishedAt": "2026-02-16T17:28:10.000Z",
  "site": "https://programming.dev",
  "tags": [
    "Linux",
    "cm0002",
    "21 comments",
    "https://linuxiac.com/kde-responds-to-fud-over-alleged-systemd-mandate/"
  ],
  "textContent": "submitted by cm0002 to linux\n61 points | 21 comments\nhttps://linuxiac.com/kde-responds-to-fud-over-alleged-systemd-mandate/\n\n> Here’s something that’s both surprising and, in a way, not surprising at all, especially after yesterday’s announcement from KaOS, a distribution long known for its deep commitment to the KDE Plasma desktop, that it plans to move away from it. The main reason cited was KDE’s reliance on systemd in a specific component.\n>\n> As expected, the news quickly gained traction, prompting KDE to clarify its dependence on systemd and which parts of the desktop environment rely on it. In a post on KDE’s Reddit community titled “A quick anti-FUD FAQ to debunk ‘the KDE is forcing systemd!’ hoax“, the contributor described the claims as misinformation and provided a short FAQ clarifying the project’s position.",
  "title": "KDE Responds to FUD Over Alleged systemd Mandate"
}