Notices by :abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: (kaniini@pleroma.site), page 2

I am pleased to announce the immediate availability of Michabo v0.1. Sources can be retrieved from the Michabo Git repository. A pre-built binary for Mac users has been attached to this post.

I was planning to do a pre-built Windows version, but was unsuccessful in getting OpenSSL to work with Qt on Windows. Help with that is certainly welcome for future releases!

Michabo is a performance-oriented desktop client for Pleroma and Mastodon instances. With the exception of media handling, which is still a work in progress, the client implements most of the features one would expect in a fediverse client.

The primary goal of the client is to bridge between the fediverse and the desktop computing experience. This goal is only partially realized as yet, and I intend to write a more detailed blog soon about how this design goal is ultimately realized.

Michabo is free software, built by the Pleroma community and licensed under the GNU GPLv3 license.

Right now here are Michabo’s primary deficiencies:

• No integrated support for viewing attachments (attachments are handed off to external viewers, with your web browser as the ultimate fallback)

• Attachments without preview thumbnails are handled suboptimally.

• The Attachment Grid Layout System could really still use some love.

• Special timelines such as Pleroma’s Direct Messages timeline are not yet supported.

• Composing messages with a custom scope are not yet supported (but the scope will be copied).

With that said, I’ve been using Michabo as my primary desktop client for the past few days to fairly reasonable success.

Please report any bugs you encounter to the Michabo bug tracker.

ultimately, SNS services like the fediverse are seen as intimate spaces by many. participants are not thinking about the long term consequences of their actions. to an extent, one can legitimately argue that more care should be taken with selecting the audience who receives a given post.

this is of course, compounded by the fact that in typical implementations, there’s only one path to allowing posts to spread to a wider audience: labelling the posts with as:Public.

there are many avenues of leakage in the fediverse, but the binary between as:Public and a user’s followers collection is too wide and leads to users leaking their own posts unintentionally to make them boostable, etc.

if users have a middle ground, then they will use as:Public in a more appropriate way verses how it is presently used.

of course, the scopes system in general is a UX misdesign because it doesn’t really reflect the open world nature of the fediverse well, and we are working on ways to mitigate that, but it will take time, but when you have a choice between only public or private posts, people will get burned as they try to expand their audience without thinking about all consequences.

ultimately what i’m saying here is that i think there is value in what archive team is trying to accomplish, but the fediverse isn’t ready for it yet. it’d be nice if we could find a middle ground until we fix the way audience selection works (even a mitigation like as:Authenticated being widespread would stop most of the bleeding), and i think what i proposed about having archive team make a fediverse bot that allows a user to request their own instance be archived would be a good middle ground for now.

what do you think, @DashEquals ?