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 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  

from app.shared.tasks import maintenance  
from app.shared.tasks import follows, likes, notes, deletes, flags, pages, locks, adds, removes, groups, users, blocks  

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

Daily maintenance tasks execute in parallel, which is a lot faster.

Batched ActivityPub federation 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

In a landmark decision, the Muscogee (Creek) Nation supreme court ruled that Rhonda Grayson and Jeffrey Kennedy, two descendants of people who were once enslaved by the tribe, are entitled to tribal citizenship.

The court ruled on Wednesday that the Muscogee Nation’s citizenship board violated a 1866 treaty in denying Grayson and Kennedy’s 2019 application for enrollment. At the time, the citizenship board argued that the descendants should be denied because they could not identify lineal descendants of the tribe.

Grayson, who is the founder and director of the Oklahoma Indian Territory Museum of Black Creek Freedmen History, and Kennedy are descendants of the Creek Freedmen, people who were enslaved by the Muscogee Nation. They can trace their lineage back to people who are on the Dawes Rolls, a list that identifies people from the Cherokee, Chickasaw, Choctaw, Muscogee (Creek) and Seminole tribes. Grayson’s and Kennedy’s ancestors are also listed on the Freedmen Roll, but not the Muscogee Roll. This discrepancy is how the tribal citizenship board previously justified denying Grayson’s and Kennedy’s applications for enrollment.

However, the court ruled unanimously this week that such a decision was in violation of the Muscogee Nation’s laws. “Are we, as a Nation, bound to treaty promises made so many years ago?” the court wrote. “Today, we answer in the affirmative, because this is what Mvskoke law demands.” According to the ruling, any future applicant who can trace their ancestry to someone on either roll will be eligible for enrollment.