Pixelfed federates now! 🎉
Merry Christmas fediverse. #pixelfed
We are an ethical alternative to Instagram.
The project is still young, but we are getting close to a polished v1.0 release with federation support!
We can't wait to join the fediverse. ❤️ #pixelfed
Instagram was ranked as the most toxic social media platform.
Pixelfed can do better but we need your help.
I'm organizing working groups to contribute solutions that improve platform safety.
Follow @PixelfedLabs for the latest updates!
Pixelfed users will be able to block domains, I forgot I shipped this already but found a few bugs. Will be shipping the bug fixes shortly!
In the near future you will be able to export/import block lists across Pixelfed instances.
We will be banning Gab domains in the next version (v0.9.5) due for release in the next few days.
Pixelfed Labs will be establishing working groups to tackle a wide range of issues and topics related to pixelfed and social media.
The first batch of groups will be:
- Abuse Prevention
- Youth Safety
- Dark Pattern Prevention
We will need your help. You will have a chance to shape pixelfed's future and make it more inclusive and safe for everyone.
For more info, follow @PixelfedLabs
v0.9.5 major updates:
- Photo improvements (filters + alt tags)
- Admin dashboard updates
- User settings updates
- Video support + Loops updates
- Discover updates
- Bulk manage followers/following
- Contact form/page
- CW Comments
- Admin Custom Page Editor
- Admin Configuration Editor
- Performance improvements
- Remote Following
- Remote posts (search, like, share, comment, report)
and more! #pixelfed
Full federation timeline:
v0.9.5 - Remote follows, remote posts in home timeline (ETA: ~1 day)
v0.9.6 - Shared inbox, profile refetching, bug fixes (ETA: ~1 week)
v0.9.7 - Network timeline (ETA: ready now)
v0.9.8 - Direct Messages (ETA: ready now)
v0.9.9 - Bug fixes and TBA features
Keep in mind that opt-in federation updates in v0.9.5 will be extremely experimental.
Enabling the federation experiments is not recommended for production instances until v0.9.6 or later.
Please update your pixelfed instance ASAP.
We have fixed a bug introduced earlier today that could have locked a single user out of their account.
We apologize for not catching this bug sooner.
Special thanks to @tuneintodetuned for alerting us to this bug.
To see if you have an affected profile on your instance, run the following command in artisan tinker:
If the response is 0, you have no affected accounts.
To fix an affected account:
$email = 'users email here';
$user = User::whereEmail('')->first();
$user->email = $email;
$user->email_verified_at = now();
- PSA Update -
We have shipped a fix and tested in production.
When we moved the email settings to its own page, we did not update the logic, leading to an unfortunate bug.
If a user updated their name, bio or website on an instance running the latest commits, it would clear their email and email verified at timestamp.
The bug would only affect one account per instance due to the unique constraint of the email column.
It's easy to fix the affected account by setting their email manually...
✅ Easy Installation
✅ Powerful Admin Dashboard
✅ One click updates
Shipping in v0.9.5 with Remote Follows!
Photo Sharing. For Everyone.
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!