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

115 lines
2.6 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
2023-10-30 16:40:45 +00:00
"lastUpdate": "30 Oct 2023",
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
2023-10-30 16:40:45 +00:00
"population": "354\u00a0330",
"activeUsers": "41\u00a0518",
Update numbers
2023-10-04 20:59:07 +00:00
"podsNum": "94"
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
2023-10-30 16:40:45 +00:00
"population": "21\u00a0319",
"activeUsers": "5\u00a0369",
"podsNum": "353"
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
2023-10-30 16:40:45 +00:00
"population": "4\u00a0349",
"activeUsers": "1\u00a0506",
Update numbers
2023-10-04 20:59:07 +00:00
"podsNum": "68"
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
2023-10-30 16:40:45 +00:00
"population": "8\u00a0812\u00a0832",
"activeUsers": "3\u00a0369\u00a0596",
"podsNum": "11\u00a0442"
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
2023-10-30 16:40:45 +00:00
"population": "386",
"activeUsers": "324",
"podsNum": "20"
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
2023-10-30 16:40:45 +00:00
"population": "142\u00a0212",
"activeUsers": "34\u00a0003",
"podsNum": "1\u00a0095"
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
2023-10-30 16:40:45 +00:00
"population": "613\u00a0750",
"activeUsers": "26\u00a0073",
"podsNum": "1\u00a0161"
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
2023-10-30 16:40:45 +00:00
"population": "307\u00a0327",
"activeUsers": "68\u00a0873",
"podsNum": "1\u00a0172"
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
2023-10-30 16:40:45 +00:00
"population": "184\u00a0518",
"activeUsers": "58\u00a0601",
"podsNum": "516"
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
2023-10-30 16:40:45 +00:00
"population": "9\u00a0243",
"activeUsers": "2\u00a0119",
"podsNum": "115"
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
2023-10-30 16:40:45 +00:00
"population": "96\u00a0494",
"activeUsers": "19\u00a0134",
"podsNum": "536"
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
2023-10-30 16:40:45 +00:00
"population": "24\u00a0151",
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
"activeUsers": "1",
Update numbers
2023-10-30 16:40:45 +00:00
"podsNum": "46"
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
2023-10-30 16:40:45 +00:00
"population": "32\u00a0535",
Update numbers
2023-10-04 20:59:07 +00:00
"activeUsers": "20",
Update numbers
2023-10-30 16:40:45 +00:00
"podsNum": "112"
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
2023-10-30 16:40:45 +00:00
"population": "1\u00a0358\u00a0338",
"activeUsers": "114\u00a0023",
"podsNum": "1\u00a0045"
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
2023-10-30 16:40:45 +00:00
"population": "1\u00a0248",
Update numbers
2023-10-04 20:59:07 +00:00
"activeUsers": "45",
Update numbers
2023-10-30 16:40:45 +00:00
"podsNum": "689"
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
2023-10-30 16:40:45 +00:00
"population": "240",
"activeUsers": "240",
"podsNum": "240"
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
2023-10-30 16:40:45 +00:00
"population": "21\u00a0790",
"activeUsers": "10\u00a0297",
"podsNum": "106"
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
2023-10-30 16:40:45 +00:00
"population": "73",
"activeUsers": "1",
"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
},
"akkoma": {
Update numbers
2023-10-30 16:40:45 +00:00
"population": "15\u00a0141",
"activeUsers": "14\u00a0043",
"podsNum": "570"
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
"calckey": {
Update numbers
2023-10-30 16:40:45 +00:00
"population": "2\u00a0388",
"activeUsers": "2\u00a0034",
"podsNum": "58"
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
2023-10-30 16:40:45 +00:00
"population": "16\u00a0669",
"activeUsers": "10\u00a0085",
Update numbers
2023-10-04 20:59:07 +00:00
"podsNum": "161"
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
2023-10-30 16:40:45 +00:00
"population": "12\u00a0019\u00a0333",
"activeUsers": "3\u00a0777\u00a0905",
"podsNum": "19\u00a0672"
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