mirrors/fediparty
1
0
Fork 0
mirror of https://codeberg.org/fediverse/fediparty.git synced 2024-10-01 15:52:54 +00:00
Code Issues Packages Projects Releases Wiki Activity
fediparty/source/_data/numbers.json

130 lines
2.9 KiB
JSON
Raw Normal View History

Initial commit
2018-03-12 19:31:14 +00:00
{
Add script for updating source/_data/numbers.json The JSON it produces is slightly different from what we had before: 1. indentation is a bit different; 2. it uses non-breaking space as thousands separator. I discussed this with @lostinlight and persuaded her that NBSP is less confusing than commas, because different cultures use different separators; 3. `lastUpdate` uses a format like "27 Jun 2023" rather than "27/06/23". Again, I discussed this with @lostinlight and she agreed that the new format is less confusing. Fixes #152.
2023-06-26 21:21:28 +00:00
"list": {
Update numbers
2024-06-06 12:50:20 +00:00
"lastUpdate": "06 Jun 2024",
Add script for updating source/_data/numbers.json The JSON it produces is slightly different from what we had before: 1. indentation is a bit different; 2. it uses non-breaking space as thousands separator. I discussed this with @lostinlight and persuaded her that NBSP is less confusing than commas, because different cultures use different separators; 3. `lastUpdate` uses a format like "27 Jun 2023" rather than "27/06/23". Again, I discussed this with @lostinlight and she agreed that the new format is less confusing. Fixes #152.
2023-06-26 21:21:28 +00:00
"diaspora": {
Update numbers
2024-06-06 12:50:20 +00:00
"population": "299\u00a0191",
"activeUsers": "19\u00a0412",
"podsNum": "73"
Add script for updating source/_data/numbers.json The JSON it produces is slightly different from what we had before: 1. indentation is a bit different; 2. it uses non-breaking space as thousands separator. I discussed this with @lostinlight and persuaded her that NBSP is less confusing than commas, because different cultures use different separators; 3. `lastUpdate` uses a format like "27 Jun 2023" rather than "27/06/23". Again, I discussed this with @lostinlight and she agreed that the new format is less confusing. Fixes #152.
2023-06-26 21:21:28 +00:00
},
"friendica": {
Update numbers
2024-06-06 12:50:20 +00:00
"population": "20\u00a0226",
"activeUsers": "4\u00a0839",
"podsNum": "304"
Add script for updating source/_data/numbers.json The JSON it produces is slightly different from what we had before: 1. indentation is a bit different; 2. it uses non-breaking space as thousands separator. I discussed this with @lostinlight and persuaded her that NBSP is less confusing than commas, because different cultures use different separators; 3. `lastUpdate` uses a format like "27 Jun 2023" rather than "27/06/23". Again, I discussed this with @lostinlight and she agreed that the new format is less confusing. Fixes #152.
2023-06-26 21:21:28 +00:00
},
"hubzilla": {
Update numbers
2024-06-06 12:50:20 +00:00
"population": "4\u00a0841",
"activeUsers": "1\u00a0143",
"podsNum": "72"
Add script for updating source/_data/numbers.json The JSON it produces is slightly different from what we had before: 1. indentation is a bit different; 2. it uses non-breaking space as thousands separator. I discussed this with @lostinlight and persuaded her that NBSP is less confusing than commas, because different cultures use different separators; 3. `lastUpdate` uses a format like "27 Jun 2023" rather than "27/06/23". Again, I discussed this with @lostinlight and she agreed that the new format is less confusing. Fixes #152.
2023-06-26 21:21:28 +00:00
},
"mastodon": {
Update numbers
2024-06-06 12:50:20 +00:00
"population": "8\u00a0680\u00a0478",
"activeUsers": "1\u00a0885\u00a0686",
"podsNum": "10\u00a0143"
Add script for updating source/_data/numbers.json The JSON it produces is slightly different from what we had before: 1. indentation is a bit different; 2. it uses non-breaking space as thousands separator. I discussed this with @lostinlight and persuaded her that NBSP is less confusing than commas, because different cultures use different separators; 3. `lastUpdate` uses a format like "27 Jun 2023" rather than "27/06/23". Again, I discussed this with @lostinlight and she agreed that the new format is less confusing. Fixes #152.
2023-06-26 21:21:28 +00:00
},
"gnusocial": {
Update numbers
2024-06-06 12:50:20 +00:00
"population": "-490",
"activeUsers": "222",
"podsNum": "11"
Add script for updating source/_data/numbers.json The JSON it produces is slightly different from what we had before: 1. indentation is a bit different; 2. it uses non-breaking space as thousands separator. I discussed this with @lostinlight and persuaded her that NBSP is less confusing than commas, because different cultures use different separators; 3. `lastUpdate` uses a format like "27 Jun 2023" rather than "27/06/23". Again, I discussed this with @lostinlight and she agreed that the new format is less confusing. Fixes #152.
2023-06-26 21:21:28 +00:00
},
"pleroma": {
Update numbers
2024-06-06 12:50:20 +00:00
"population": "120\u00a0033",
"activeUsers": "21\u00a0029",
"podsNum": "921"
Add script for updating source/_data/numbers.json The JSON it produces is slightly different from what we had before: 1. indentation is a bit different; 2. it uses non-breaking space as thousands separator. I discussed this with @lostinlight and persuaded her that NBSP is less confusing than commas, because different cultures use different separators; 3. `lastUpdate` uses a format like "27 Jun 2023" rather than "27/06/23". Again, I discussed this with @lostinlight and she agreed that the new format is less confusing. Fixes #152.
2023-06-26 21:21:28 +00:00
},
"misskey": {
Update numbers
2024-06-06 12:50:20 +00:00
"population": "785\u00a0379",
"activeUsers": "26\u00a0675",
"podsNum": "1\u00a0080"
Add script for updating source/_data/numbers.json The JSON it produces is slightly different from what we had before: 1. indentation is a bit different; 2. it uses non-breaking space as thousands separator. I discussed this with @lostinlight and persuaded her that NBSP is less confusing than commas, because different cultures use different separators; 3. `lastUpdate` uses a format like "27 Jun 2023" rather than "27/06/23". Again, I discussed this with @lostinlight and she agreed that the new format is less confusing. Fixes #152.
2023-06-26 21:21:28 +00:00
},
"peertube": {
Update numbers
2024-06-06 12:50:20 +00:00
"population": "147\u00a0116",
"activeUsers": "23\u00a0747",
"podsNum": "672"
Add script for updating source/_data/numbers.json The JSON it produces is slightly different from what we had before: 1. indentation is a bit different; 2. it uses non-breaking space as thousands separator. I discussed this with @lostinlight and persuaded her that NBSP is less confusing than commas, because different cultures use different separators; 3. `lastUpdate` uses a format like "27 Jun 2023" rather than "27/06/23". Again, I discussed this with @lostinlight and she agreed that the new format is less confusing. Fixes #152.
2023-06-26 21:21:28 +00:00
},
"pixelfed": {
Update numbers
2024-06-06 12:50:20 +00:00
"population": "235\u00a0233",
"activeUsers": "65\u00a0583",
"podsNum": "485"
Add script for updating source/_data/numbers.json The JSON it produces is slightly different from what we had before: 1. indentation is a bit different; 2. it uses non-breaking space as thousands separator. I discussed this with @lostinlight and persuaded her that NBSP is less confusing than commas, because different cultures use different separators; 3. `lastUpdate` uses a format like "27 Jun 2023" rather than "27/06/23". Again, I discussed this with @lostinlight and she agreed that the new format is less confusing. Fixes #152.
2023-06-26 21:21:28 +00:00
},
"funkwhale": {
Update numbers
2024-06-06 12:50:20 +00:00
"population": "11\u00a0130",
"activeUsers": "1\u00a0994",
"podsNum": "99"
Add script for updating source/_data/numbers.json The JSON it produces is slightly different from what we had before: 1. indentation is a bit different; 2. it uses non-breaking space as thousands separator. I discussed this with @lostinlight and persuaded her that NBSP is less confusing than commas, because different cultures use different separators; 3. `lastUpdate` uses a format like "27 Jun 2023" rather than "27/06/23". Again, I discussed this with @lostinlight and she agreed that the new format is less confusing. Fixes #152.
2023-06-26 21:21:28 +00:00
},
"writefreely": {
Update numbers
2024-06-06 12:50:20 +00:00
"population": "166\u00a0176",
"activeUsers": "44\u00a0713",
"podsNum": "539"
Add script for updating source/_data/numbers.json The JSON it produces is slightly different from what we had before: 1. indentation is a bit different; 2. it uses non-breaking space as thousands separator. I discussed this with @lostinlight and persuaded her that NBSP is less confusing than commas, because different cultures use different separators; 3. `lastUpdate` uses a format like "27 Jun 2023" rather than "27/06/23". Again, I discussed this with @lostinlight and she agreed that the new format is less confusing. Fixes #152.
2023-06-26 21:21:28 +00:00
},
"plume": {
Update numbers
2024-06-06 12:50:20 +00:00
"population": "23\u00a0979",
Update numbers
2024-02-04 20:50:47 +00:00
"activeUsers": "3",
Update numbers
2024-06-06 12:50:20 +00:00
"podsNum": "40"
Add script for updating source/_data/numbers.json The JSON it produces is slightly different from what we had before: 1. indentation is a bit different; 2. it uses non-breaking space as thousands separator. I discussed this with @lostinlight and persuaded her that NBSP is less confusing than commas, because different cultures use different separators; 3. `lastUpdate` uses a format like "27 Jun 2023" rather than "27/06/23". Again, I discussed this with @lostinlight and she agreed that the new format is less confusing. Fixes #152.
2023-06-26 21:21:28 +00:00
},
"mobilizon": {
Update numbers
2024-06-06 12:50:20 +00:00
"population": "28\u00a0137",
"activeUsers": "3",
"podsNum": "50"
Add script for updating source/_data/numbers.json The JSON it produces is slightly different from what we had before: 1. indentation is a bit different; 2. it uses non-breaking space as thousands separator. I discussed this with @lostinlight and persuaded her that NBSP is less confusing than commas, because different cultures use different separators; 3. `lastUpdate` uses a format like "27 Jun 2023" rather than "27/06/23". Again, I discussed this with @lostinlight and she agreed that the new format is less confusing. Fixes #152.
2023-06-26 21:21:28 +00:00
},
"lemmy": {
Update numbers
2024-06-06 12:50:20 +00:00
"population": "1\u00a0895\u00a0195",
"activeUsers": "98\u00a0127",
"podsNum": "639"
Add script for updating source/_data/numbers.json The JSON it produces is slightly different from what we had before: 1. indentation is a bit different; 2. it uses non-breaking space as thousands separator. I discussed this with @lostinlight and persuaded her that NBSP is less confusing than commas, because different cultures use different separators; 3. `lastUpdate` uses a format like "27 Jun 2023" rather than "27/06/23". Again, I discussed this with @lostinlight and she agreed that the new format is less confusing. Fixes #152.
2023-06-26 21:21:28 +00:00
},
"gotosocial": {
Update numbers
2024-06-06 12:50:20 +00:00
"population": "1\u00a0729",
"activeUsers": "42",
"podsNum": "777"
Add script for updating source/_data/numbers.json The JSON it produces is slightly different from what we had before: 1. indentation is a bit different; 2. it uses non-breaking space as thousands separator. I discussed this with @lostinlight and persuaded her that NBSP is less confusing than commas, because different cultures use different separators; 3. `lastUpdate` uses a format like "27 Jun 2023" rather than "27/06/23". Again, I discussed this with @lostinlight and she agreed that the new format is less confusing. Fixes #152.
2023-06-26 21:21:28 +00:00
},
"owncast": {
Update numbers
2024-06-06 12:50:20 +00:00
"population": "224",
"activeUsers": "224",
"podsNum": "224"
Add script for updating source/_data/numbers.json The JSON it produces is slightly different from what we had before: 1. indentation is a bit different; 2. it uses non-breaking space as thousands separator. I discussed this with @lostinlight and persuaded her that NBSP is less confusing than commas, because different cultures use different separators; 3. `lastUpdate` uses a format like "27 Jun 2023" rather than "27/06/23". Again, I discussed this with @lostinlight and she agreed that the new format is less confusing. Fixes #152.
2023-06-26 21:21:28 +00:00
},
"bookwyrm": {
Update numbers
2024-06-06 12:50:20 +00:00
"population": "27\u00a0493",
"activeUsers": "9\u00a0147",
Update numbers
2024-04-25 21:12:29 +00:00
"podsNum": "105"
Add script for updating source/_data/numbers.json The JSON it produces is slightly different from what we had before: 1. indentation is a bit different; 2. it uses non-breaking space as thousands separator. I discussed this with @lostinlight and persuaded her that NBSP is less confusing than commas, because different cultures use different separators; 3. `lastUpdate` uses a format like "27 Jun 2023" rather than "27/06/23". Again, I discussed this with @lostinlight and she agreed that the new format is less confusing. Fixes #152.
2023-06-26 21:21:28 +00:00
},
"microblogpub": {
Update numbers
2024-06-06 12:50:20 +00:00
"population": "52",
Update numbers
2024-04-25 21:12:29 +00:00
"activeUsers": "2",
Update numbers
2024-06-06 12:50:20 +00:00
"podsNum": "52"
Add script for updating source/_data/numbers.json The JSON it produces is slightly different from what we had before: 1. indentation is a bit different; 2. it uses non-breaking space as thousands separator. I discussed this with @lostinlight and persuaded her that NBSP is less confusing than commas, because different cultures use different separators; 3. `lastUpdate` uses a format like "27 Jun 2023" rather than "27/06/23". Again, I discussed this with @lostinlight and she agreed that the new format is less confusing. Fixes #152.
2023-06-26 21:21:28 +00:00
},
"akkoma": {
Update numbers
2024-06-06 12:50:20 +00:00
"population": "17\u00a0481",
"activeUsers": "6\u00a0361",
"podsNum": "555"
Add script for updating source/_data/numbers.json The JSON it produces is slightly different from what we had before: 1. indentation is a bit different; 2. it uses non-breaking space as thousands separator. I discussed this with @lostinlight and persuaded her that NBSP is less confusing than commas, because different cultures use different separators; 3. `lastUpdate` uses a format like "27 Jun 2023" rather than "27/06/23". Again, I discussed this with @lostinlight and she agreed that the new format is less confusing. Fixes #152.
2023-06-26 21:21:28 +00:00
},
Update numbers (and fix update-numbers.py) Kudos to David Morley for the help: https://gitlab.com/diasporg/poduptime/-/issues/69
2024-01-01 19:30:19 +00:00
"firefish": {
Update numbers
2024-06-06 12:50:20 +00:00
"population": "18\u00a0097",
"activeUsers": "10\u00a0324",
"podsNum": "251"
Add script for updating source/_data/numbers.json The JSON it produces is slightly different from what we had before: 1. indentation is a bit different; 2. it uses non-breaking space as thousands separator. I discussed this with @lostinlight and persuaded her that NBSP is less confusing than commas, because different cultures use different separators; 3. `lastUpdate` uses a format like "27 Jun 2023" rather than "27/06/23". Again, I discussed this with @lostinlight and she agreed that the new format is less confusing. Fixes #152.
2023-06-26 21:21:28 +00:00
},
"hometown": {
Update numbers
2024-06-06 12:50:20 +00:00
"population": "14\u00a0798",
"activeUsers": "5\u00a0924",
"podsNum": "142"
Update numbers
2024-02-04 20:50:47 +00:00
},
"iceshrimp": {
Update numbers
2024-06-06 12:50:20 +00:00
"population": "2\u00a0882",
"activeUsers": "1\u00a0506",
"podsNum": "111"
Update numbers
2024-02-04 20:50:47 +00:00
},
"sharkey": {
Update numbers
2024-06-06 12:50:20 +00:00
"population": "10\u00a0411",
"activeUsers": "4\u00a0089",
"podsNum": "241"
Update numbers
2024-02-04 20:50:47 +00:00
},
"mbin": {
Update numbers
2024-06-06 12:50:20 +00:00
"population": "5\u00a0343",
"activeUsers": "1\u00a0310",
"podsNum": "22"
Add script for updating source/_data/numbers.json The JSON it produces is slightly different from what we had before: 1. indentation is a bit different; 2. it uses non-breaking space as thousands separator. I discussed this with @lostinlight and persuaded her that NBSP is less confusing than commas, because different cultures use different separators; 3. `lastUpdate` uses a format like "27 Jun 2023" rather than "27/06/23". Again, I discussed this with @lostinlight and she agreed that the new format is less confusing. Fixes #152.
2023-06-26 21:21:28 +00:00
},
"fediverse": {
Update numbers
2024-06-06 12:50:20 +00:00
"population": "12\u00a0515\u00a0134",
"activeUsers": "2\u00a0232\u00a0105",
"podsNum": "17\u00a0608"
Initial commit
2018-03-12 19:31:14 +00:00
}
Add script for updating source/_data/numbers.json The JSON it produces is slightly different from what we had before: 1. indentation is a bit different; 2. it uses non-breaking space as thousands separator. I discussed this with @lostinlight and persuaded her that NBSP is less confusing than commas, because different cultures use different separators; 3. `lastUpdate` uses a format like "27 Jun 2023" rather than "27/06/23". Again, I discussed this with @lostinlight and she agreed that the new format is less confusing. Fixes #152.
2023-06-26 21:21:28 +00:00
}
Update numbers
2023-10-04 20:59:07 +00:00
}
Reference in a new issue Copy permalink