Number of active instances: 692
Number of users: 20 900
Number of statuses: 7 953 608
Number of users last 4h: -1
Number of statuses last 4h: 121
#Fediverse
Fedi, do you tip on self-service/ready-to-go meals?
Ex. Prepared wraps, sandwiches, salad bowls or similar; drinks, chips or snacks, cookies, etc. Where you simply grab what you want and go to pay at the staffed cash.
I’ve created #Piefed’s first dedicated community to movies!
If you’re on #Mastodon, #Akkoma, or #Sharkey, follow it here:
And if you’re on #Lemmy, #Mbin, or Piefed follow it here:
!movies@piefed.social
From now on, all my posts about movies, including reviews, will be posted there.
Everyone is welcome and you’re allowed to chat about whatever movie-related things you like.
#PublicDigitalInfrastructure on the rise:
@encyclia, an #ORCID bridge that will make ORCID records followable and interactable on the fediverse.
"You can use it to follow researchers who don't have a Fediverse presence and see their new publications on your feed! Or you can follow your own ORCID record from #Mastodon (or #Akkoma or #Misskey etc.) and share your academic works with your followers."
One thing about Akkoma that can cause you problems when hosting it is —
It stores media in the databases.
Including caching the profile images and profile headers from random people on the Fediverse.
This can cause your storage-drive to fill up.
I've seen 40% or more of the storage-drive taken up by this caching.
Everything on this #Piefed community does not originate from Piefed:
https://piefed.social/c/lumoura
It originates from #Akkoma or #Pixelfed. Specifically, I’m sending posts that originate from @atomicpoet@atomicpoet.org
and @atomicpoet@pixelfed.social
to @lumoura@piefed.social
.
Now why would I do this? Because I want to:
Yes, I believe this is a very big deal—which is why I talk so much about it.
Here’s screenshots of all four photo-based #Piefed communities I’m running.
Now if these posts look familiar, that’s because I’m posting them from #Akkoma and #Pixelfed – and they’re submitted to Piefed by tagging the relevant communities.
This is what I mean when I say that people on #Lemmy are seeing something drastically different from what you’re seeing on #Mastodon.
I’ve created four new #Piefed photo-based communities. They are:
I’ll mostly be using these communities to post photos from #Akkoma and #Pixelfed. Not only will they categorize these photos in a coherent manner, they’ll be open for other contributors, and also be easy to moderate.
Why not use hashtags instead? Simple: anyone can use a hashtag and no one can moderate them. Which means they’re easy to spam.
For my purposes, groups are simply better.
Nope, mentioning a #Lemmy group actor like @pcgaming@lemmy.ca
does not result in my post appearing in that Lemmy community.
Other people have said that it’s possible to post to Lemmy from a microblogging platform, but every time I’ve tried, I haven’t been able to get it to happen.
So I may have to duplicate several Lemmy communities in #Piefed simply because it plays better with microblogging platforms like #Mastodon and #Akkoma.
RE: https://atomicpoet.org/objects/c76d141f-be15-4821-9ed0-2e88e56b43f5
Confirmed. You can post from a microblogging platform (e.g., #Mastodon, #Akkoma, etc.) to #Piefed simply by mentioning the group actor in your post.
Piefed sticks a [Microblog] descriptor in the title so that #Lemmy, #Mbin, and Piefed readers know that the post originated from a microblog.
To use this feature, you need to use @
for the mention instead of !
. For example @community@exampleserver.com
.
This is yet another reason I’ll be using Piefed to create communities.
So it seems to me that, for posting purposes, #Piefed is much friendlier to #Mastodon and #Akkoma than #Mbin is.
When you look up a Piefed post on microblogging platforms, it returns a link to the post as well as the body:
https://piefed.social/post/488492
But when you look up an Mbin post, it repeats the title twice and does not display the body:
For this reason, I’ll be posting from piefed.social simply because I want my posts to be readable on microblogging platforms. To be sure, this is not a slam against Mbin. I acknowledge it’s a work in progress. But I have to use the platform that works for my purposes.
Attention, blind Akkoma users! I will be writing to the developer with my concerns about a few problems with accessibility on this platform. Most should be easy to resolve. Please let me know if you find any more, and also state what browser and screen reader you are using. Note: This is in reference to the site itself, not to your client of choice. I will post about that separately. For the record, I use NVDA with Firefox.
#accessibility #Akkoma #blind #Blob.cat #Chrome #Fediverse #fediverse #Firefox #JAWS #NVDA #html #ScreenReaders #SemanticHtml #Supermium #Windows