We are a software development studio from Austria.
We are known for developing the Pixelfed client @Pixelix
| hompage | https://ghostbyte.dev/ |
| Socialfolio Profile | https://socialfolio.me/ghostbyte |
We are a software development studio from Austria.
We are known for developing the Pixelfed client @Pixelix
| hompage | https://ghostbyte.dev/ |
| Socialfolio Profile | https://socialfolio.me/ghostbyte |
When visiting a user profile on Pixelix, a small icon at the top is indicating the Fediverse software which the profile is using. This icon can be clicked to open a dialog with more information about the software and the server.
Previous versions of Pixelix fetched this data from FediDB. With our latest Pixelix update we exchanged the FediDB dependency with our own service called FediSea.
More information about FediSea: https://fedisea.surf
Hey everyone!
Quick question for all the Pixelix users, where did you get the app from?
We would love to understand our community better.
Let us know in the replies if you got it from somewhere else.
Please boost for more reach 🚀
A new Pixelix update is coming later today 👀
Wer an #Pixelfed seine Freude hat, sollte sich die App #Pixelix anschauen. Meines Erachtens gelungener (stabiler) als die "Haus-App"
https://f-droid.org/de/packages/com.daniebeler.pfpixelix/
Via Google Play kostet das Tool rund 2 Euro
Today was a quite productive day. FediSea now stores server location (country and city) and provider name of every instance.
We are also storing the supported protocols and the metadata JSON in Nodeinfo.
We just restarted the crawler to revisit every instance again and store the newly added information.
Check it out:
https://fedisea.surf/servers/pixelix.social
I love all the creative Mastodon instance thumbnails😍
To initially fill the software table of the database we used the data in the "software.json" file of communityDB (FediDB).