PriorProject @ PriorProject @lemmy.world

Just an explorer in the threadiverse.

---

Read more

Posts

9

Comments

266

Joined

2 yr. ago

Report it if you haven't already. I don't think there's a setting you can use to prevent it right now. If you feel passionate enough about it, you could file a GitHub issue for the Lemmy project highlighting that images in DMs can be used for undeletable harassment and stalking to identify IP addresses and geolocate individuals.

You want a finger? I can get you a finger, believe me. There are ways, Dude. You don't wanna know about it, believe me. I'll get you a finger by this afternoon--with nail polish.

It's a frequently requested feature, there's a GitHub issue for it in the Lemmy project, Mastodon does it so it's possible, but it's not available yet.

To my knowledge, the only paths are:

• Whack a mole with new titty communities, as you have been doing.
• Use Connect, which achieves this via client-side filtering. That is to say, it must still download the titty posts, but doesn't display them to you.
• Be a programmer and submit a PR to improve Lemmy, lemmy-web-ui, or the app of your choice to add this feature somehow.

It does not. I believe Connect is the only client with this feature, and it's done with client-side filtering. Connect still sees the posts from the instance, it just doesn't show them to you.

If there's nothing in the modlog, why do you think you were banned?

If you can't log in, try:

• Logging out explicitly if you have a logout button.
• Clearing your browser cache, or wiping app storage in android system settings.
• Try logging in again.

There are several occasions where mods had to wipe existing session tokens on the server, and this procedure helps recover if that's what's keeping you out.

Post in !moderators@lemmy.world. I'd expect to have to explain how you lost access to your previous account, and if it was banned to discuss why. If your previous account was banned by admins, it seems that they're unlikely to reinstate you as a mod.

I've used a combination of

• Managing ZFS snapshots with pyznap
• Plain old rsync to copy important files that happen not to be on ZFS filesystems to ZFS.

If I were doing this over today, I'd probably consider https://zrepl.github.io/ instead of pyznap, as pyznap is no longer receiving real active development.

In the past I've used rdiff-backup, which is great but it's hard to beat copy-on-write snapshots for speed and being lightweight.

My sense is that the front-runners were Schumacher (who Tost was pushing for based on the above ESPN article), Lawson/Hauger (who are the RB juniors closest to be ready for a callup), and Ricciardo who didn't want the seat last year. I feel like Nyck was a dark horse who shook up the order last year, but I don't think they really lost any options giving him a shot.

This is a good article but I really would like to see a fully open source app with a GPL, MIT, or similar license.

What is a "fully open source app" in this context? Does this not describe a headscale server with the tailscale android client?

• https://github.com/tailscale/tailscale-android/blob/main/LICENSE <- 3-clause BSD
• https://github.com/juanfont/headscale/blob/main/LICENSE <- 3-clause BSD

I mean, the mods are being chill about it so far. If they start dropping bans, the users trying to turn this into a support community won't actually be users anymore and they can go create asklemmyaboutsupportbutalsootherstuffwhatever and mod it themselves. In this respect, lemmy communities differ from language evolution.

For my part, I'm here for a discussion sub. I participate heavily in lemmy support communities, but that's not why I joined here.

Interesting, I feel like that active-users column is new in lemmy v0.18.x, I don't remember that being there and I didn't initially read your post clearly enough to understand that bit.

Here's my best-guess at what's going on. It's purely speculation, but speculation informed by study of how lemmy does other things in general and also by lots of exposure to system designs:

1. The subscriber count works as I described in my last post. It's a db query that fetches the count of local subscribers and is therefore... pretty much totally useless.
2. The active-user, post, and comment counts are calculated based on the local db state also. Now this generally SHOULD be useful. Posts and comments are supposed to be federated, and active user counts should be locally derivable simply from the posts and comments themselves. So these figures should generally match.

They obviously do not though, so what's the skinny?

1. For post and comment counts, lemmy.ml has post and comment history back to the beginning of time. Whereas lemmy.world and lemdroi.id are both relatively new servers. When the first user on an instance subscribes to a community, their server tells the instance's server "I want you to send me a copy of all new posts and comments going forward... also send me the most recent dozen or so just to get me started". There's no historical backfill. So you don't expect to see post and comment counts match. I guess that makes them useless.
2. For any server more than a month old, you SHOULD expect to see active-user counts match. Unless there's some rolling average that takes a few months to settle (which is possible). But if that's not what's up, then I think we're seeing side effects of broken replication: https://github.com/LemmyNet/lemmy/issues/3101. Perhaps lemdro.id is missing actual posts and comments and therefore cannot calculate the active-user counts accurately.

In any event, the workarounds are the same...

1. Browse communities on lemmyverse.net, not in the native community browser. It will give comparable activity numbers for communities on all servers.
2. Visit the home instance for each community, and only use the numbers there: https://lemmy.ml/c/asklemmy. That gives a third set of numbers that are bigger than any of the other two, and the most reliable. If the community's instance doesn't know about a post... it didn't get federated anywhere so it mostly really doesn't exist (except maybe on the instance of the user that posted it).

This is all kind of a wreck, I'm not trying to defend any of it. Just trying to explain why it might be that way. I have basically decided that the lemmy community browser is not useful except to look up a specific community and subscribe to it. Otherwise I always use lemmyverse or the community's instance to find info about it.

Why not just bookmark m.lemmy.world if that's how you want to browse? I'm not seeing what a server-side setting buys you?

Correct, when viewing a "remote" community (one that is hosted on an instance different from your account), you see subscriber number only for your local instance.

It's incredibly confusing to almost everyone, and has the effect that communities on big instances like Lemmy world end up growing faster than anything else because people literally can't figure out what the biggest community is and subscribe to the smaller local one thinking it's larger by mistake. And lemmy.world is big enough that if this goes on for a bit... it actually becomes the biggest community for a topic.

I recommend folks browse communities on lemmyverse.net (which uses accurate global activity rankings) and only use their instance community page to subscribe after they have found what they want.

I don't have an answer to your question, but out of curiosity why passbolt over vaultwarden (the non-commercial bitwarden backend)? It's the most common thing I hear about in this space, what makes you prefer passbolt?

The notifications counter gets confused sometimes and especially forgets to decrement when you mark a notification as read.

• In your browser, refresh the page. It will get normal again.
• In Jerboa, mark-all-as-read and the counter clears.
• Other clients may or may not have other workarounds, the most severe of which is killing and restarting them which should generally force a reread of the current notification count.

It's a bug I'm sure they'll work out at some point, but for now it is what it is and you just have to live with the irritation as far as I know.

Awesome feature. It's great to see you thoughtfully trying to balance the community discovery problem with the federation overhead caused by mass subscription.

While I continue to favor and recommend manual subscription, I've bookmarked lsb and lcs to recommend to folks looking for automated approaches. I think they're looking pretty good right now and seeing you proactively address feedback gives me faith that they'll get even better.

Lol, upvoted. Good luck to you Don Quixote, I can think of nothing that can go wrong with this plan whatsoever.

Check out https://lemmy.world/post/1375042. Yesterday login status was wild, but it seems to be settled today after logging out and logging back in to all my clients.

Is there any way to see the true subscriber count of a community while logged in?

1. Browse lemmyverse.net instead of your instance's community browser. The former will show apples to apples activity stats across instances.
2. When looking at a remote community from your Instance browser, visit the community on its home instance to see the global subscriber count.
3. Go on GitHub and emoji react to https://github.com/LemmyNet/lemmy/issues/3464 to show your support for this feature, or try to actually fix it. I don't see core devs working on much other than performance and moderation tools for a while, as these are both existential gaps given current growth rates. Quality of life features like community discovery (which are extremely important to users) are likely to take a back seat to these.

It would have to be client-side filtering. Just fetching and then not displaying affected posts and comments.