[-] [email protected] 3 points 1 day ago

is that sync? sync has some issues with local communities. I think it might get better if you subscribe to the community.

compare with the web version to rule out account related issues.

[-] [email protected] 2 points 3 days ago* (last edited 3 days ago)

normalerweise werden keine frames eingebunden, nur bei video embeds meine ich

[-] [email protected] 4 points 6 days ago

deleted the database

this is generally something you should avoid doing with activitypub software, as there is no clearly defined way to deal with changed private keys and it is handled differently depending on the software. with lemmy it should more or less resolve itself after some time, as instances will refresh public keys from time to time. after a few days of being alive again and having activities federate out it that part should start working properly again.

Subscription Pending Issue

check if your instance is considered dead, it may take sending some activities (e.g. subscribing, posting, commenting) and a bit of waiting to get your instance considered reachable again. you can use https://phiresky.github.io/lemmy-federation-state/site to check the instance you're expecting data from and look for where your instance is listed.

Old Content Persisting

as @[email protected] already mentioned, all you did was disappear. how would anyone know that your intention was to delete data?

while you can't force other instances to respect your deletion requests, it would still be possible to ask them for it, but this is not an easy task once they're no longer in your database. the most effective/efficient way to do this would probably to first get your overall federation fixed/not considered dead anymore, then delete the account using the same name, and never use the username again on the same domain in the future, as deletions are more pretty much irreversible and depending on the software on the other side may permanently block the username from being used, even if you change this in your database. another option could be creating posts/comments with matching ids in the database and then deleting them via api, but this is also rather fiddly and a lot easier to fuck things up with. i don't recommend editing the db directly without good understanding of lemmy's internals.

Old Replies Resurfacing

Lemmy uses numeric incremental ids for posts and comments, so when you started with a fresh database these ids are getting reused. this will break your posts and comments from properly federating to instances that have seen them with the same id before.

the easiest and lowest tech solution to deal with this would be to simply move to a different domain/subdomain for a proper new instance experience. alternatively you could consider adjusting the sequences in the database used for new post, comment and pm ids, to ensure that they are higher than any number your instance may have previously seen. as they are incremented not only by local content, but also by content retrieved via federation, these numbers will be significantly higher than the amount of content you had posted in the past, but it will be hit or miss whether they will overlap with ids that were for old local content.

based on counts from lemmy.ml and lemmy.world, it seems that a post sequence starting at 55m is likely safe to use, 20m for comments. pm ids are not publicly visible, but unless you sent or received many in the past, something like 1k or 10k are probably still safe bets. this is a db modification that you will need for sure if you want to minimize federation issues while using the same domain.

looking at your instance i'm not sure if this is what you mean by replies resurfacing, as i don't see any replies by remote users on your comments, but what i described is otherwise going to cause issues randomly in the future if you happen to hit a previously locally used id on a new local post/comment.

[-] [email protected] 16 points 1 week ago

nothing about this is cherry-picking. it's simply how lemmy works. there are no remote js sources. lemmy-ui even sets security headers that prevent loading js from third party domains.

[-] [email protected] 19 points 1 week ago* (last edited 1 week ago)

doesn't require allowing javascript of a million other servers?

half the images are broken because I’m expected to allow scripts on like 30+ sites to see most of the posts

software like noscript is not exactly beginner friendly. you're expected to understand the impact of your blocking and what you are blocking. the only domain you need to allow JS from on lemmy.world is lemmy.world. standard lemmy-ui does not load any js or css from third party sources, only the domain where lemmy-ui is served. your noscript configuration is blocking the actual images, not javascript that would be required to load images.

edit:

to expand on this, even in tor browser in safest mode, lemmy.world works totally fine when all you do is allow JS from lemmy.world on lemmy.world:

[-] [email protected] 19 points 2 weeks ago

you can simply check your profile and modlog on the instance in question. it'll show that you got banned from that instance 8 days ago. since you didn't participate in any community on that instance there were no community bans federated out. instance bans currently don't federate, only community bans for communities on the instance you got banned from, if you have previously participated in them.

[-] [email protected] 17 points 4 months ago

based on the creation date advertised by the instance, lemmy.ml exists since 2019-04-20. lemmy.world exists since 2023-06-01.

[-] [email protected] 23 points 6 months ago

it's not just lemmy.world.

of the larger instances, the following have trouble sending activities to lemm.ee currently:

  • lemmynsfw.com -> lemm.ee: 2.81d behind
  • sh.itjust.works -> lemm.ee: 1.04d behind
  • lemmy.world -> lemm.ee: 22.5h behind

i pinged @[email protected] on matrix about 30h ago already about the issues with federation from lemmynsfw.com, as it was the first one i noticed, but I haven't heard back yet.

[-] [email protected] 25 points 7 months ago

I think most (especially mobile) clients simply don't have this option and will always copy/share the "fedi link" - the url where the content is canonically hosted. all other URLs are simply cached representations of the original content.

[-] [email protected] 25 points 7 months ago

https://lemmy.blahaj.zone/instances shows lemmygrad as blocked, maybe there are some older communities that were never removed on blahaj after defederation?

[-] [email protected] 25 points 10 months ago

cleaning up communities doesn't make lemmy more active either. it may help to make active communities stand out more against inactive ones though.

[-] [email protected] 45 points 10 months ago
if you want to get fancy
you can even use undocumented tables
view more: next ›

Nothing4You

0 post score
0 comment score
joined 1 year ago