shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

288
active users

#akkoma

5 posts5 participants0 posts today

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.

#poll#polls#fedi

#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."

encyclia.pub/

Encyclia.pubEncyclia.pubBridging ORCID into the Fediverse

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:

  1. create photo streams around a unique aesthetic
  2. de-couple certain content away from my personal accounts
  3. allow people to experience that content through different social media lenses

Yes, I believe this is a very big deal—which is why I talk so much about it.

piefed.socialLumouraAn arts and culture aesthetic that has a certain unexplainable mood.

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:

  1. @recordpics
  2. @dustbloom
  3. @lumoura
  4. @blue

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:

https://kbin.earth/m/pcgaming@lemmy.ca/t/947755/Steam-s-best-rated-games-of-2024-aren-t-what-you-d-expect

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.

piefed.socialWelcome Amiga fans!I never grew up with an Amiga. But as I joined the Internet, I became aware of this legendary machine that had incredible graphics and sound -- and…

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.

  1. Many buttons are unlabelled and simply say "button". This is true on the main page as well as when viewing posts and tabs in profiles. Most work once pressed. They just need to be labelled.
  2. Searching for people, tags, groups, and posts is inaccessible. I can enter the edit field and write my text, but then, there are two unlabelled buttons next to that. The first simply takes me back to the edit field. The second does nothing. I am assuming this is a submit button that doesn't work via the keyboard.
  3. It is impossible to view followers, as well as those whom I follow. I can see the numbers of each but not the people and groups themselves.
  4. I cannot read my own profile without editing it. There appears to be no link where I can simply view it, either as myself or anonymously. If I go to my page and am not logged in, however, I can view it. I can also easily edit it when logged in.
  5. The page renders very differently in Chrome than in Firefox. In Chrome, I can't see anything but my notifications, so I can't get to my page or the other timelines.

#accessibility #Akkoma #blind #Blob.cat #Chrome #Fediverse #fediverse #Firefox #JAWS #NVDA #html #ScreenReaders #SemanticHtml #Supermium #Windows

What client do you use to browse #akkoma on #android ?

I prefer native apps as they are faster and use less data. My experience so far:

#moshidon (Using this app currently)
Lightweight, fast and beautiful. Issues with emoji reactions and notifications. Development seems to be stalled.

#pachli
Actively developed and really good. Some issues like scrolling of posts when you open the timeline and emoji reactions.

#phanpy (web)
Beautiful and minimalistic. Cannot schedule posts

#elk (web)
Beautiful but cannot login.

#mangane (web)
Default and minimal web UI for my instance. Can't figure out a way to browse lists.

#mastodon #fediverse