Nothing4You

so just dropping duplicates then?

are there no references to the duplicates from posts? if there are and the duplicate rows are just deleted it’ll cascade deletion and purge all those posts from the db as well

how are you planning to fix this?

delegating authentication to another service.

one of the more commonly known options would be sign in with google, but this is also quite useful for providers hosting multiple services. a provider could host a service that handles authentication and then you only have to login once and will automatically get logged in for their lemmy, xmpp, wiki and other services they might be providing.

do you happen to have experience with setting up influxdb and telegraf? or maybe something else that might be better suited?

the metrics are currently in prometheus metrics format and scraped every 5 minutes.

my idea was to keep the current retention for most metrics and have longer retention (possibly with lower granularity for data older than a month).

the current prometheus setup is super simple, you can see (and older copy of) the config here.

if you want to build a configuration for influxdb/telegraf that i can more or less just drop in there without too many adjustments that would certainly be welcomed.

the metric that would need longer retention is lemmy_federation_state_last_successful_id_local.

I’ll probably have to look at another storage than prometheus, aiui it’s not really well suited for this task.

maybe something with influxdb+telegraf, although i haven’t looked at that yet.

this feels like more db index corruption that already existed for users previously, unlikely to be an issue in lemmy itself

you may want to redact the names as this spam is framing another person pretending to be originating from them

so all you’re looking for is the amount of activities generated per instance?

that is only a small subset of the data currently collected, most of the storage use currently comes from collecting information in relation to other instances.

Hi, I run this.

What benefit do you expect from longer retention periods and how much time did you have in mind?

The way data is currently collected and stored keeps the same granularity for the entire time period, which currently uses around 60 GiB for a month of retention across all monitored instances.

see https://programming.dev/post/20167648 and https://programming.dev/post/20201619, this was an issue with p.d infrastructure

verification emails are usually sent immediately. if there are delays you should check your junk folder, and if it’s not there it probably won’t arrive anymore. depending on the instance you signed up on there may be alternative methods to reach out to the instance admins about this. note that private messages from mastodon to lemmy do not work unfortunately.

you may have broken your language settings? check in your account settings. the posts are all tagged as English, you’ll want to have at least English and undefined languages selected

fwiw, for Sync users the update to 0.19.5 is not that great, as @[email protected] still hasn’t updated Sync to use the updated APIs for marking posts as read :(

also adding my vote for the second one

lemmy updates did some improvements on the receiving side, parallel sending on the sending side is not yet part of a new release. it’ll also likely take some time for that to be deployed on lemmy.world to have those changes be tested by other production instances first. my activitypub-federation-queue-batcher is currently used by at least 2 other high latency instances and would address the issue at the cost of a small (like 3 bucks or so) vps in Europe and some time investment for the setup.

this is only for setting the default user language during registration based on the browsers accept language headers.

this is likely related to https://github.com/LemmyNet/lemmy/issues/4971

this isn’t true. it was incorrectly stated in the upgrade guide but has been removed a while ago. it was supposed to be a recommendation due to some issues with postgres 15. there is no postgres upgrade required between 0.19 releases.

account names cannot be changed.

you can only change your display name, which is available in the settings.

whether display names or usernames are shown depends on the interface/client and user settings where available.

the only way to change the username is to create a new account.

it seems to have become more frequent recently.

i’ve been experiencing the same on firefox and i’ve also heard other people report the same on firefox, which happened around the time of the firefox 129 release. i didn’t see anything noteworthy in the release notes though that’d explain this. it seems like it might be related to enhanced tracking protection and cookie isolation.