this post was submitted on 14 Sep 2024
-3 points (28.6% liked)

Bug reports on any software

116 readers
3 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.

founded 3 years ago
MODERATORS
 

Discuss. (But plz, it’s only interesting to hear from folks who have some healthy degree of contempt for exclusive corporate walled-gardens and the technofeudal system the fedi is designed to escape.)

And note that links can come into existence that are openly universally accessible and then later become part of a walled-garden... and then later be open again. For example, youtube. And a website can become jailed in Cloudflare but then be open again at the flip of a switch. So a good solution would be a toggle of sorts.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 1 month ago (1 children)

maybe instead of linking, just copy the content here. The link can still be there in addition to that. If its not pasteable then i dont know.

[–] [email protected] 1 points 1 month ago* (last edited 1 month ago)

It’s a decent approach but incomplete. Couple problems:

  • Lemmy would not host youtube videos. YT transcripts could (and should) be part of the post, but then there is the same problem as the next bullet:
  • w.r.t text content, some people (very few people) indeed copy the content. It’s failing because people are lazy. Too lazy to check whether the link is in a walled garden; too lazy to warn people of the walled garden; also too lazy to copy the text. Sometimes it’s more naivety than lazy, but same problem: you are relying on the masses to make individual decisions that are wise, inclusive, and higher effort.

A good system is designed with the assumption that users are lazy. As such, Lemmy is poorly designed.

1 lazy author can inconvenience thousands of readers. Lammy’s design fails to address that.