Other: pf for packet-filter; (yes, I seen the packetfilter tag)

You can flag (report) your own post with a request for it to be moved.

Better: it's not possible "to use" avif or webp formats? (much lighter)

@stefano@mastodon.bsd.cafe please, how can I delete the following post from Mastodon? https://mastodon.bsd.cafe/@grahamperrin@billboard.bsd.cafe/116475215991714222 The post above is already deleted in NodeBB. (I duplicated the title to the first line of the post, to work around the missing title issue, the result was duplication in Mastodon.) Thanks The subsequent post by me is OK, no duplication: https://mastodon.bsd.cafe/@grahamperrin@billboard.bsd.cafe/116475260834678599. This one should remain.

Make an issue

Similarly, with the Yeti skin I get missing texts in the Powered by area: [image: 1776614005911-5ecfb87a-4915-4555-9d1e-fc1c79f680e1-image.jpeg] Also with Yeti, https://billboard.bsd.cafe/unread failed to show the name of at least one category, OpenBSD. I wonder whether the issue will be reproducible with the default (no skin).

… my previous posts, they don’t seem to have had this problem. Here's another: [image: 1776611842047-9fa33bf5-3db8-440d-8319-ac4e051217ad-image.jpeg] When using glitch-soc at BSD Network to create and edit a post, it seems that Markdown and HTML options work only if the required content type is preselected when drafting and when editing. Examples: https://bsd.network/@grahamperrin/116432053054263857 https://bsd.network/@grahamperrin/116432064198716983 I assume that when an HTML post is incoming from something other than glitch-soc, glitch-soc defaults to plain text – without attempting to automatically detect HTML. glitch-soc/mastodon: A glitchy but lovable microblogging server issues …

https://mastodon.bsd.cafe/@grahamperrin/116360952509659346 a few minutes ago did address a category here in NodeBB, but has not yet appeared in the category: https://billboard.bsd.cafe/category/6/freebsd It is visible as a post at https://billboard.bsd.cafe/user/grahamperrin@mastodon.bsd.cafe/posts. A post, not a topic. Might this explain why it is not a topic in the category?

@stefano thanks s lot! ️

The problem here was auto-fill. The normal hint is automatically hidden by my real email address (pixelated in the screenshot below): [image: 1775270267359-6404e482-4e9b-4ed8-99ce-17d9e0b61814-image.jpeg] Keyword in the screenshot above: whatever. My email address is used for the Mastodon instance, but does not identify the instance. Whatever. After clearing the auto-fill, the hint is visible: [image: 1775270520828-85e70b11-6b73-4649-8a46-757476cfbf2c-image.jpeg] Eg username@mastodon.social The opening post is solved (tagged), I have flagged it for a move to the test area. Apologies for the noise.

I prefer new tabs for outgoing links: [image: 1775242252190-9a96606d-cd6e-4a85-96ed-bc24b2d09df4-image.jpeg] When I use the context menu at https://billboard.bsd.cafe/post/https%3A%2F%2Fsocial.linux.pizza%2Fusers%2Frestorante%2Fstatuses%2F116339353868717301 (for example) to open an original post, I'm taken away from Billboard in the same tab. This feels wrong. I can't find a matching open or closed issue at https://github.com/NodeBB/NodeBB/issues.

@pgeorgi Uhm no...it should also appear on the other instance

Ole Asteo / nodebb-plugin-shortcuts · GitLab If I understand correctly, the plugin will allow shortcuts such as Control-I and Control-B. Whilst I love the idea, you might want to hesitate before plugging things such as this into a nice new instance. See, for example, https://community.nodebb.org/post/96744 (2023) …

grahamperrin said: the horse or the otter … I guess that other random animals can appear at the Not Found screen.

Thanks. Maybe NodeBB defaults to strictness for new users, which would make sense. If so: leave it as is, I guess that I'll be able to edit the subject line there when I become a trusted user (I'm in no rush).

@carson@social.chittom.family great. Let me know if you find any problems!