Developer of Deus Ex Randomizer, StarCraft 2 Randomizer, RollerCoaster Tycoon Randomizer, Build Engine Randomizer, and Groovie 2 in ScummVM
IDK, people will probably eventually leave Reddit, as they left Digg and Myspace and many others. Where would they go aside from the Fediverse? Almost all new alternatives being built are using the Fediverse, and it’s the only way to get more than 1000 users currently.
It might not be Lemmy, it might even be a platform that doesn’t exist yet, but they’ll be here in the Fediverse with us.
Most platforms die or never catch on at all, but the Fediverse allows the platforms to rotate in and out without losing the users or content.
Since you’re on Mbin, the Lemmy remote follow feature isn’t going to work for you
Just paste this into your search:
It probably also works in the Lemmy format (it didn’t on Kbin but I think Mbin might’ve fixed it):
There are so many communities for games (too many…) I’ll try to stick with the most active ones that haven’t been mentioned yet
Link to the community: [email protected] (this is the proper way to link people to communities)
I don’t mean a website, I mean a friend. When I tell my friend to join Lemmy I should just link them direct to an instance for them to join instead of giving them 1000 choices
If the website does want to help you choose then maybe it could just use a simple flow chart or ask some questions to narrow down the choices
this is the bash script I use to create backups
#! /bin/bash
# https://join-lemmy.org/docs/administration/backup_and_restore.html#a-sample-backup-script
now=$(date +"%Y-%m-%d_%H.%M.%S")
cd ~/lemmy && (docker-compose exec -T postgres pg_dumpall -c -U lemmy 1> dump.sql 2> dump.errors)
cd ~/lemmy && zip -r9 ~/bak-lemmy-$now.zip ./ --exclude "volumes/postgres/*"
rm -f ~/lemmy/dump.sql
it creates very small zip files as a result so it’s very efficient
I made a cron for it to run every 3 hours, like
0 */3 * * * ~/lemmy/backup.sh
To the first, rollback.
for the first, you still have everyone subbed to the newly created community made by the attacker and all the links are still updated
if instead of migrating everything right away, you have the original server of the community give redirects for each request, then that won’t help if the original server is closing down, but it’s probably the only right way to do it, I guess you could also have an angry instance admin disable the redirect to keep the community on their own server
To the second, is that a problem?
migrating and then recreating the original is actually an issue that Github has when you rename a repo, Github will give redirects for the links to the old name of the repo, but if you create another repo with the old name then the redirects are no longer served and if someone clicks on an old link then they end up at the repo that stole the name instead of the repo that was renamed
so if let’s say there was an official linus_tech_tips community on beehaw and they moved to lemmy.world, some random person could create the community again on beehaw after the migration to appear official and hijack all the old links out on the internet
you fix that by keeping the old name reserved after migration, I don’t really think that’s a big problem in this case
I actually liked @[email protected]’s idea, instead of “migrating”, you just copy the community and then send a message to every subscriber, close the original community, and put a pinned post at the top, maybe a message in the sidebar too
what happens when you clear pictrs? you mean just deleting the folder? does that break stuff?
for comparison, my instance is only communities and no users (FAQ here: https://programming.dev/post/442419 )
it’s about 5 days old but not much activity
# du -h --max-depth=2 ./
73M ./volumes/postgres
7.8M ./volumes/pictrs
8.0K ./volumes/lemmy-ui
81M ./volumes
81M ./
the latest backup is only 7.4 MB zipped, I use this backup script
#! /bin/bash
# https://join-lemmy.org/docs/administration/backup_and_restore.html#a-sample-backup-script
now=$(date +"%Y-%m-%d_%H.%M.%S")
cd ~/lemmy && (docker-compose exec -T postgres pg_dumpall -c -U lemmy 1> dump.sql 2> dump.errors)
cd ~/lemmy && zip -r9 ~/bak-lemmy-$now.zip ./ --exclude "volumes/postgres/*"
rm -f ~/lemmy/dump.sql
like I said though, not much activity
and here’s how my backup zip files have grown in size over time
6.6M bak-lemmy-2023-07-08_03.00.01.zip
6.6M bak-lemmy-2023-07-08_06.00.01.zip
6.6M bak-lemmy-2023-07-08_09.00.01.zip
6.6M bak-lemmy-2023-07-08_12.00.01.zip
6.6M bak-lemmy-2023-07-08_15.00.01.zip
6.6M bak-lemmy-2023-07-08_18.00.01.zip
6.6M bak-lemmy-2023-07-08_21.00.01.zip
6.6M bak-lemmy-2023-07-09_00.00.02.zip
6.6M bak-lemmy-2023-07-09_03.00.01.zip
6.6M bak-lemmy-2023-07-09_06.00.01.zip
6.6M bak-lemmy-2023-07-09_09.00.01.zip
6.6M bak-lemmy-2023-07-09_12.00.01.zip
6.6M bak-lemmy-2023-07-09_15.00.01.zip
6.6M bak-lemmy-2023-07-09_18.00.01.zip
6.6M bak-lemmy-2023-07-09_21.00.01.zip
6.7M bak-lemmy-2023-07-10_00.00.01.zip
6.7M bak-lemmy-2023-07-10_03.00.01.zip
6.7M bak-lemmy-2023-07-10_06.00.01.zip
6.7M bak-lemmy-2023-07-10_09.00.01.zip
6.8M bak-lemmy-2023-07-10_12.00.01.zip
6.8M bak-lemmy-2023-07-10_15.00.01.zip
7.0M bak-lemmy-2023-07-10_18.00.01.zip
7.0M bak-lemmy-2023-07-10_21.00.01.zip
7.0M bak-lemmy-2023-07-11_00.00.01.zip
7.0M bak-lemmy-2023-07-11_03.00.01.zip
7.0M bak-lemmy-2023-07-11_06.00.01.zip
7.0M bak-lemmy-2023-07-11_09.00.01.zip
7.0M bak-lemmy-2023-07-11_12.00.01.zip
7.0M bak-lemmy-2023-07-11_15.00.01.zip
7.4M bak-lemmy-2023-07-11_18.00.01.zip
This is what I did with some communities, I created my own instance to group them together
yea the reason to want more users is for niche communities, I don’t need a billion people just for memes or news, but when you subdivide your users down to niche communities suddenly you’ll want more
I wish there were more people on Lemmy talking about Deus Ex, The 7th Guest, DOS games, Randomizers, or specific TV shows that I’m currently watching (Reddit always had a pretty active sub for each and every show)
This is cool too, but I would like to offer an idea I’ve seen other communities do which is a specific day of the week for posting pictures. Like Pictures Tuesday or something.