Interesting. It shows up, but just as the shortcode:
@rimu@piefed.social - not sure what the json looks like coming from mitra, but at least in the short term it might make sense to just have piefed interpret emoji it doesn’t understand as an upvote (like it had been doing up to now) so that it doesn’t break the UI like this.
Thanks for tracking that down. It makes finding the issue and fixing it a lot easier. rimu will likely see this thread before I get a chance to sit down and work on it, but should have a fix soon probably. Sorry for the extraneous reports!
Let me see if I understand this issue correctly…
You are a lemmy instance admin. If a user from your instance is moderating a community, then any report in that community that is made by a piefed user is also forwarded to you. This happens even if the user being reported is not local to your instance.
You might not know the answer to this since it happens rarely, but does this happen for reports just in local communities, or also in remote communities that your user is a moderator for? So, if modA@slrpnk.net is a mod for commA@notslrpnk.net, do you still see the report if a piefed user makes a report in commA?
I have both a piefed and a lemmy instance I run for testing things, I can try to mess around with the different permutations for this one.
There’s no winning against Blaze.
This isn’t an error I have come across before, but it looks like there is some kind of error with activitypub signing of activities? I think that is what this block of the trace is saying:
File “/app/app/activitypub/routes.py”, line 613, in shared_inbox
LDSignature.verify_signature(request_json, actor.public_key)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/app/app/activitypub/signature.py”, line 485, in verify_signature
final_hash = cls.normalized_hash(options) + cls.normalized_hash(document)
~^^^^^^^^^^
File “/app/app/activitypub/signature.py”, line 544, in normalized_hash
norm_form = jsonld.normalize(
document,
{"algorithm": “URDNA2015”, “format": “application/n-quads"},
)
Your best bet to help troubleshoot is to hop on either the zulip chat (chat.piefed.social) or the matrix room to get support in realtime.
Visiting your instance, it looks like it is federating just fine, so I am not sure what the issue is.
As far as I know, this is the community where it happens so to speak. There is also !piefed_announcements@peertube.wtf where @rimu@piefed.social will post videos showcasing new features. However, not all features have need of a video.
because > doesn’t seem to work in selectors
I learned this the other day when I was trying to troubleshoot some css. It gets html-encoded so it doesn’t work anymore in the selector.
Like Blaze mentioned, it’s a whole different instance, running a different, experimental version of the code. It’s the instance we use for testing features for the next version of piefed.
If you want to make an account, feel free to register (I try to check registrations often). However, due to its testing nature, it might be a bit unstable and could not play nice with some mobile apps.
As the author of the codeberg issue for this, it hasn’t been added yet. I really liked the custom thumbnail feature when it was added to lemmy, so I haven’t forgotten about adding it to piefed. A big focus of my devwork recently has been on the api-side to help make apps/frontends more complete, so we will get there. I just added the issue to the 1.3 release kanban to make sure it is prioritized.
Ah, that would explain it. I guess it doesn’t really make sense to filter your own posts by read since they would pretty much all be marked as read. I can try to take a look at tweaking that.