The odd part is that it was running fine until the upgrade.
The odd part is that it was running fine until the upgrade.
I used the Lemmy-Easy-Deploy method but the catch is that I migrated from Google Cloud Free Tier to a paid server with another host. I have the backups so I can always restore from that if I really have to. I have an env file with the password that it should be using but I’m not sure how it was changed…
Good point. I did follow a few accounts I already follow on Mastodon. But then I thought “I have a Mastodon account already… Why am I doing this?”
And the Emojis instead of starring a post was throwing me off.
edit: I see there is a star online now. Maybe it was just the Kimis app that was weird.
Is Firefish the same thing as Calckey?
I created a Calckey account a couple of weeks ago but it was basically a weird Mastodon with even fewer people from what I could tell.
Project Manager
Did you request him to a add the ones you want?
Are you sure you don’t have a return character in the user name after “lemmy” accidentally? I haven’t set up an instance but it looks like that could be your issue.
I’ve been doing the same. I have all 4 but most of my time is spent on Memmy but Mlem is quickly catching up.
Wow, it hadn’t even crossed my mind that people ALREADY might not recognize it.
I blocked them this morning. Didn’t want to but it was overwhelming.
THANK YOU!!! Ugh, this has been super annoying.
Yeah, I have a kbin account and noticed the same thing. I keep going back and forth between the two. I understand why it’s implemented, but I’m not sure I entirely like the idea of having every favorite being visible to the public. At least they’re only visible on the specific comment/ post but not visible from the user profile.
I’m on lemmy.world and I can see the time and date your comment was posted and same for edited.
I couldn’t get my container started with postgress running but I had an idea:
I started the upgrade process with Lemmy-Easy-Deploy,
canceled out of it before it removed the containers,
ran
sudo docker exec -i lemmy-easy-deploy-postgres-1 psql -U lemmy -c "alter user lemmy with password 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'"
with the password set in my
env
file,then restarted the upgrade process. It’s running again.