mirrors/fediparty
1
0
Fork 0
mirror of https://codeberg.org/fediverse/fediparty.git synced 2024-11-08 18:33: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 (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
"lastUpdate": "01 Jan 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 (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
"population": "657\u00a0194",
"activeUsers": "34\u00a0561",
"podsNum": "90"
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 (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
"population": "20\u00a0269",
"activeUsers": "5\u00a0049",
"podsNum": "340"
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 (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
"population": "4\u00a0782",
"activeUsers": "1\u00a0354",
"podsNum": "67"
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 (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
"population": "8\u00a0931\u00a0951",
"activeUsers": "3\u00a0056\u00a0556",
"podsNum": "10\u00a0971"
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 (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
"population": "345",
"activeUsers": "267",
"podsNum": "18"
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 (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
"population": "123\u00a0568",
"activeUsers": "22\u00a0212",
"podsNum": "1\u00a0024"
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 (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
"population": "650\u00a0234",
"activeUsers": "25\u00a0876",
"podsNum": "1\u00a0128"
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 (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
"population": "280\u00a0805",
"activeUsers": "59\u00a0160",
"podsNum": "1\u00a0206"
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 (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
"population": "200\u00a0582",
"activeUsers": "62\u00a0954",
"podsNum": "505"
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 (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
"population": "9\u00a0890",
"activeUsers": "2\u00a0191",
"podsNum": "109"
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 (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
"population": "96\u00a0456",
"activeUsers": "23\u00a0992",
"podsNum": "522"
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 (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
"population": "26\u00a0517",
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 (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
"population": "33\u00a0274",
"activeUsers": "3",
"podsNum": "104"
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 (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
"population": "1\u00a0965\u00a0542",
"activeUsers": "136\u00a0853",
"podsNum": "875"
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 (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
"population": "1\u00a0459",
"activeUsers": "47",
"podsNum": "718"
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 (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
"population": "235",
"activeUsers": "235",
"podsNum": "235"
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 (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
"population": "24\u00a0686",
"activeUsers": "11\u00a0524",
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 (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
"population": "71",
Update numbers
2023-10-30 16:40:45 +00:00
"activeUsers": "1",
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
"podsNum": "71"
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 (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
"population": "15\u00a0940",
"activeUsers": "6\u00a0496",
"podsNum": "568"
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": {
"population": "21\u00a0561",
"activeUsers": "16\u00a0619",
"podsNum": "445"
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 (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
"population": "15\u00a0913",
"activeUsers": "7\u00a0718",
"podsNum": "157"
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 (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
"population": "13\u00a0081\u00a0274",
"activeUsers": "3\u00a0473\u00a0669",
"podsNum": "19\u00a0305"
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