PieFed Meta

Title. Can't figure out how to crosspost anything in Piefed.

tl;dr - Please only upvote this post if you want Summit to support PieFed.

I was supposed to start doing these starting from v1.64.0, but I forgot so apologizes.

I will start creating one of these posts per major release to gauge interest in PieFed. Y'all have until the next major release to vote. If any of these posts reach 200 upvotes before the poll for the next release I will make the next release focused on adding PieFed support.

Thank you.

A way for people to screen out AI generated content, similar how people can screen out nsfw content already.

It works the same as the nsfw filter except underneath it's an integer instead of a Boolean.

Content authors will flag their content as AI-generated, on a sliding scale from 0 (no AI) to 100 (completely AI generated. Intermediate values could be used too although this amount of nuance may be confusing for some.

Users will be able to set a "AI generated threshold" which filters out content above that threshold. At the UI level this could be presented as a checkbox but maybe a slider would be good.

Mods need to be able to set the AI level on content, as they do now with NSFW content.

Communities will have an AI-gen value too, which is automatically applied to all content within. Instance admins can override this value too, for local or remote communities.

Thoughts?

Votes are no longer using an alt profile so instead you now have the choice of federating your votes or not. Please go to https://piefed.social/user/settings and see the 'Federate votes' checkbox. It should be showing the opposite of what you had for the 'Vote privately' checkbox that was there before, however the behavior and tradeoffs are really quite different so you might want to revisit that decision.

Whatever you choose there, you can still override that on a case-by-case basis by holding down your mouse button on the voting controls ("long press" on a touch device) of a post/comment.

If this is all news to you, please see https://piefed.social/post/979325 and https://piefed.social/post/956572

Due to difficulties making private voting a viable reality , we've been playing around with an alternative approach: public/private votes becomes "federated votes" where you can choose whether to send your vote off to other instances or whether it only counts locally and doesn't get federated.

There are obvious drawbacks to casting a vote that doesn't federate. But this avoids all the issues with which instances to trust (and who decides that) and avoids the distrust generated by all these sockpuppets with weird names running around and the need to explain in difficult technical detail why we're doing that, no it's not vote manipulation, don't ban / defederate us, etc etc

The video shows how the user interface could work. Basically there is a setting in your profile that determines whether your votes federate and an optional override you can use on a case-by-case basis.

There is an assumption here that people will generally choose one mode (public or private) and stick with that for most of their votes. The popup will only be used rarely so the extra clicks and the waiting involved won't be much of an issue.

Thoughts?

cross-posted from: https://vger.social/post/20512447

I'm excited to announce that Voyager now has experimental support for logging in with Piefed! You can try it out today on:

• iOS Testflight
• Android Play Open Testing
• beta.vger.app

This will roll out to the official app stores and vger.app soon(tm), once I’m confident there are no major regressions. If you prefer not to switch to beta builds, just hang tight.

Please note that Piefed support is EXPERIMENTAL! There are still many things that don't work quite right, which I'm hoping to improve over the coming weeks.

The basics including scrolling home/all/local, viewing posts, blocking, commenting and voting should work well. However there are some known issues:

• Can't sign up for a Piefed account in-app, only log in with an existing one
• Subscribed communities list is empty (should be fixed soon!)
• Inbox tab doesn't load
• Comment search doesn't work
• Profile upvoted/downvoted doesn't load
• No moderation tools
• Mark as read doesn't persist
• Creating/editing posts is currently untested
• ...probably a bunch of other stuff too, please let me know below!

Behind the scenes, this interoperability is made possible thanks to aeharding/threadiverse, a new library I am working on to normalize various threadiverse-software APIs. It's open source so any project use it, but it's under heavy development right now. What's cool about this is in the future, adding support for mbin, or whatever else is possible!

Again, feel free to try it out and let me know if there are any more issues to be documented and fixed.

Is it possible to add such a theme, or is it doable by adding some css to the additional css option in settings? for comparison lemmy web ui shows images, links, and text posts without any associated image in a consistent fashion

i know i could use the super compact option but that doesn't show any images at all

tia for any advice

See the install instructions to get the latest release. Switch to the "v1.0.x" git branch to run this release rather than the latest code.

Existing instances:

git pull  
git checkout v1.0.0  
./deploy.sh or ./deploy-docker.sh  

PieFed usage has been growing very fast lately, with many communities moving to piefed.social from lemm.ee and several new instances such as piefed.ca, piefed.blahaj.zone, and more .

With this increased attention a light has been shone on many previously ignored parts of PieFed so we've been hard at work closing the gaps and incorporating new ideas from new people. Also it has become necessary to begin doing proper releases so instances have a more stable place to park themselves without being exposed to the constant turmoil that comes from running bleeding-edge code in production.

Due to feedback from a wider audience than before, some of the idiosyncratic features that I built because of my personal obsessions have been made optional and OFF by default, such as the 4chan meme filter, meme communities being flagged as 'low quality' and so on. Private voting has fundamental issues and could be removed soon, I'll make a separate post about that.

The API is now in use and the mobile app Interstellar works with it well. Other apps are working on PieFed compatibility too. Again a lot of work went in there to get it ready for prime time.

To sum up - leading up to this release the last few weeks have showed intensive development with major focus on performance optimization, UI/UX improvements and enhanced federation capabilities. We made significant progress on API development, moderation tools, and overall platform stability.

Below is an incomplete list of some things we've worked on in June. Sorry to those whose work I overlooked, it's been a deluge.

rimu (178+ commits)

• Performance Optimizations:
  • Fixed slow API comment/list endpoint (https://codeberg.org/rimu/pyfedi/issues/883)
  • Added community total_subscriptions_count column (https://codeberg.org/rimu/pyfedi/issues/881)
  • Optimized API user sorting (https://codeberg.org/rimu/pyfedi/issues/880)
  • Performance improvements for community sorting (https://codeberg.org/rimu/pyfedi/issues/879)
  • Home page performance improvements - reduce reliance on redis and optimize jinja templates
  • CORS
• Security & Bug Fixes:
  • Fixed find_instance_id bug
  • Added CSRF token protection on various forms
  • Fixed user reputation update DB deadlocks (https://codeberg.org/rimu/pyfedi/issues/752)
• UI/UX Improvements:
  • Bootstrap 5 upgrade (https://codeberg.org/rimu/pyfedi/issues/810)
  • Mega menu implementation - merge Topics and Feeds into one huge "Communities" menu
  • Theme updates and CSS improvements
  • Add your own CSS to PieFed - https://piefed.social/c/piefed_css
  • Import latest language updates from translation team
  • Markdown-based CMS so admins can create static pages
  • Make https://piefed.social/rules using CMS
• Admin Tools: Database migration fixes, config checking, various admin panel enhancements

freamon (45+ commits)

• API Development:
  • Implemented resolve_object endpoint for generic object resolution (https://codeberg.org/rimu/pyfedi/issues/729)
  • Added API rate limiting and verification endpoints
  • Enhanced API comment/list performance work (https://codeberg.org/rimu/pyfedi/issues/883)
  • resolve_object API functionality (https://codeberg.org/rimu/pyfedi/issues/729)
  • Lots to do with moderators in the API
• Federation Improvements:
  • Fixed community federation issues
  • Enhanced mod management via API (https://codeberg.org/rimu/pyfedi/issues/814)
  • Improved ActivityPub compatibility
  • Federate community bans and user blocks
• Database & Infrastructure:
  • Fixed initial DB setup issues (https://codeberg.org/rimu/pyfedi/issues/862)
  • Improved migration handling
  • Enhanced query performance
• Project coordination and pull request reviews

wjs018 (25+ commits)

• User Interface Enhancements:
  • Blocking/unblocking disambiguation for local vs remote users (https://codeberg.org/rimu/pyfedi/pulls/892)
  • Added seamless bookmark management with HTMX (https://codeberg.org/rimu/pyfedi/pulls/864)
  • Community page redesign and sidebar improvements (https://codeberg.org/rimu/pyfedi/pulls/806)
  • Added domains to posts in feeds (https://codeberg.org/rimu/pyfedi/pulls/807)
  • Communities page redesign
• Content Features:
  • Implemented spoiler flair with image blurring (https://codeberg.org/rimu/pyfedi/pulls/759)
  • Better blockquote and code block styling (https://codeberg.org/rimu/pyfedi/pulls/818)
  • Inline spoiler text support (https://codeberg.org/rimu/pyfedi/pulls/788)
  • Text blurring in post previews
• Admin Features:
  • Community creation restrictions for admins (https://codeberg.org/rimu/pyfedi/pulls/816)
  • Additional admin settings panel (https://codeberg.org/rimu/pyfedi/pulls/797)
  • Low quality community filtering (https://codeberg.org/rimu/pyfedi/pulls/820)
  • Do not automatically add piefed.social to trusted instances

JollyDevelopment (8 commits)

• Moderation Tools: Find and ban user feature for community moderation (https://codeberg.org/rimu/pyfedi/issues/857)
• Feed Management:
  • Fixed feed auto-follow functionality (https://codeberg.org/rimu/pyfedi/issues/856)
  • Feed icon upload fixes (https://codeberg.org/rimu/pyfedi/issues/829)
  • Enhanced feed link handling (https://codeberg.org/rimu/pyfedi/pulls/849)

h3ndrik (12 commits)

• Fix things rimu broke:
  • Restored user notes after rewrite (https://codeberg.org/rimu/pyfedi/pulls/790)
  • Restored user flair functionality after rewrite
• Forms & Security:
  • Added missing CSRF tokens to polls and other forms (https://codeberg.org/rimu/pyfedi/pulls/870)
  • Made donate page editable via CMS (https://codeberg.org/rimu/pyfedi/issues/830)
• Notifications: Fixed scheduled post notifications (https://codeberg.org/rimu/pyfedi/pulls/867)

Neshura (5 commits)

• More accurate server overload warning (https://codeberg.org/rimu/pyfedi/pulls/871)
• Feed Management:
  • Fixed feed deletion performance issues (https://codeberg.org/rimu/pyfedi/pulls/886)
  • Fixed feed owner unsubscribe issue (https://codeberg.org/rimu/pyfedi/pulls/885)
• Documentation: Updated INSTALL.md

karasugawasu (1 commit)

• Internationalization: Added ruby annotation support for Japanese text (https://codeberg.org/rimu/pyfedi/pulls/865)

sleeping-miyagi (several commits)

• Various video embedding improvements and fixes

quokkau (2 commits)

• UI Fixes: Fixed chat avatar sizing issues (https://codeberg.org/rimu/pyfedi/pulls/825)

supakaity (1 commit)

• Registration: CAPTCHA is optional (https://codeberg.org/rimu/pyfedi/pulls/735)

fxomt (1 commit)

• Theming: Updated fxomt theme

Hello folks: I'm wondering if there's anything in the UI or API to view the status of federation/list of federated instances. Largely, this is for personal curiosity but, it could be useful for users deciding what instance to join and for quickly detecting odd federation behavior/API compatibility breakages.

I've seen a lot of people say the piefed API is similar to the lemmy api.

Will it become more distinct as time goes on, or do you plan on keeping them similar?

Which version of the lemmy API is it similar to? v3 or v4?

I post things every so often but honetly I understand people are busy and developing is not a cake walk. I am continually amazed as things just show up. Seperating the comments and posts for users is just massive for evaluating a troll user because the posts tend to be more karma fishing while the comments tend to show what its really doing. Im so impressed at how piefed is working to improve so much and kudos to everyone working on it. This is actually why I originally was on kbin as earnest definately was looking to improve, improve, improve. I still worry about what happened to him. Need closure on his situation and I hope its good or at least better.

EDIT: Initial self-votes don't federate, so it seems this specific way doesn't work.

Am I missing something, or is Piefed's private voting kinda trivial to reverse engineer as long as every user by default upvotes every post and comment they make?

If you have a username and want to find the matching private voting ID, search through that user's posts and comments for an entry that only has one upvote. The vote cast on that entry will be the private voting ID.

If you have a private voting ID and want to find the matching username, search through all votes cast by the private voting ID to find a post/comment that only has one upvote. The user that posted that entry will be the original user.

If it really is this easy, it seems like it's sort of a false sense of security. On the other hand, if automatic upvoting of your own content could be disabled by default, that would prevent this from working.

For example, things that are posted in one instance being delayed in the other, things that are removed not being removed, name changes not showing up, being directed to the wrong places when searching things, info not showing up letting people know they are banned, etc.

I have noticed all of these.

What features made you choose PieFed over Mbin/Lemmy?
What features do they have that you’d like to see in PieFed?

I've created !polls@piefed.social. Normally I would go to the big community promo communities on Lemmy and promote it there. But, since this is a polls community and Lemmy doesn't support polls yet, the community is completely empty when viewed from Lemmy.

I don't really know where else I could go to tell people that this community exists. I hope it's okay to post it here.

Lemmy have Moderator feed which only show post from community in which you mod.

Not sure where to post this: the Piefed API doesn't support CORS, at least testing against piefed.social, so requests from webapps like photon, alexandrite, voyager via PWA would not work.

Also, is there a way to pass a fedilink to resolve, like Lemmy resolveObject?

And lastly, how is Piefed planning on handling updates to the API for lemmy v1? Things like varying object type arrays being combined, and new/updated sorts.

Thanks!

API documentation

OpenAPI docs are at https://freamon.github.io/piefed-api

Mlem

We’re working on adding Piefed support to Mlem 😄 Stay tuned!

https://lemmy.ml/comment/19027320

Blorp

I’m sold. I’ll be adding PieFed support in the next couple months.

https://lemmy.ml/comment/19108013

I'm new here and think it's developing very nicely. Congrats and thank you!

Not the most important thing, but maybe it makes sense to collect some feedback on the various translations?

In the german interface 'Note' in the profile section is not translated, yet the word means 'Grade' in German. Combined with Attitude/Verhalten it may come off as social-scorish, which both are not. (Maybe the latter could have a link to the explanation).

A common alternative would be 'Notiz'.

This is for admins only.

• Create a page with the url "privacy" and it will override the default privacy page.
• Create a page with the url 'about' and the content will be appended to the normal about page.

All other urls just function as you'd expect with no special behavior.

Pretty soon I'll publish a 'rules' page based on the draft post the other day. I can't think of any other uses for it yet but I'm sure people will use it for creative things on their instances.

In web development, the technical term for those popup menus with multiple columns and headings inside is a "mega menu" and I just added one to PieFed. It unifies the topics and feeds menus into one.

It only works on a tablet or larger.

What do you think?

I just created an account here just a couple of days back, so I don't know if this is normal or a bug, so I thought of asking here first.

Today, I posted 3 articles and they all started with 2 upvotes. Not sure if this was the case yesterday too, if it was, admittedly, I didn't notice.