7
submitted 1 month ago* (last edited 1 month ago) by CyberSage@piefed.social to c/piefed_meta@piefed.social

I've deployed piefed.social on a Raspberry Pi and made it public using a Cloudflare Tunnel. Now I'd like to add a Zulip chat instance and, if possible, share login credentials between the two services like the main instance does.

26
submitted 1 month ago* (last edited 1 month ago) by CyberSage@piefed.social to c/piefed_meta@piefed.social

So, I used to vote on posts constantly—not really to give karma, but as a quick way to mark them as read to get them out of my feed. It was perfect: a single click, much faster than actually opening the post. But now with the new voting quota in place, I can't do that anymore without hitting the limit. According to discussions on the instance, the quota was implemented to limit voting activity, and it's already affecting users who vote frequently.

The "Hide posts I've interacted with" setting is still there, but it relies on that interaction happening . What am I supposed to do now? Opening each post to mark it as read is significantly slower. Is there another way to mark posts as read in bulk that I'm missing, or is this just how it's going to be now?

26
submitted 11 months ago* (last edited 11 months ago) by CyberSage@piefed.social to c/piefed_meta@piefed.social

I was thinking about moderation in PieFed after reading @rimu@piefed.social mention he doesn’t want NSFW content because it creates more work to moderate. But if done right, moderation shouldn’t fall heavily on admins at all.

One of the biggest flaws of Reddit is the imbalance between users and moderators—it leads to endless reliance on automods, AI filters, and the usual complaints about power-mods. Most federated platforms just copy that model instead of proven alternatives like Discourse’s trust level system.

On Discourse, moderation power gets distributed across active, trusted users. You don’t see the same tension between "users vs. mods," and it scales much better without requiring admins to constantly police content. That sort of system feels like a much healthier direction for PieFed.

Implementing this system could involve establishing trust levels based on user engagement within each community. Users could earn these trust levels by spending time reading discussions. This could either be community-specific—allowing users to build trust in different communities—or instance-wide, giving a broader trust recognition based on overall activity across the instance. However, if not executed carefully, this could lead to issues such as overmoderation similar to Stack Overflow, where genuine contributions may be stifled, or it might encourage karma farming akin to Reddit, where users attempt to game the system using bots to repost popular content repeatedly.

Worth checking out this related discussion:
Rethinking Moderation: A Call for Trust Level Systems in the Fediverse.

[-] CyberSage@piefed.social 5 points 1 year ago

Browse a list of communities sorted by their Monthly Active Users (MAU). It could make discovering popular or active communities a bit easier. Just a thought! It's not something I'm really missing.

[-] CyberSage@piefed.social 8 points 1 year ago

It's there. 'Do not display posts with which I have already interacted (opened/upvoted/downvoted)'

[-] CyberSage@piefed.social 3 points 1 year ago* (last edited 1 year ago)

A user setting to customize vote display: users could choose to see only upvotes for their own content, while viewing others' content by upvote percentage, or only upvotes, or see both upvotes and downvotes, instead of only total votes.

[-] CyberSage@piefed.social 8 points 1 year ago

My ideal default would be, users have to subscribe to vote, because drive-by downvotes are very common, and keep niche communities from getting anywhere in the All feed.

[-] CyberSage@piefed.social 4 points 1 year ago

That's what I meant, I hadn't seen it before.

[-] CyberSage@piefed.social 4 points 1 year ago

But it allows downvotes, which isn't supposed to be allowed in a poll.

21
submitted 1 year ago* (last edited 1 year ago) by CyberSage@piefed.social to c/ask@piefed.social

Please answer with a single option per comment without duplicating and upvote the topics you've seen active.

I've discovered the keyword filter and I want to know what's out there. Although I doubt the filter will work in topics I at least can try and figure out some keywords usually used in those communities.

The polls don't allow users to add their own options so I had to do it this way.

[-] CyberSage@piefed.social 7 points 1 year ago

Many posts don't have a language selected so 'content language' preference should either allow selecting those, or a setting to reverse it turning it into a block list with all languages automatically selected, then allow the user to deselect his language to block the rest.

[-] CyberSage@piefed.social 8 points 1 year ago

Create a clear description of Piefed on the about page or another relevant page to direct users there instead of the code repository or specific instances.

[-] CyberSage@piefed.social 5 points 1 year ago

User-created sorting methods: If the API exposes post metadata (e.g., timestamps, tags, upvotes, etc.), and the plugin system allows client-side scripting (e.g., JavaScript plugins), users could fetch post metadata and experiment implementing their own custom sorts in the browser.

[-] CyberSage@piefed.social 6 points 1 year ago

Allow user to view only votes from the instance they are using

[-] CyberSage@piefed.social 6 points 1 year ago

Allow voters to write their own choices in polls

64
submitted 1 year ago* (last edited 1 year ago) by CyberSage@piefed.social to c/piefed_meta@piefed.social

I'm super impressed by the features I'm discovering using Piefed! I'm going to be experimenting a lot with the keyword filter particularly. Here are some ideas we might add to make Piefed even better. Share you own in the replies.

Some of these options where too long to make it a poll.

1
submitted 2 years ago* (last edited 2 years ago) by CyberSage@piefed.social to c/piefed_meta@piefed.social

As a community grows in popularity, it often shifts from hosting insightful discussions to attracting memes, funny, and low-quality content. This change appeals to a larger audience interested in such content, creating a vicious cycle where valuable discussions are overshadowed and marginalized by the platform's primary demographic.

It's the pendulum swing of pretty much every community on Reddit.

  • Community starts out with a small group of users dedicated to quality content related to the topic
  • Community growth reaches a point where the most popular posts begin to trend outside of the community
  • New users join the community after seeing popular posts show up in their own feeds. Growth accelerates
  • Community becomes "popular" enough that posts regularly trend outside of the community
  • New users flood in
  • Users flood the community with low-effort content to karma farm
  • Community now sucks.

It happened to basically every big sub on Reddit once reaching a large enough size.

https://lemm.ee/comment/552579

As the platform grows, it becomes increasingly important to have a system that differentiates between different types of content, such as insightful discussions and humorous posts. Without such a system, there is a risk that the platform could become dominated by low-quality content and memes, burying meaningful discussions and discouraging participation from users seeking more substantive interactions.

To address this concern, I propose implementing a nuanced voting system inspired by Slashdot's approach

this was something I loved about slashdot moderation. When voting, people had to specify the reason for the vote. +1 funny, +1 insightful, +1 informative, -1 troll, -1 misleading, etc.

That way you can, for example, set in your user preferences to ignore positive votes for comedy, and put extra value on informative votes.

Then, to keep people from spamming up/down votes and to encourage them to think about their choices, they only gave out a limited number of moderation points to readers. So you’d have to choose which comments to spend your 5 points on.

Then finally, they had ‘meta moderation’ where you’d be shown a comment, and asked “would a vote of insightful be appropriate for this comment” to catch people who down-voted out of disagreement or personal vandetta. Any users who regularly mis-voted would stop receiving the ability to vote.

I don’t think this is directly applicable to a federated system, but I do think it’s one of the best-thought-out voting systems ever created for a discussion board.

edit: a couple other points i liked about it:

Comments were capped at (iirc) +5 and -1. Further votes wouldn’t change the comment’s score.

User karma wasn’t shown. The user page would just say Karma: good. Or Excellent, or poor, or some other vague term.

https://beehaw.org/comment/208569

Normal, Offtopic, Flamebait, Troll, Redundant, Insightful, Interesting, Informative, Funny, Overrated, Underrated

Slashdot had this covered years ago, literally decades.

  1. Upvotes limited to +5.
  2. Votes categorized: funny, informative, insightful, etc.
  3. Number of votes limited per time frame and user karma.
  4. Meta-moderation: your votes (up/down both) were subject to voting (correct/incorrect). good score == more upvotes to spend.

It's a pity that Reddit and other sites didn't follow this model.

https://discuss.online/comment/65643

I'm thinking this seems pretty similar to post tagging. Perhaps both could be implemented with the same feature? Post tagging usually needs to be objective but that's indicated in the guidelines, perhaps there could be some subjective tags users could vote to sort the posts based on those tags.

Wikipedia — Slashdot Peer Moderation

view more: next ›

CyberSage

0 post score
0 comment score
joined 2 years ago