HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
jotaen
xit
Productivity2022–2022
jotaen / xit

xit

A plain-text file format for todos and check lists

3Distinct people
12Mentions
0Explicit recommenders
1.1KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A plain-text file format for todos and check lists

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 8:59:02 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week12 dated mentions

Observed mentions: 2022-04-01 15:39:56 UTC to 2022-08-22 21:35:31 UTC. Weeks start Monday, UTC.

02462022-03-28 00:00:00 UTC to 2022-04-04 00:00:00 UTC (exclusive): 7 mentions; 1 submissions, 6 commentsMar 282022-04-04 00:00:00 UTC to 2022-04-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-04-11 00:00:00 UTC to 2022-04-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-04-18 00:00:00 UTC to 2022-04-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-04-25 00:00:00 UTC to 2022-05-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-05-02 00:00:00 UTC to 2022-05-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-05-09 00:00:00 UTC to 2022-05-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-05-16 00:00:00 UTC to 2022-05-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-05-23 00:00:00 UTC to 2022-05-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-05-30 00:00:00 UTC to 2022-06-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-06-06 00:00:00 UTC to 2022-06-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJun 62022-06-13 00:00:00 UTC to 2022-06-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-06-20 00:00:00 UTC to 2022-06-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-06-27 00:00:00 UTC to 2022-07-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-07-04 00:00:00 UTC to 2022-07-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-07-11 00:00:00 UTC to 2022-07-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-07-18 00:00:00 UTC to 2022-07-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-07-25 00:00:00 UTC to 2022-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-08-01 00:00:00 UTC to 2022-08-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-08-08 00:00:00 UTC to 2022-08-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-08-15 00:00:00 UTC to 2022-08-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-08-22 00:00:00 UTC to 2022-08-29 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 commentsAug 22

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
Mar 282022-03-28 00:00:00 UTC2022-04-04 00:00:00 UTC716
Apr 42022-04-04 00:00:00 UTC2022-04-11 00:00:00 UTC000
Apr 112022-04-11 00:00:00 UTC2022-04-18 00:00:00 UTC000
Apr 182022-04-18 00:00:00 UTC2022-04-25 00:00:00 UTC000
Apr 252022-04-25 00:00:00 UTC2022-05-02 00:00:00 UTC000
May 22022-05-02 00:00:00 UTC2022-05-09 00:00:00 UTC000
May 92022-05-09 00:00:00 UTC2022-05-16 00:00:00 UTC000
May 162022-05-16 00:00:00 UTC2022-05-23 00:00:00 UTC000
May 232022-05-23 00:00:00 UTC2022-05-30 00:00:00 UTC000
May 302022-05-30 00:00:00 UTC2022-06-06 00:00:00 UTC000
Jun 62022-06-06 00:00:00 UTC2022-06-13 00:00:00 UTC000
Jun 132022-06-13 00:00:00 UTC2022-06-20 00:00:00 UTC000
Jun 202022-06-20 00:00:00 UTC2022-06-27 00:00:00 UTC000
Jun 272022-06-27 00:00:00 UTC2022-07-04 00:00:00 UTC000
Jul 42022-07-04 00:00:00 UTC2022-07-11 00:00:00 UTC000
Jul 112022-07-11 00:00:00 UTC2022-07-18 00:00:00 UTC000
Jul 182022-07-18 00:00:00 UTC2022-07-25 00:00:00 UTC000
Jul 252022-07-25 00:00:00 UTC2022-08-01 00:00:00 UTC000
Aug 12022-08-01 00:00:00 UTC2022-08-08 00:00:00 UTC000
Aug 82022-08-08 00:00:00 UTC2022-08-15 00:00:00 UTC000
Aug 152022-08-15 00:00:00 UTC2022-08-22 00:00:00 UTC000
Aug 222022-08-22 00:00:00 UTC2022-08-29 00:00:00 UTC514

What Hacker News says

5 sources
I’ve never used TaskPaper, but the capabilities of the data format look somewhat similar. I think the difference is primarily a philosophical one: [x]it! is a file format with a formal specification that’s open source.[1] There is no “canonical” tool for it, the idea is rather that tools can be created separately. That should give users the freedom to work with their data independent of specific tools. [1] https://github.com/jotaen/xit/blob/main/Specification.md
In A plain-text file format for todos and check lists
For reference, this is the discussion around subitems / nesting: https://github.com/jotaen/xit/discussions/2 As mentioned in that ticket, I’m still reluctant to add this to the [x]it! file specification. On the one hand it seems like an obvious and useful feature, but on the other hand it’s unfortunately pretty difficult to implement in tooling. For example, I tried to add experimental support for nested subitems in the Sublime Text plugin, but I eventually had to give up, just because the syntax highlighting engine is so limited in regards to recursion. It’s the same – or much worse – for other editors. At the end of the day, I feel that it doesn’t help to add such a feature to the file format, if tools then cannot deal with it properly. Right now, the spec is so simple that it can be implemented in maybe a day or so. I see a great deal
Read the rest
of value in keeping the hurdle for tool creators small. But it’s a pretty tricky balancing act in the end.
In A plain-text file format for todos and check lists
Creator here. [x]it! was deliberately designed as a strict data format that stands on its own, as I think this makes it easier to create tooling and work with the data programmatically. However, I think use-cases and preferences are as different as the people who use them, so [x]it! doesn’t aim to be the one-size-fits-all approach. For reference, there was also some discussion about this topic going on here https://github.com/jotaen/xit/discussions/10.
In A plain-text file format for todos and check lists

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.