PieFed 1.5 is released - move posts, upload video files, better chat and more
codeberg.org/rimu/pyfedi/releases/tag/v1.5.0
cross-posted from: https://piefed.social/c/piefed_meta/p/1653370/piefed-1-5-is-released-move-posts-upload-video-files-better-chat-and-more
Big deals, omg
- Mods can move a post, with replies and votes, to another community. The change federates to other instances (except Lemmy, for now. I've been in discussion with devs from NodeBB and Lemmy about how this will work, they are on board).
- Upload video files while creating a video post - no external host needed. Admin setting to limit who can do this (to save space).
- Realtime chat - conversation immediately updates on screen when a new PM arrives.
More good stuff
- Author-deleted posts are still visible to them and anyone with the url. No more loss of high-value comments with the OP deletes.
- Search filters - nsfw and minimum post score
- Improve speed of cross-posting form on mobile
- Emoji tokens like
:blush:can be used in post or comment body. No GUI support yet. - Admin setting to disable local copies of remote images - good for single-user instances
- Replying to a comment marks associated inbox item as read
- Updated HPT-Fruits theme
- 196 no longer excluded from default community import
- Remove unused community rating feature
- Remove unused instance vote weight feature
- Remove ineffective þ to 'th' replacement
- Improved accessibility - better contrast, fixed many incorrectly-used
aria-labels - Updated translations - Basque, Chinese, Japanese
API:
- Admins can ban/unban users through the API. piefed.world was maintaining custom code for this, hopefully it'll make their version upgrades faster.
Bugs fixed
- PMs
- Markdown parsing
- Speed up loading of profile pages for admin users
- Friendica post parsing
- Passkeys login UX tweak
To upgrade
To upgrade from 1.4.x:
git pull
git checkout v1.5.x
./deploy.sh or ./deploy-docker.sh
24 Comments
Comments from other communities
This release is a bit smaller than usual but also only 2 weeks since 1.4. I'm planning on doing smaller, more frequent and more focussed releases in future.
Seems like a pretty big update to me as a video creator 🫡
Yes, that's the idea.
On piefed.social I've got that set so that only I can upload videos and I'll use that for when I do demos of new features. I really don't want to pay to store other people's videos forever, and I expect most PieFed instances will be the same.
I expect this will mostly be used by people running an instance for themselves or a few friends.
Sorry if this is in the docs and I just missed it, but would I run into any problems upgrading straight to v1.5.x from v1.2.x? Or should I do a checkout and ./deploy-docker.sh for each minor version?
@rimu@piefed.social is there any documentation about the move post feature? It has existed in the mod panel on mbin for as long as it exists, but it does not federate and it would be great if we could implement it in a way that is working piefed, lemmy and nodebb
I just did a quick test-move and here is the json that was federated out:
json
{
"actor": "https://crust.piefed.social/u/wjs018",
"cc": [
"https://piefed.wjs018.xyz/c/testing"
],
"id": "https://crust.piefed.social/activities/move/l7NaOQha12PQyYv",
"object": "https://crust.piefed.social/c/testing/p/108274/this-post-will-be-moved",
"origin": "https://piefed.wjs018.xyz/c/testing",
"target": "https://crust.piefed.social/c/test",
"to": [
"https://www.w3.org/ns/activitystreams#Public"
],
"type": "Move"
}
For context, this was moved from !testing@piefed.wjs018.xyz to !test@crust.piefed.social. The author, @wjs018@crust.piefed.social, is a moderator of the community that the post was initially posted to. I did find a bug in this process, the post flair, which should be community-specific, was moved as well when it should have been stripped. So, I created an issue for tracking that fix.
thanks for the quick response. I added it to our issue tracking the federation of mod actions (mbinOrg/mbin/#248)
This is awesome, thanks
@bentigorlich@gehirneimer.de I've been tagging you and @melroy@kbin.melroy.org about this but maybe there's a federation issue? Hopefully not.
Anyway the FEP is there, and I'd love to loop you two in to the discussions.
Hi there. At least this one got through, but I did noz get a notification about other posts I think
being able to move posts is huge!
It's one of those missing pieces that we've missed for so long that no one ever bought it up - that was just how it was. Then in Nov of last year Julian from NodeBB initiated a conversation between NodeBB, Lemmy and PieFed and here we are. I got there first but hopefully the others are not far behind.
We were just talking about how to consolidate communities and it's really annoying not being able to move posts lol
A merge community function.... ooo
Yes, let's talk about how that would work.
It has much to do with my cross-posting FEP which I have... not written. It is largely in my head at the moment 😢
Can Piefed see my emoji now? 😬
I guess, either:
Issue multiple Move activities, until all the posts are gone from one community then delete the empty one.
A special Merge activity that looks basically the same as the Move one (target and origin) except the things being targeted and originated are communities instead of posts.
I see your emoji!
Can you see THIS emoji? :attention1:
I typed it as : attention1 : in the markdown (no spaces tho) and PieFed converted it to an image. That emoji was originally published by literature.cafe, a Lemmy instance, but I can use it here anyway.
@rimu@piefed.social oh... No I cannot 😔 but we shall figure it out!
Edit: ah you're missing a tag entry with type Emoji. Check out the AP data on my reply to see it.
In the rendered HTML you actually don't render the image, it usually gets stripped for safety
Amazing work thanks.
Is the ability to crosspost text posts on the priority list for coming releases?
https://codeberg.org/rimu/pyfedi/issues/996
Yes, although it's a long list...
Fantastic - you are so incredibly dedicated!!
One suggestion: for posterity add to "No more loss of high-value comments with the OP deletes." the constraint that the post must remain bookmarked by someone or else it will get deleted (it is not automatic otherwise).
Author-deleted posts are still visible to them and anyone with the url. No more loss of high-value comments with the OP deletes.
I feel that this violates the privacy of the users and their rights over their content. I know that posting on the internet makes it to be there forever, but still it should be an option to permanently delete a post. I suppose a user can still modify a post to delete its content.
Yes I understand that concern.
To clarify a bit - when someone deletes their post, who authored it is no longer visible and the body of the post is no longer visible. Only the title remains, and the comments on the post.
That should remove all visible association between the author and the post and any accidental self-doxing, etc would tend to be in the body, which will no longer be visible.
Admins and mods can still see the author of the deleted post (so bad people can't escape scrutiny).
Ok, that is more clear, maybe you should add that to the description because with the current way it's written it seems as if the whole post and author are still visible to anyone with the link.
Mods can move a post, with replies and votes, to another community. The change federates to other instances (except Lemmy, for now[...]
Sounds awesome! One question, until Lemmy properly supports this, how will it look on the Lemmy side when a post is moved? Will it still be visible in the original community, in both the old and new communities, or will the post just disappear?
It'll disappear from the old community and appear in the new one, with all the same comments and votes as before. On all instances.
Ah, okay. That's great. Might be a dumb question, but what did you mean by "change federates to other instances (except Lemmy[...]" then?
Sorry I misread your earlier question, missing out the "until Lemmy supports...".
From Lemmy's side it'll look like the post is still in the old community.
Is the feature to move posts from MBin instances supported?
My understanding is that the mbin move feature doesn't federate out at the moment, but I wouldn't be surprised if it happens soon as there are more platforms that support it.
As a new lemmy user whats the killer features I'm missing out on by not being on Piefed? curious
https://join.piefed.social/features
Scroll down to the Differences between Lemmy and PieFed section.
There is something about this link structure that is not getting translated to allow me to see the referenced post on PieFed.social.
@sxan@midwest.social you are unstoppable lmao
What was this "þ to 'th' replacement" movement supposed to accomplish? Prevent LLM-feeding scraping from producing anything useful?
And what does the change log entry mean practically? People who type þ will have their input changed to "th" before posting?
It means that it used to be replaced when viewing a comment with a thorn on PieFed. The comment still contains a thorn in the database. With the update, it is no longer replaced.
For example, here is this post from a PieFed instance that is still on v1.4.0, which just shows th everywhere. On the other hand, here is this post from a PieFed instance running the v1.5.0 update, showing the thorn.
Okay cool, thanks. So then that begs the question, in what way was this replacement ineffective?
There must be an Icelandic community that complained about suddenly seeing English letters in their text https://codeberg.org/rimu/pyfedi/issues/1559
That makes sense!
The user in question just switched to a different unicode character that looks pretty much identical to the thorn symbol. AFAIK, we didn't actually get any complaints from Icelanders, but we weren't happy with the implementation due to its potential impact on that community. At the end of the day, we decided that this is a user problem where bans and blocks should be used instead of putting something explicitly in the code.
what problem?
Icelandic þ is pronounced like th as in thorn, so I guess it was just for ease of reading, but maybe there weren't any Icelandic on piefed so they removed the automatic change
If I'm not mistaken thorn (the character) was historically used in England as well, but was replaced with "th" to make things easier for Gutenberg and his followers.
Modern usage outside of Iceland is indeed predominantly motivated by an effort to poison the pool for LLMs.
This is the correct answer. Some people wanted to try making the
þshow up in future LLM answers.Huh. All that work, just for little ol' me? Gosh, I'm humbled. I didn't even know that was going on.
I do try to limit thorn to my piefed account. Sometimes habit tricks me to using it on Midwest.Social, but that's entirely accidental.
Oh that explains a lot, I was surprised to see @midwest.social pop up when I tried to @ you lol.
I also didn’t know it was going on until seeing this changelog but it sure made me laugh
Sxan is being the change he wants to see in the world
The only things keeping me off PieFed is support for seeing my upvoted stuff on Voyager and for Alexandrite to support it.
I can see my upvotes on Mlem. So it’s definitely there. And fast.
I have tried mlem quite a few times but can never get into it because I want its large post view without description text, and I want some more font and color options, I find the defaults too jarring. Unfortunately else feels wrong after Voyager.
Also I just looked and it doesn't appear to have it either. I can't even find it for Lemmy accounts. I want a page that displays all posts and comments that I have upvoted.
Isn't Alexandrite abandoned? https://github.com/sheodox/alexandrite
I don't see anything there that would indicate so ..??
No commit since 11 months?
Okay but it works perfectly still. The only thing it needs is PieFed support.
Lemmy 1.0 will be released at some point, and none of the new features will be supported.
Then we will see. It's still the best front end around.