I would recommend removing the piped.video integration completely for two reasons. Someone (I think maybe blaze@piefed.zip? who knows) said that naked YouTube URLs are better because phones can be set up to open directly in NewPipe. In fact that is how my phone is set up right now. Desktops can do the same with intents probably. Ease of maintenance burden.

What's new Media library that lets you upload images to comments/post body and paste from the clipboard Animated gif support for user profile pictures Specify alt-text for link posts that link to an image Emoji picker and spoiler button added to markdown toolbar More links to the modlog (footer, community sidebar, user profile) and improved searching/filtering Leave a conversation to remove it from the list of their direct message conversations Post urls are now "friendly" since they include the community name and a snippet of the title instead of just a number Add link to show parent comment when directly viewing a comment reply Image markdown style formatting to allow more advanced control of how images are rendered. e.g.  Code syntax highlighting in code blocks and allow for style selection in user settings Tag cloud added to sidebar for feeds and topics Better searching and filtering of the Instances list Add a block (of a user, community, instance or domain) from the blocks and filters management area, without doing it via a post Popup suggestions when mentioning a community or user as you type Onboarding plugin which auto-subscribes, auto-blocks and sends a welcome message for new accounts Improved federation efficiency Old posts can be automatically archived (saved to S3) to free up database space Old posts by bots with no comments are automatically deleted LLDAP support, which does LDAP a bit differently To upgrade To upgrade from 1.2.x: git pull git checkout v1.3.x ./deploy.sh or ./deploy-docker.sh In the past we had a separate project for realtime notifications, which is now unsupported as it's code has been merged with the main PieFed project. To set it up, refer to the Push Notifications section of install.md. As well as enhancing the user experience doing this will decrease load on your server if it hosts local communities with many subscribers as some of the federation work has been offloaded to the push notifications service. Donations PieFed is free and open-source software while operating without any advertising, monetization, or reliance on venture capital. Your donations are vital in supporting the PieFed development effort, allowing us to expand and enhance PieFed with new features. Donations can be made via Patreon, Liberapay or Ko-fi.

When the GUI editor is enabled there won't be a 'Insert image' button below the post, you can use the image icon. This one: [image: 49uAa4Gz6U3TZe4.png] Also, you can paste an image from your clipboard into the body field and it'll be automatically uploaded and the markdown for the image inserted into the field.

This post did not contain any content.

rimu@piefed.social for what it's worth, we had this discussion a decade ago too. We ended up being very simplistic and not tying anything to anything else. So posts are not tied to topics (theoretically you could have a post in multiple topics... we don't do that, but you can) And topics aren't tied to categories (same deal, and we also don't have topics in multiple categories... yet!!, cross-posting will change that. So when you have a direct url to a post it's just /post/. A friendly URL uses a post index, but we can do that because we order posts linearly. Piefed doesn't have that advantage unfortunately.

I'm looking to seeing this will bugger up Piefed <> NodeBB interop :laughing: Keep it up!

Also works with !communityname@whatever.tld for communities.

In general that's a good idea because you should never trust content coming from somewhere else (even in an S2S context) For reference, NodeBB literally sanitizes the bejeezus out of what it gets from anywhere. All classes are removed, all attributes are removed. I want it as close to semantic HTML as possible, and classes/attributes mean absolutely nothing because: I don't use the same CSS classes Attributes may not follow my own rules for when and where they are added. For example, Mastodon messes with any URL it federates out. It chops the anchor text in half, hides the rest behind invisible or something, and adds an ellipsis. invisible does something different in NodeBB, so there is a CSS conflict here. I strip everything and just show the URL as it was intended.

It took a few days for instances to be upgraded and admins to fill in their profiles but it's looking much healthier now! https://piefed.social/auth/instance_chooser

Discourse's Trust Levels are an interesting idea, but not one that is novel. It was lifted almost entirely from Stack Overflow. At the time, Discourse and Stack Overflow had a common founder, Jeff Atwood. There's a reason Stack Overflow is rapidly fading into obscurity... its moderation team (built off of trust levels) destroyed the very foundation of what made Stack Overflow good. I am also not saying that what we have now (first-mover moderation or top-down moderation granting) is better... merely that should you look into this, tread lightly.

On piefed.social I don't want to have much NSFW content to oversee because it's an extra moderation burden but there is plenty of it on other instances. If you go to https://piefed.social/auth/instance_chooser and then filter by ’NSFW content available’ you’ll see the instances that allow NSFW communities. Of those feddit.online has been around the longest and will have the deepest back catalogue but most of them will be fine for casual browsing. Before you make an account on a new instance, go to the_instance.tld/communities then into the advanced search and switch on NSFW to check how many NSFW communities have been federated to that instance.

I notice nobody responded to you... yes notifications work fine on PWAs. No additional apps required. NodeBB has supported them for a couple years, and Piefed can do so with some effort too. rimu@piefed.social happy to discuss how we did it — all standard web tools! I am not 100% sure there is iOS support, though. Supposedly there is, but we got some reports saying otherwise.