Caused by the same db issue thats been causing issues
Its been getting looked at and we have some more people that are being added on to help out as well
Issue should be fixed, messed around with the db a bit and seems to work now
Started using certbot-dns-cloudflare to generate the certificate
Were currently just using base lemmy since pangora isn't done so not sure why we would be different from other instances. I can try to look into it
Update: I haven't been able to replicate jshelter showing high. I'm thinking though it might be something about lemmy 0.18.5 vs 0.18.4 since we're on 0.18.4 still. Lemmy.ml is on 0.18.5
Update #2: Was able to replicate it from a computer restart. Could not replicate it on other lemmy 0.18.4 instances
I tried messaging an account I though was running it when your bots posted something to elixir but I can repost it here
Just wanted to let you know that we dont allow reposting of comments made on other platforms (both for spam reasons and tends to be a mess with gdpr). Link posts with no text are fine as long as you get approval from a moderator of a community or by one of the admins for site wide usage (and then allow moderators to opt out), and follow our bot guidelines that you can find in the sidebar on our site. Id be willing to greenlight the bot for sitewide usage as long as you remove the comments, make posts links only (links to the content, not the reddit post) and limit it to maximum 10 posts a day across the instance (max 2 in a specific community) (and also make sure you dont repost stuff already posted in the community). We have another bot called reddit x-poster that its been working fairly well with but they hang out in a couple communities like haskell
We do have a soft fork for the instance getting built up to add features on top of lemmy
Pangora is soft forked so we get changes pulled from lemmy and add new features we need for the site onto their changes (that can then push to go upstream or have for ourselves if they don't want that feature)
Pangora-UI is built from scratch to replace lemmy-ui as a frontend for the site
In the settings all languages are allowed due to issues with language federation from mastodon and kbin. Its up to the mods what languages they allow. (Majority will be English but allows for some communities that are two if theres some technology where official info is given in another language or for things like c/programming but in another language (naturally hidden from people who don't have that set as their language))
I deleted that german post since its just a stream ad
This was a cross post rather than a direct post to the community so it acts the same as if its posted on two different communities here like a lemmy cross post (with different threads based on the community the post is on)
If someone on mastodon commented on this version of the thread their comment would show up here
true moving posts could be something that could be done if lemmy is set to deal with that. I can check to see how difficult that would be to put into lemmy and possibly push a patch out.
If we get that functionality in we can do another poll to determine whether it should switch to that but for now im just polling these options since I assume it wont be a thing for a bit (I tried to push another patch out to the site to make the request community more prominent but it seemed to be having issues with certain aspects of the changes so that needs to be fixed before we can get some updates out)
Ill switch all the icons according to what gets voted on. Will leave voting open for a day
Ategon
0 post score0 comment score
Sites back, communities that previously had their community page not vieweable are now viewable
An example of this is https://programming.dev/c/a11y
Basically what I did was before the maintenance exported every single post in the post table and use a js script to check for duplicate ap_ids (checking using sql itself didnt work due to broken indices so it was always missing some). Then I generated sql statements to remove duplicate posts that had higher ids than the other posts theyre a duplicate of. Ran all those during maintenance and since all duplicate ap_ids were removed I could now reindex the table to fix the broken indices
Did the same for communities after the posts (but also did some statements to move posts from one version of the community to the other)
Site might be slow for a tiny bit as it processes the 2 hour of activities that were generated while it was down