Bug reports 🐞on🐛any🦠software🪲

147 readers

8 users here now

When a bug tracker is inside the exclusive walled-gardens of MS Github or Gitlab.com, and you cannot or will not enter, where do you file your bug report? Here, of course. This is a refuge where you can report bugs that are otherwise unreportable due to technical or ethical constraints.

⚠of course there are no guarantees it will be seen by anyone relevant. Hopefully some kind souls will volunteer to proxy the reports.

related communities in the decentralised free world:

!broken_software@lemmings.world

founded 4 years ago

MODERATORS

freedomPusher@sopuli.xyz

-3

Lemmy instance block feature has the perverse side-effect of a shitty Reddit-esque shadow ban on all DMs from users on that instance (like blackholing email). Yikes! (slrpnk.net)

submitted 5 months ago* (last edited 5 months ago) by activistPnk@slrpnk.net to c/bugs@sopuli.xyz

3 comments fedilink hide all child comments

In the user settings, I have several Cloudflare instances on my blocklist (e.g. Lemmy.World). When a user from one of those instances DMs me, the sender is falsely led to believe the msg was delivered and the recipient has no way of knowing. It has a nasty side effect comparable to shadow banning.

I have not actually tested this myself. I just know that I do not recall receiving a DM from a user on an instance that I block. But the linked comment is from @wolfyvegan@slrpnk.net who discovered the bug and tested this.

top 3 comments

sorted by: hot top controversial new old

[–] TrickDacy@lemmy.world 4 points 5 months ago

Closed as Won't Fix. Working as designed. User expectation is upside down.

[–] 7uWqKj@lemmy.world 3 points 5 months ago (1 children)

Isn’t that what blocking is supposed to be like?

[–] activistPnk@slrpnk.net -1 points 5 months ago* (last edited 5 months ago)

Not unless the devs are incompetent as TrickDacy. It’s inexcusable in any comms system to deceive senders about the delivery of their message. A block certainly does not imply: lie to senders about the transmission status. In the very least, the sender should be informed that their msg was not be delivered.

Do you think it’s smart for a mail server to accept email for delivery then silently blackhole it?

But beyond that, the meaning of a “block” on an “instance” is not defined to users. Block what? It is not blocking everything as it is. E.g. you will still see public posts from users of a blocked instance, just not their DMs. What justifies the inconsistency between pubic and private msgs particularly when it’s the opposite of intuition? If blocking one and not the other, it’d be more reasonable to block public msgs and not DMs.

And what justifies not properly informing users of the blocks what effect to expect?

Beyond failing to inform users, the control is not refined enough. I want to block Cloudflare clutter from my search results and timeline views, but not individuals -- and most particularly not individuals sending a DM. OTOH, there /would/ be a corner case benefit to blocking DMs from a whole instance, if a lot of harassing msgs come from multiple accounts on an instance. It should also be possible but only as a separate control.