mirrors/fediparty
1
0
Fork 0
mirror of https://codeberg.org/fediverse/fediparty.git synced 2024-11-22 08:31:28 +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-02-04 20:50:47 +00:00
"lastUpdate": "04 Feb 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-02-04 20:50:47 +00:00
"population": "662\u00a0941",
"activeUsers": "33\u00a0535",
"podsNum": "87"
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-02-04 20:50:47 +00:00
"population": "20\u00a0025",
"activeUsers": "4\u00a0898",
"podsNum": "331"
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-02-04 20:50:47 +00:00
"population": "4\u00a0841",
"activeUsers": "1\u00a0286",
"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
2024-02-04 20:50:47 +00:00
"population": "8\u00a0951\u00a0129",
"activeUsers": "2\u00a0894\u00a0725",
"podsNum": "10\u00a0764"
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-02-04 20:50:47 +00:00
"population": "479",
"activeUsers": "1\u00a0282",
"podsNum": "17"
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-02-04 20:50:47 +00:00
"population": "112\u00a0955",
"activeUsers": "19\u00a0473",
"podsNum": "983"
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-02-04 20:50:47 +00:00
"population": "668\u00a0067",
"activeUsers": "25\u00a0962",
"podsNum": "1\u00a0102"
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-02-04 20:50:47 +00:00
"population": "287\u00a0222",
"activeUsers": "62\u00a0379",
"podsNum": "1\u00a0202"
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-02-04 20:50:47 +00:00
"population": "207\u00a0545",
"activeUsers": "60\u00a0538",
"podsNum": "491"
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-02-04 20:50:47 +00:00
"population": "10\u00a0226",
"activeUsers": "2\u00a0211",
"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
},
"writefreely": {
Update numbers
2024-02-04 20:50:47 +00:00
"population": "111\u00a0735",
"activeUsers": "28\u00a0826",
"podsNum": "530"
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-02-04 20:50:47 +00:00
"population": "24\u00a0291",
"activeUsers": "3",
"podsNum": "42"
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-02-04 20:50:47 +00:00
"population": "35\u00a0661",
"activeUsers": "20",
"podsNum": "98"
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-02-04 20:50:47 +00:00
"population": "1\u00a0969\u00a0218",
"activeUsers": "105\u00a0178",
"podsNum": "775"
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-02-04 20:50:47 +00:00
"population": "1\u00a0537",
"activeUsers": "37",
"podsNum": "740"
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-02-04 20:50:47 +00:00
"population": "231",
"activeUsers": "231",
"podsNum": "231"
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-02-04 20:50:47 +00:00
"population": "25\u00a0633",
"activeUsers": "10\u00a0222",
Update numbers
2023-10-30 16:40:45 +00:00
"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
2024-02-04 20:50:47 +00:00
"population": "64",
Update numbers
2023-10-30 16:40:45 +00:00
"activeUsers": "1",
Update numbers
2024-02-04 20:50:47 +00:00
"podsNum": "64"
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-02-04 20:50:47 +00:00
"population": "16\u00a0299",
"activeUsers": "6\u00a0321",
"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-02-04 20:50:47 +00:00
"population": "15\u00a0443",
"activeUsers": "10\u00a0702",
"podsNum": "350"
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-02-04 20:50:47 +00:00
"population": "15\u00a0295",
"activeUsers": "7\u00a0324",
"podsNum": "154"
},
"iceshrimp": {
"population": "2\u00a0463",
"activeUsers": "1\u00a0487",
"podsNum": "97"
},
"sharkey": {
"population": "3\u00a0713",
"activeUsers": "1\u00a0957",
"podsNum": "152"
},
"mbin": {
"population": "4\u00a0863",
"activeUsers": "1\u00a0299",
"podsNum": "24"
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-02-04 20:50:47 +00:00
"population": "13\u00a0151\u00a0876",
"activeUsers": "3\u00a0279\u00a0897",
"podsNum": "19\u00a0069"
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