Notices by pixelfed (pixelfed@mastodon.social), page 12

Registration is closed on pixelfed.social, however there are a few other instances open!

https://pix.hostux.social
https://pxlfd.me
https://pix.tedomum.net
https://admires.art

(We do not endorse any instances, including pixelfed.social or any instances @dansup runs)

@moshpirit @Julianoe Please DM me your paypal so I can transfer the logo prizes!

@plantabaja I know of a few people working on art and photography instances!

Mod tools are almost finished! This is one of the last things I need to complete before I start testing federation support!

Audio via @funkwhale, pleroma, and peertube!

Its an experimental feature that will be ready after federation support!

cc @lain @Chocobozzz

YSK: Federation support for PixelFed is not ready yet, still have to finish some important features!

We are getting pretty close though 😉

New UI improvements for timelines! #pixelfed

Congrats to @marrkus on winning the logo contest! It will be added to the project soon. #pixelfed

@moshpirit That is very noble! Thank you. I will reach out to @mmn to arrange the transfer!

@mmn @makitadoge @Julianoe @hellcp @marrkus @Loogah

Fred the PixelFed mascot by @hellcp

Winners, please reach out for payment!

@marrkus - 1st place winner
@Loogah - 2nd place winner
@moshpirit - 3rd place winner
@Julianoe - 4th place winner
@hellcp - 5th place winner & mascot winner (payment sent)

The logo contest is now closed, and the winning logo has been chosen. Thank you to all the participants!

More information here: https://github.com/dansup/pixelfed/issues/182

Doodles. An optional feature to celebrate important dates! 🏳️🌈 #pride #pridemonth2018

Registration will re-open for another hour for those that missed it!

Registration is open for 1 hour, and the file size limit and caption limit have been doubled on pixelfed.social!

150 => 300 (caption)
15mb => 30mb (per file)

https://pixelfed.social/register

If you reserved your username on June 5th, you have to do a password reset to access your account!

The goal for the discover feature is to use public data (likes, captions, comments, hashtags) as signals in an algorithm to show you related posts (including federated posts the instance is aware of). This would be similar to IG while balancing privacy with discovery! (non-public data will not be used, ie: dm's, follower only posts, ect)

Instance/domain blocking will be supported, but you might not even need it!

There is no federated timeline, and a user will only see posts from people they follow or local users on the public timeline. They can mute (ignore, prevent mention notifications) remote users/domains and admins can mute remote users/domains too.

I'm not against a federated timeline, I'm just not sure it makes sense for this project. Feedback wanted!

Good news: CW, Filters, privacy settings, Admin/Mod tools, and accessibility/localization features have been prioritized.

Bad news: This will delay federation support. I think its crucial for CW support, privacy settings, and mod tools to be ready before federation is supported.

The CW/NSFW feature is nearly complete, it may not look pretty at first but we will improve the CW UI eventually. It works without js using the HTML5 <details> tag! #JavascriptNotRequired