utopify_org

joined 2 years ago
 

I've reinstalled lemmy several times and after I went public with my instance, I figured out federation is broken for those posts with a low id, because those posts got federated and after reinstall, they have been ghost data and no sync happened.

Now, I've figured out that almost every post is broken and doesn't federate correctly. It shows the wrong posts on different mastodon instances.

Will a new installation, BUT with a new subdomain solve the problem?

If yes, will it be possible to move all posts to the new installation without breaking anything or do I have to rewrite every post?

I've created a question about the moving posts on Github, too.

[–] utopify_org@lemmy.ml 2 points 1 year ago

What a big no-go, if you could lock out yourself as an admin.

That's such a sloppy craftsmanship.

[–] utopify_org@lemmy.ml 1 points 1 year ago (2 children)

What exactly was the issue with your verification system?

Currently the emails get out. At least I can see people creating accounts and posting stuff.

[–] utopify_org@lemmy.ml 1 points 1 year ago

but if the user has any posts

They are unverified, they can't have posts.

If the user has no posts you may need to delete from the database directly for now.

Do you know by any chance how to do this in a clean way, because I tried and there have been restovers.

 

I've set up a Lemmy instance and tested federation by commenting with my Mastodon account on the lemmy instance, which worked.

But I broke the test instance and had to start over (not even once).

The productive instance runs now, but after a few days I figured out that there is still the old post from the old installation on Mastodon and over Mastodon I can't see the new post and no new comments?

It is the same link (older Mastodon post, old Mastodon post, new Lemmy post), but the content is different.

  • The post itself doesn't update (it is completely different)
  • The comments don't update (different comments)

How to solve this problem? Is it even solvable?

[–] utopify_org@lemmy.ml 1 points 1 year ago* (last edited 1 year ago) (2 children)

Yes, that's exactly what I described with the issue, that a lot of other features will be deactivated too, because there is only one button for everything.

But if you know it: How exactly do I deactivate the "All Feed" to not pollute my server and avoid distractions to the users, but let them comment on external posts, without having the complete post on my instance and let external people comment on posts on my instance?

Thanks for your help.

[–] utopify_org@lemmy.ml 1 points 1 year ago

Well, it is playing around with the db 😀 ... and it could even destroy the whole instance if people don't see the warning I've posted there.

 

I'd like to create a safe space without distraction and a focus on specific topics.

But as soon as a user from my instance posts or reacts to something outside of my instance, a lot of data gets transferred and everyone from my instance will see the post in the "All" timeline.

This could lead to a lot of distraction pretty fast, especially people with ADHD could lose track if they see some interesting stuff from other instances. I want to avoid this and give them a safe space to be able to focus.

The only way I figured out was to deactivate federation at all. There is only one button in the settings.

But I would like to keep the feature that people could comment from other Fediverse tools like Mastodon, Kbin, Peertube, etc., but it doesn't work anymore, if federation is deactivated.

Is there a way to keep away all federated content from other instances, which got in touch with my users (proactively cross-posted stuff is okay), but keep the feature so people from other instances could post something?

And it would be okay if my users comment on external posts, too, but not all people on my instance have to know it or get distracted by it.

Thank you for your help :)

[–] utopify_org@lemmy.ml 2 points 1 year ago* (last edited 1 year ago) (2 children)

I found a solution here

A warning to people who have the same problem:

On the website there is a command, which will purge all unverified account. If your admin account wasn't verified, it will be purged, too.

Thanks a lot for your help :)

[–] utopify_org@lemmy.ml 3 points 1 year ago* (last edited 1 year ago)

I found a solution here

A warning to people who have the same problem:

On the website there is a command, which will purge all unverified account. If your admin account wasn't verified, it will be purged, too.

Thanks a lot for your help :)

[–] utopify_org@lemmy.ml 1 points 1 year ago (2 children)

psql -U postgres

No luck with this comman :(

psql: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: FATAL: role "postgres" does not exist

But is it the right docker container? The name of the container I try to connect is lemmymydomaintld_postgres_1

Seems pretty hard to delete a user this way. Do you know an easier way by any chance?

[–] utopify_org@lemmy.ml 1 points 1 year ago* (last edited 1 year ago)

How exactly? The recommendations of other people here didn't work.

EDIT: Found a solution. Check other posts to see how it works.

[–] utopify_org@lemmy.ml 1 points 1 year ago (4 children)

After executing docker exec -it lemmymydomain_postgres_1 psql

I've got the error:

psql: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: FATAL: role "root" does not exist

[–] utopify_org@lemmy.ml 1 points 1 year ago (4 children)

docker exec -it postgres bash

After executing this command and executing psql, I got this error:

psql: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: FATAL: role "root" does not exist

 

I've installed Lemmy via ansible, but I figured out that there are problems with emails and after I've created a user, no verification email came, no login is possible and now I have a ghost account I want to delete.

Because I couldn't find an UI element to purge users in the admin panel, I want to do it over postgresql, but I have no idea how to connect to the Lemmy database over a docker container, only thing I've found is to backup/restore the whole database:

docker-compose exec postgres pg_dumpall -c -U lemmy | gzip > lemmy_dump_date +%Y-%m-%d""%H%M_%S.sql.gz

Thank you for your help.

[–] utopify_org@lemmy.ml 1 points 1 year ago (2 children)

You just go directly to the user’s page, and from there you can do things like ban/delete/purge.

I've created a test account, but emails didn't work to verify and now I have an account I can't resend verification and there isn't a purge button.

How exactly do you purge a user?

 

Because of copyright laws in my country, I want to get rid of the option to upload images on my instance.

I thought it would be the fastest way to just remove the "upload image" icon from the tool bar. But it's harder than I thought, because I can't find it...

I've installed Lemmy with ansible and it runs with docker containers.

How can I get rid of this icon or even better, the function to upload an image?

I already tried to stop the pictr container, but this avoids uploading icons/banner for communites and thumbnails for new posts will not be generated, which is a no go.

I only want to get rid of the upload option while creating a new post.

Thanks a lot for your help :)

 

I am trying to figure out how people can subscribe to a Lemmy community or Lemmy thread?

It might be possible to see a community on Mastodon if you copy the link (example: https://lemmy.ml/c/lemmy_support) and paste it into the search field on Mastodon and then you can hit subscribe and even activate the bell for notification.

But nothing happens if I do that.

Can someone confirm that it usually works like that, but it may be a problem of my Mastodon instance?

Is it possible to subscribe to threads, too, e.g. like this one here I wrote (without being the creator of a thread)?

I would really like to go public with my Lemmy instance, but if this doesn't work, it's a no-go.

view more: next ›