Rimu

Web developer. Lead developer of [PieFed](https://join.piefed.social )

Pronouns: he/him
Location: Earth
Mastodon: https://mastodon.nzoss.nz/@rimu

Public Key

npub1dje7m375wqzmdjzy5et5w7qj925yn9yyvmynctflq2mjr94emf9q0ux0zv

NIP-05 Address

[email protected]

Profile Code

nprofile1qqsxevldcl28qpdkepz2v4680qfz42zfjjzxdjfu95ls9depj6ua5jspzpmhxue69uhkummnw3ezuamfdejsz9rhwden5te0wfjkccte9ejxzmt4wvhxjmcm4dckd

Publishing to

nostr.wine

relay.damus.io

nos.lol

Author Public Key

npub1dje7m375wqzmdjzy5et5w7qj925yn9yyvmynctflq2mjr94emf9q0ux0zv

Show more details

Last Notes

2026-07-25 22:51:47 UTC

For fans of ePaper and eInk devices and tech!
This is quite an old community but it's never been advertised here and has been a ghost town for months. But I made 3 posts in it recently and they did well so it seems like there's an appetite for this subject out there.
[email protected]

2026-07-24 21:52:47 UTC

The Debian project is engaging in a debate and vote on whether large language model (LLM) tools may be used in the development of Debian, its distribution-specific code, and the project's website. The general resolution is currently being discussed leading into a vote on the subject.

2026-07-23 09:29:48 UTC

A search engine that makes videos across the whole PeerTube network actually findable
Peerseek is a federated video search engine for PeerTube. It continuously crawls public PeerTube instances, indexes their videos in PostgreSQL, and serves a fast JSON API and web UI at peerseek.video. At the time of writing it indexes roughly 940,000 videos from about 1,600 instances.
More info at https://polykit.rocks/peerseek-federated-peertube-search/ including a comparison with SepiaSearch.

2026-07-03 10:11:32 UTC

- reply

There's a follow button on each account's profile. So first find one of their posts/comments and then go to the author of it.
Also if you go to https://piefed.social/instances, find the instance you like and then go to the people in that instance, there are Follow buttons everywhere.
I'm not making this slick and easy to use, yet. I don't want everyone to suddenly follow tons of people and cause the server to melt or whatever. This following functionality could increase the federation work the server needs to do in unpredictable ways so I'll be monitoring things and dealing with issues as they arise for a while, before going big on it.

2026-07-03 09:23:37 UTC

This release saw [contributions from some new people](https://codeberg.org/rimu/pyfedi/activity/monthly), which is great to see.
In this release you can now follow other people, not just join communities. When you follow someone their posts will show up in your 'Subscribed' feed, regardless of whether you have joined the community it was posted in or not.
You can also follow Mastodon+ accounts. Getting Mastodon integration working really well is going to be a long journey but this release gets us headed in that direction. Eventually I hope that this integration will provide a steady source of timely content to cross-post into threadiverse communities as well as being a peer citizen in the Mastodon-flavored parts of the fediverse.
### New:
- You can follow other users and their posts will always show up in your 'Subscribed' feed, regardless of the community they were posted into. Following _Mastodon_ users works also but should be considered as very experimental. This will improve soon.
![vaEEQEzRySsPTnR.png](https://media.piefed.social/posts/va/EE/vaEEQEzRySsPTnR.png)
In the future you will be able to upload a list of people that you exported from your mastodon profile and follow them in one go. And add people that your instance doesn't already know about - but not yet. These features will be rolled out in future versions once the dust settles on this version.
- Mastodon posts have a new design that is distinct from threadiverse posts - there is no post title and larger author profile pic.
- Communities can be marked as being a favorite, which makes them more prominent in the 'Communities' menu.
![HHHV9TTSGgWRQbg.png](https://media.piefed.social/posts/HH/HV/HHHV9TTSGgWRQbg.png)
- Clicking anywhere in a post teaser takes you to the teaser - you don't need to aim for the title
- Dramatically improved page load times on Chrome-based browsers (Speculation Rules API).
- Little spinner thing while a vote is being cast
- Updated translations
- Preview markdown when editing a wiki page
- RSS feeds on the home page, including a feed of posts from your subscribed communities
- Topic selection during onboarding looks way nicer now.
- Accessibility improvements to headers.
### For Developers:
- Massive CSS reorganisation by travis-jeans. Lots more usage of CSS variables. Improves maintenance and accessibility.
- API: Users can now log out
- API: Follow and unfollow users
- API: video file upload works now
### For Instance Admins:
- Communities where every moderator is a bot or inactive are flagged as un-moderated. Reports about posts in un-moderated local communities go to admins.
- Warnings on domains can be 3 types instead of only a warning - the other two are 'helpful context' and 'recommendation'
![6ms4yFRd0An2PZd.png :: align-center](https://media.piefed.social/posts/6m/s4/6ms4yFRd0An2PZd.png)
- Send a DM to a user asking them if they are a bot, with 1 click. If they do not respond their account is automatically flagged as a bot
- Email bounce inbox can now be accessed through POP3, not just IMAP
- Tokens used by mobile apps can be set to expire, using the JWT_EXPIRY_DAYS environment variable
- More accurate tracking of when a user was last active. This will significantly increase your MAU stats.
- Strict allowlist mode to reduce attack surface exposed by federation
- /admin/federation form split up into 3 separate pages rather than one long confusing page.
- Option to disable DM sending for individual users if they lack the self-control to use it responsibly.
- compose.yaml has changed a bit: For most containers the build target is now "runtime' instead of 'builder'.
For example
```
celery:
build:
context: .
target: runtime
```
- Topics can be associated with countries, for more targeted onboarding suggestions based on the viewer's location.
- To reduce server load and network traffic, a maximum number of votes that can be cast each day has been set at a level that will only affect the top 2% of voters, leaving the bottom 98% unaffected. This quota can be altered with an environment variable. View a profile to see how much of their daily quota has been used.
### To upgrade from 1.6.x
```
git pull
git checkout v1.7.x
```
At this point you might see an error message about a merge conflict with compose.yaml. To preserve your custom compose.yaml you will need to copy it somewhere else, then `git checkout compose.yaml` then `git pull` again (or use git's stash feature). This time the pull will succeed so after that copy your custom compose.yaml it back, overwriting the one from git.
Then,
`./deploy.sh or ./deploy-docker.sh `
If you had to do the compose.yaml fix up earlier then you might want to compare what you have with https://codeberg.org/rimu/pyfedi/src/branch/main/compose.yaml and manually copy and paste some improvements in particular the `target:` part of the db container.
### Donations
PieFed is [free and open-source](https://codeberg.org/rimu/pyfedi/src/branch/main/LICENSE#L587) 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](https://www.patreon.com/PieFed), [Liberapay](https://liberapay.com/PieFed/) or [Ko-fi](https://ko-fi.com/piefed).

2026-06-16 02:05:30 UTC

- reply

Yes, we need this.
In the next release you'll be able to follow other people (not just communities), which means following people from Mastodon, which means posts are going to start arriving with multiple images.
It's on it's way.

2026-05-05 00:35:14 UTC

from the [mod log](https://piefed.world/modlog?mod_action=ban_user&suspect_user_name=&communities=&user_name=flatworm7591%40lemmy.dbzer0.com&submit=Search):
![Mojng5xTnVM7YHd.png](https://media.piefed.social/posts/Mo/jn/Mojng5xTnVM7YHd.png)
https://s.faf-pb.xyz/lXxek
The output from the LLM was provided as proof that someone needed to be banned.
I didn't want to do this but my hand was forced by [their dissembling, minimization and bullshit](https://piefed.social/post/2032935#comment_11212728).

2026-05-04 04:59:29 UTC

- reply

Check this out - https://www.structural-integrity.eu/the-politics-of-decentralization-and-the-libertarian-allure-of-mastodon/

2026-05-04 04:53:04 UTC

- reply

Yeah you can do that but now you're on my do-not-trust list. And probably a few other people's lists.
I appreciate you being open about your opinions because now I can make an more informed choice about interacting with you and the instance you run.
Don't you think everyone deserves the information they need to choose which instances they want to interact with, according to whatever criteria is important to them? Even if your criteria are different?

2026-05-04 04:46:22 UTC

- reply

> you are free to leave and choose a different one.
I only have that freedom if the admin tells me that they use LLMs in this manner or if they federate with instances that do. At the moment everyone is in the dark.

2026-05-04 04:43:50 UTC

- reply

You're hyperfocusing on one point, as if that's the only part that matters and ignoring all the rest. I don't consider that helpful, hence the downvote.
What is especially unhelpful is abusing your admin access to call out people's votes. Leave that shit alone.

2026-05-04 03:19:36 UTC

I recently discovered that some popular federated instances have been using LLM-assisted moderation tooling that evaluates whether someone has said something bannable. They do this by running a script/app that sends the user’s comment history to OpenAI with the question “analyze this content for evidence of *specific political ideology* sentiment. Also identify any *related political ideology* tropes“. (The italic bits are where I've redacted the ideology they're seeking).
OpenAI’s LLM (they’re using GPT-5.3-mini) then responds with something like:
[![image](https://media.piefed.social/posts/JF/um/JFumUeL3iWYfLVr.png)](https://join.piefed.social/2026/05/04/ai-assisted-moderation-in-the-fediverse-is-happening-now-what/)
and so on, hundreds of comments.
I have not named the instances or people involved, to give them time to consider the results of this discussion, make any corrective changes they want and disclose their practices at their own pace and in their own way. I have also redacted the evidence to avoid personal attacks and dogpiling. Let’s focus on the system, not the individuals involved. Today these instances and people are using it and maybe we’re ok with that because it’s being used by groups we agree with but what if people we strongly disagree with used it on their instances tomorrow?
The use and existence of this tooling raises a lot of other questions too.
What are the risks? Fedi moderators are often unsupervised, untrained volunteers and these are powerful tools.
What safeguards do we need?
Would asking a LLM “please evaluate this person’s political opinions” give different results than “find evidence we can use to ban them” (as used in the cases I’ve seen)?
What are our transparency expectations?
Is this acceptable and normal?
Should this tooling be disclosed? (it was not – should it have been?)
If you were given a choice, would you have opted out of it?
Can we opt out?
Are there GDPR implications? Privacy implications? Should these tools be described in a privacy policy?
Are private messages being scanned and sent to OpenAI?
How long should these assessments be retained and can we request to see it, or ask for it to be deleted?
Once the user’s comments are sent to OpenAI, is it used to train their models?
What will the effect be on our discourse and culture if people know they are being politically profiled?
Where are the lines between normal moderation assistance tools, political profiling and opaque 3rd-party data processing?
I hope that by chewing over these questions we can begin to establish some norms and expectations around this technology. The fediverse doesn’t have any centralized enforcement so we need discussions like this to develop an awareness of what people want in terms of disclosure, privacy, consent and acceptable use. Then people can make choices about which instances they join and which ones they interact with remotely.
And of course there are the other issues with LLMs relating to environmental sustainability, erosion of worker’s rights, increasing the cost of living and on and on. I can’t see PieFed adding any functionality like this anytime soon. But it’s happening out there anyway so now we need to talk about it.
What do you make of this?

2026-05-01 22:54:08 UTC

I did some analysis of [the modlog](https://piefed.social/modlog) and found this:
![V8lPrxY1qxcISLe.png](https://media.piefed.social/posts/V8/lP/V8lPrxY1qxcISLe.png)
Ok, bigger instances ban more often. Not surprising, because they have more communities and more users and more trouble. But hang on, dbzer0 isn't a very big instance. What happens if we do a ratio of bans vs number of users?
![vyfUNYTrX9pHQeR.png](https://media.piefed.social/posts/vy/fU/vyfUNYTrX9pHQeR.png)
Ok, so lemmy.ml, dbzer0 and pawb are issue an outsized amount of bans for the number of users they have... But surely the number of communities the instance hosts is going to mean they have to ban more? Bans are used to moderate communities, not just to shield their user-base from the outside. Let's look at the number of bans per community hosted:
![Yrc7TofOr88SeGt.png](https://media.piefed.social/posts/Yr/c7/Yrc7TofOr88SeGt.png)
Seems like dbzer0 really loves to ban. Even more than the marxists and the furries! What is it about dbzer0 that makes them such prolific banners?
Raw-ish numbers and calculations are [in this spreadsheet](https://join.piefed.social/wp-content/uploads/2026/05/banning_numbers.ods) if anyone wants to make their own charts.

2026-04-16 23:44:19 UTC

Banning kids from social media won’t work, as they “will find very quickly the ways to go around and to still use social media,” Estonian Education Minister Kristina Kallas said.

2026-04-08 22:33:36 UTC

**Please only vote if you have contributed to PieFed in some capacity (e.g. coding, translation, reporting bugs, discussing bugs) or might in the near future!**
> Currently, we have two different developer chats on Zulip and Matrix. This means, that new devs will be confused about which channel to join and experienced devs have to actively look around in both channels for questions to answer. This seems like a really inefficient system, so we should at least decide on one official communication channel.
More discussion at https://piefed.social/c/piefed_meta/p/1964543/we-should-rethink-how-the-communitcation-channels-for-piefed-devs-work
Personally I find Matrix to be a pain in the ass and prefer Zulip. But it hasn't managed to attract as many users as Matrix has despite pushing it quite hard for months. Also PieFed development has started to bleed over into PieFed naturally, such as [email protected] and [email protected]. So we're in an awkward place at the moment.

2026-03-22 06:21:04 UTC

A few months ago I threw this question out into the void - "what if you could access the fediverse through your Usenet reader??" and got almost no response. Still, the idea had lodged in my brain and wouldn't go away so this weekend I caved in and built the thing. Hat tip to the author of the excellent [nntpserver package](https://pypi.org/project/nntpserver/) that did all the hard stuff.
I look forward to seeing someone's screenshots of fediverse posts on a Commodore 64, some day.
This will be released as a part of PieFed 1.7, coming soon.

2026-02-23 23:15:02 UTC

- reply

Very interesting that only 71% of humans got it right.

2026-02-18 04:30:11 UTC

2026-01-28 22:30:24 UTC

Welcome! What brings you to PieFed and how did you find out about it?

2026-01-12 06:57:02 UTC

### 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-label`s
- 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
```

2025-12-07 07:37:24 UTC

One of the long-standing issues we have in/on the fediverse is that when I have a link in my post that goes to another post on my instance, people on other instances will click that link and be taken to MY instance, where they can't comment, don't have an account, aren't logged in, etc and they will try to log in using their login credentials for their home instance then wonder why it doesn't work.
When someone links to https://lemmy.world/post/39832275 and I'm on piefed.social I want to see https://piefed.social/c/news/p/1544770/national-parks-ordered-to-check-gift-shops-for-dei-type-items not the copy on lemmy.world!
As of PieFed v1.4, links like that will automatically be converted to link to the local copy of the post, where 'local' is whatever is local for the reader. See the linked video where I demonstrate this in action.

2025-10-30 06:18:06 UTC

- reply

Yes, we know.
This is a blog post about Anubis I wrote a few months back, when I thought I had it working https://join.piefed.social/2025/07/09/an-anubis-config-for-piefed/
After writing that post I took another approach and moved the logic into nginx instead as the Anubis configuration language was impossible to debug. That seemed fine but then a different weird Anubis bug that had been languishing in their issue queue for months with no solution hit me and I gave up.
It's just not ready. It's bad software. Their documentation is very misleading. I hope no one else loses as many days as I did.

2025-10-30 03:14:23 UTC

- reply

Sir, this is a Wendys.

2025-10-29 23:40:52 UTC

- reply

I tried 2 times, for hours each time, to set this up in a way that does not break federation, the api, or the web ui. It's not as easy as the OP thinks and problems aren't always obvious immediately.

2025-10-09 03:39:21 UTC

- reply

Yes PieFed has that.

2025-10-09 01:06:50 UTC

I've followed all the frequent posters on piefed.social using my mastodon.social account so we should be seeing a lot more PieFed content showing up there now. But unless you use hashtags, I'll be the only one seeing it!
When making your post, put a few words into the Tags field below the Body field, separated by a comma. No need to include the # character.

2025-09-12 22:39:25 UTC

- reply

FYI piefed released v1.1.6 and v1.1.7 in the last week.
https://codeberg.org/rimu/pyfedi/releases
I'll put more fulsome release notes on minor point releases like that if I know people are going to link to them.

2025-09-12 20:33:06 UTC

- reply

Naah, when mods delete things it federates out.

2025-09-12 10:35:51 UTC

- reply

I'll wait to see what people want but I probably intended the 'delete child comments' feature to be for moderators only. For cleaning up threads that have gone off on a bad tangent.

2025-09-07 00:01:52 UTC

- reply

Possibly although the differences of federation between the threadiverse and the rest of the fediverse go way beyond deletes. FEP 1b12 is a whole thing, chipping away at it piece by piece would be slow going.

2025-09-06 22:53:09 UTC

- reply

Yes, a Delete activity is sent to all instances with actors that follow the category/community. Those instances then delete their local copy. In Lemmy/PieFed there is no distinction between deletion and removal.
The deletes are soft so it is possible to un-delete by sending an Undo activity. PieFed keeps soft-deleted posts (topics, in NodeBB language) for a few days then after a week deletes the content from the database.
All of these activities are enclosed in an `Announce` and the http POST is signed using the community key. So in a way the content 'belongs' to the community, not to the original author. With that model of ownership the idea of removal redundant - a post without a community is not a post.
Tangentially - it would be good to come up with a way to move a topic to another category and federate that so the move can happen on other instances, too. We could go off-piste and create a `Move` activity, or use `Remove` (from old topic/comm) followed by `Add` (to new topic/comm) to do the same thing. I feel more inclined to go with `Move` as it's a single atomic operation that either succeeds or fails, despite it not being in the spec.
The AP spec is so badly stretched by various implementation-specific differences that I don't think it's worth being ideological about adherence to it it anymore.

2025-08-29 10:26:18 UTC

The upcoming v1.2 release will include a built-in instance chooser, so every instance will be able to recommend every other instance, without a centralized site like https://joinmastodon.org or https://lemmyverse.net/instances. (except those instances that have opted out or closed registrations)
The instance-choosers for other platforms tend to push people towards the bigger instances by prominently displaying the number of users or communities they have, or even worse sorting results by number of users. This seems like a good metric because if lots of people chose it in the past then it must be well-run, right? Right? Heh.
Instead, the PieFed instance chooser sorts by ping (network ping + page load speed) and prominently shows a "Stability" metric which is a combination of various things (daily backups, multiple people having SSH access, financial health, etc). Another key metric is Newbie-friendliness which is whether they have a decent number of topics created, which are used as starter-packs to get new accounts into many communities quickly. Thirdly, the Age is shown, which is the number of months it has been operating. Join brand new instances at your peril.
Another aspect I've chosen not to get into is regional or topic focus of instances because most people are into more than one topic, leading to difficult choices. Sorting by ping will tend to show you instances in your country anyway.
The primary language of an instance is really important - people need to be able to communicate with their admins - so I made that a filter.
With new PieFed instances opening up all the time we need to get new people using those instead of everyone clustering together on piefed.social. The sooner we do this the better, in terms of spreading the financial load around and fostering a healthy diversity of instances before one or two instances snowball and end up dominating.
I'm really looking forward to releasing this functionality, in the next couple of weeks.
https://media.piefed.social/posts/pv/RL/pvRLrJTDSKpMPAL.png

2025-08-04 08:43:00 UTC

It's been 6 weeks since 1.0 and we've merged in 80+ PRs and closed as many issues. A third of the issues originally intended for v1.2 are already completed and so they are included in 1.1 instead.
### Some signs of maturity
There are now 32 PieFed instances, serving 1750+ MAU. Voyager, Summit, Blorp and Interstellar are mobile apps that connect to PieFed.
From now on https://piefed.social will change from following the main development branch of the repo and instead stay on v1.1 until v1.2 is released. This will provide a more stable experience for people using the instance and allow for wilder experiments on the development branch. I recommend all other instances do the same.
It will also put less pressure on other instances to keep up with piefed.social. A new instance will be created soon that will use the dev branch and serve as a staging instance.
### To upgrade
To upgrade from 1.0.x (or switch to 1.1 from the main branch):
```
git pull
git checkout v1.1.x
./deploy.sh or ./deploy-docker.sh
```
### Highlights of 1.1
Most instances have been on the dev branch anyway so they will already have these:
You can set a default comment sort, for when viewing a post.
LDAP support, so people can use their piefed.social login for chat.piefed.social and translate.piefed.social
More Ajax throughout, creating a more fluid UI.
Better notifications, with types and which are removed if the post they're notifying about is deleted.
Private votes are just non-federated votes.
Popup tooltips all over the place.
New login methods:
- Mastodon
- Discord
Hashtags in community side pane, e.g. [this community](https://piefed.social/c/fediverse)
Daily maintenance tasks execute in parallel, which is a lot faster.
[Batched ActivityPub federation](https://codeberg.org/rimu/pyfedi/src/branch/main/docs/fep-4248.md) that will significantly improve federation performance between PieFed instances
Filter out posts based on a keyword search of community name.
Reduce deadlocks and improve DB performance
- use redis for locking.
- extensive refactors to stop connection leakage.
Load comments using ajax when there are > 100 on a post, making the initial loading of a post quicker.
Automatic post archiving of old posts, to slow DB growth and reduce operating costs. Post body and comments are saved in S3 as JSON instead of in the DB.
Show/hide text inside password fields, making confusion during login less common.
Mods can lock comments and their children.
A lot of improvements to scheduled posts.
Several improvements in the markdown to html parsing.
Upgrade to Flask 3.
Swagger for API developers (in progress).
API: new json serialization lib that is 10x faster.
API: Get topics & feeds endpoints. Replacement for comments/list endpoint.
### Things planned for 1.2
An instance chooser during registration - no separate instance choosing website needed
Optional post approval process for mods
Communities populated by a RSS feed.
Remind me
AI content filter
Event post type which federates with Friendica and [Mobilizon](https://mobilizon.org/)

2025-06-05 21:56:19 UTC

What if the Fediverse met... in real life?

2025-04-16 00:45:22 UTC

2025-03-21 19:13:11 UTC

>“This is a completely different approach to what people have done before. The writing’s on the wall that this is going to transform things, it’s going to be the new way of doing forecasting,” Turner said. He said the model would eventually be able to produce accurate eight-day forecasts, compared with five-day forecast at present, as well as hyper-localised predictions.
>Dr Scott Hosking, the director of science and innovation for environment and sustainability at the Alan Turing Institute, said the breakthrough could “democratise forecasting” by making powerful technologies available to developing nations around the world, as well as assisting policymakers, emergency planners and industries that rely on accurate weather forecasts.

2025-03-20 22:36:27 UTC

- reply

Every few months Dansup announces that Groups are imminent.

2025-02-21 06:38:05 UTC

2025-02-10 03:59:51 UTC

Communities on PieFed have a setting that controls whether downvotes are accepted and from where.
Perfect for communities that swim against the mainstream a bit!
https://piefed.social/static/media/posts/Jd/Xq/JdXqxnPr60X54ub.png

2025-02-10 00:36:38 UTC

[email protected]
All pro-PieFed memes are welcome!

2025-01-24 23:23:51 UTC

We’re working on a multireddit feature which will let people join or leave large groups of related Communities with a single click, and see all the posts from those communities in a single list. These groups will be crowd-sourced, so anyone can create or share collections of Communities around their interests. Basically the same as https://piefed.social/topics except crowd-sourced (and federated?).
We’re stuck on what to call this feature, though, and your creativity could really help us out! Here are some ideas we’ve been tossing around:
- Bundles
- Community Packs
- PieSlices
- Stacks
- QuickJoin Packs
- Collections (kbin called it this)
- Topics (we call them this now but they're all maintained by the instance admin)
Which of these do you like best? Do you have any suggestions of your own? We're aiming for something that’s easy to understand, catchy, and fits the PieFed ethos. I'll copy those suggestions into individual comments on this post so people can upvote what resonates with them.
The problem I have with ideas like "Collections" or "Topics" is those concepts have no relation to "Communities" which increases the learning new users need to do while getting comfortable. Something more intuitive like "Towns" is more obviously a larger or group of "Communities", for example.
Please throw your ideas into the comments below and vote on what you see!

2025-01-11 05:21:20 UTC

2024-11-09 01:56:14 UTC

Recently there have been two more PieFed instances created, which offer accounts to anyone who wants one:
- https://feddit.online
- https://link.fossdle.org
Feddit.online is hosted in USA which should make it a _little_ faster for people there. It also has a different topic structure at https://feddit.online/topics than PieFed.social has.

2024-10-11 07:57:41 UTC

Eighteen theatregoers at Stuttgart’s state opera required medical treatment for severe nausea over the weekend after watching a performance that included live piercing, unsimulated sexual intercourse and copious amounts of fake and real blood.

2024-08-19 21:42:22 UTC

We had [a really interesting discussion](https://lemmy.world/post/18805474 ) yesterday about voting on Lemmy/PieFed/Mbin and whether they should be private or not, [whether they are already public](https://lemmy.world/post/18813833 ) and to what degree, if another way was possible. There was a widely held belief that [votes should be private](https://lemmy.world/comment/11850820 ) yet it was repeatedly pointed out that [a quick visit to an Mbin instance](https://lemmy.world/comment/11854355 ) was enough to see all the upvotes and that [Lemmy admins already have a quick and easy UI](https://lemmy.world/comment/11851016 ) for upvotes and downvotes (with [predictable results](https://lemm.ee/comment/13768482 ) ). Some thought that using ActivityPub automatically means any privacy is impossible (spoiler: it doesn't).
As a response, I’m trying this out: PieFed accounts now have two profiles within them - one used for posting content and another (with no name, profile photo or bio, etc) for voting. PieFed federates content using the main profile most of the time but when sending votes to Mbin and Lemmy it uses the anonymous profile. The anonymous profile cannot be associated with its controlling account by anyone other than your PieFed instance admin(s). There is one and only one anonymous profile per account so it will still be possible to analyze voting patterns for abuse or manipulation.
ActivityPub geeks: the anonymous profile is a separate Actor with a different url. The Activity for the vote has its “actor” field set to the anonymous Actor url instead of the main Actor. PieFed provides all the usual url endpoints, WebFinger, etc for both actors but only provides user-provided PII for the main one.
That’s all it is. Pretty simple, really.
To enable the anonymous profile, go to https://piefed.social/user/settings and tick the ‘Vote privately’ checkbox. If you [make a new account](https://piefed.social/auth/register ) now it will have this ticked already.
This will be a bit controversial, for some. I’ll be listening to your feedback and here to answer any questions. Remember this is just an experiment which could be removed if it turns out to make things worse rather than better. I've done my best to think through the implications and side-effects but there could be things I missed. Let's see how it goes.

2024-08-18 22:55:23 UTC

Probably better to post in the github issue rather than replying here.
https://github.com/LemmyNet/lemmy/issues/4967

2024-08-17 00:33:00 UTC

A new contributor, "JollyDevelopment" made some improvements:
<li>Fixed a very annoying bug where enabling the markdown editor emptied the text input field</li>
<li>Changed the home page so there are now separate sorting and filtering options, making the 'Popular' and 'All' home pages obsolete. They have been removed from the main menu.</li>
<li>Added a 'dev tools' page so developers can easily create large amounts of dummy content to test with</li>
<li>Added a <a href="https://piefed.social/topics/new" rel="nofollow ugc" target="_blank">suggest a topic</a> form</li>
"wakest" created a very efficient SVG icon for PieFed that is 5x smaller than the old .png icon.
Also I did a few things:
<li>Made wide tables scroll rather than overlap the sidebar</li>
<li>Communities can be blocked. Good if you regularly browse posts by 'All' which is bit of a firehose.</li>
<li>Some mastodon integration bugs</li>
<li>Wrote a guide about <a href="https://join.piefed.social/docs/piefed-mobile/" rel="nofollow ugc" target="_blank">how to install the PieFed mobile app</a></li>
As you can see we don't have a lot of *really* big news to share, lately. It nearly feels like a good time to call an end to the beta test phase of PieFed's development and formally release a version. With that in mind, over the next little while, we will focus on stability and bug fixes so the first release is something people can stick with without immediately getting back on the dev branch treadmill.

2024-08-07 03:40:48 UTC

Just a quick note to recognize that the first lines of PieFed code were published on the 28th July 2023, just over a year ago. Since then there have been 1400+ changes made by 9 people, involving adding 88,000 lines of code and removing 28,000 lines. The issue queue has 98 open and 99 closed issues.
While [join.piefed.social](https://join.piefed.social ) went live in October 2023, it wasn't until time off work over the christmas holidays enabled a big push to get it ready that [piefed.social](https://piefed.social ) went live on 4th January 2024.
Since then piefed.social has federated 190k posts, 2.3M comments and 19M votes with 1900 other instances of various types. Besides piefed.social there are 5 other PieFed instances that I know of.
What a year it's been! I've grown significantly as a developer, had a lot of fun and hopefully contributed something meaningful to whatever the fediverse is becoming. Long may it continue!