Skip to content

Piero Bosio Social Web Site Personale Logo Fediverso

Social Forum federato con il resto del mondo. Non contano le istanze, contano le persone

Is there a way to quote post #Piefed posts from Mastodon yet?

Uncategorized
13 7 2

Gli ultimi otto messaggi ricevuti dalla Federazione
Post suggeriti
  • 0 Votes
    1 Posts
    1 Views
    I've made it so that when someone deletes their own post it is still viewable, including the comments. The post author and body will NOT be visible. Deleted posts will not show up in communities, search results, etc just as before - you need the URL of the post to get to it. Bookmark a deleted post within 7 days or it will be deleted for real. [image: 1olGBQ7vwolXKNa.png] Ask your instance admin to upgrade to v1.4.4. Chances are they'll be on 1.4.x already so this will be easy for them.
  • 0 Votes
    1 Posts
    0 Views
    This is our biggest release yet, including more finished tasks than any of our previous ones. Below is a summary of the highlights: What's new Posts & communities can be labelled as AI-generated and people can choose to hide all posts tagged that way. Very similar to how NSFW works. Comments can be marked as an Answer, like on StackOverflow. React to posts and comments with an emoji. Hide an individual post from yourself, without blocking the author. PieFed is now in the Yunohost app store, making initial setup easier. When banned from a remote instance you cannot make local-only posts in their communities. Honeypot to automatically IP ban badly-behaved crawlers. https://lemmy-federate.com integration, making PieFed communities get more exposure. "Share on Mastodon" menu item on posts. Vastly improve docs for new developers, see https://codeberg.org/rimu/pyfedi/src/branch/main/docs/developer_docs. Language selection is more visible during post creation. Tag clouds can also be viewed as a list of tags. View post/comment markdown. Bot accounts are not included in community statistics. Footnote support in markdown. Polish translation. Better HTTP caching, which reduces dependence on Cloudflare. Bugs Passkey fixes. Polls can now have up to 15 options. User profile performance improved. Don't allow bypassing minimum username length and post title with whitespace. Polls and Events can no longer be posted into Lemmy communities. API Additional user settings can be set through the api, including Extra Fields. Fetch url metadata. Sort comments by controversial. Comment search now works. Hashtags. Events. Polls. Emoji reactions on posts and comments. See https://piefed.social/c/piefed_api for more details. To upgrade To upgrade from 1.3.x: git pull git checkout v1.4.x ./deploy.sh or ./deploy-docker.sh There is a big database migration that will take a few minutes to run. How long will vary depending on how old your instance is - older instances will have more content to process. It took ~25 minutes on piefed.social so expect it to be less than that. 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.
  • 0 Votes
    4 Posts
    19 Views
    I'm looking to seeing this will bugger up Piefed <> NodeBB interop :laughing: Keep it up!
  • 0 Votes
    1 Posts
    21 Views
    At Piefed office hours, rimu@piefed.social and I got to talking about what's next for Piefed and the Threadiverse WG. One of those things is moving stuff between communities (or in bbs parlance: moving topics between categories/forums). Rimu suggested we use the already-existing as:Move activity, sent by the community (a group actor), with origin and target set, and with object being the post id itself. I suggested we update this to use the resolvable context collection as object instead, which Piefed has supported since v1.2. That should be enough to get a proof-of-concept implementation going between Piefed and NodeBB... a question remained as to whether this should be Announce(Move(Object)) or simply Move(Object). Argument for former was that it was similar verbiage to other 1b12 actions. Argument for the latter was that this is merely 1b12 adjacent and needn't follow prior art. We'll likely put together an FEP for this.