I’m calling this a #LemmyBug. When an address is copy-pasted into a msg, you have no indication of whether the other account was properly recognized and that they will get a notification. When I view source, it just shows the body of the msg not the JSON record.
I don’t do MS #Github (#deleteGithub). Or MS (anything) for that matter. I am 100% #GAFAM and #Cloudflare-free. I will generally report issues to #Debian’s bug tracker but that’s only an option for pkgs that are in Debian’s official repos. #Lemmy is not -- which in itself is a concern.
Debian requires packages to reach a certain quality standard. When a pkg becomes official Debian it suggests the package has enough popularity & quality to be taken seriously. Debian is quite popular¹ so Lemmy should try to put itself on the map. Until then I’ll have to file my bugs under the LemmyBug hashtag.
I’m calling this a #LemmyBug. When an address is copy-pasted into a msg, you have no indication of whether the other account was properly recognized and that they will get a notification. When I view source, it just shows the body of the msg not the JSON record.
That definitely sounds like a bug I would check if it exists on their GitHub and report it if it doesn't.
I don’t do MS #Github (#deleteGithub). Or MS (anything) for that matter. I am 100% #GAFAM and #Cloudflare-free. I will generally report issues to #Debian’s bug tracker but that’s only an option for pkgs that are in Debian’s official repos. #Lemmy is not -- which in itself is a concern.
Debian requires packages to reach a certain quality standard. When a pkg becomes official Debian it suggests the package has enough popularity & quality to be taken seriously. Debian is quite popular¹ so Lemmy should try to put itself on the map. Until then I’ll have to file my bugs under the LemmyBug hashtag.
1: https://has-no.solutions/objects/5891cf49-163d-491e-900a-6b5af92fa9a0