I’ve been following the discussion by @alexito4 about adding extra tags to a followed hashtag on Fedi clients generally (and @IceCubesApp specifically) with interest …

Since this is a feature that I’d wanted myself, I decided to go ahead and add it to my custom IceCubes fork with an additional change — the ability to specify how the extra tags are used for selecting posts …

This should reduce my main timeline clutter quite a bit — with an additional change, of course. Currently, followed tags appear in the main timeline and I’ve added filtering to remove them.

But I realized with this change that I don’t have to follow hashtags at all — I was simply doing that as a backup mechanism so that I can have all followed hashtags saved on the server so that when I switch clients, I don’t have to set up hashtags all over again.

However, if I add saving my local client config to iCloud, I might have a much better system here … Hmm ….

#FediClients #Swift #SwiftUI #Coding #Hashtags

So … good news, bad news situation with yesterday’s experiment with putting some of the more high-volume people I follow on to lists and unfollowing them 😛

My hometimeline was so much leaner and cleaner today. There were very few replies and I just got posts that I was actually interested in and was through my home timeline in record time since I had like one third the normal volume of posts.

On the other hand, the list had not moved at all since I created it yesterday, except for one post 😀

Now if I’d stopped to think about this before I came up with my “brilliant” plan, I would have realized this — given the philosophy behind Mastodon/Fediverse, I don’t think anybody really wants you following people without the followee knowing/approving the action. So, creating lists the way Twitter allowed you to would not make much sense from a privacy standpoint.

Unfortunately, that makes lists a rather useless feature in the Fediverse since, as far as I know, there is no server-side filtering of posts from lists from your main timeline. If you just scroll through and read a bit and don’t care about duplicates, this is fine. But if you obsessively go through every post till you are caught up, like I do, then this becomes annoying pretty fast 😛

So my plan at the moment is to implement client-side filtering. When posts are fetched from the server for the home timeline, see if any of the fetched posts are authored by, replies to, or boosts by people on any of my lists. If they are, filter out those posts since they will be displayed on the lists.

I’m not sure how CPU intensive this will be and how smooth the experience will be. But I’m going to try and find out …

#Lists #Following #FediStuff #FediClients

@Kaiteki is being developed to support #Misskey, Mastodon, #Pleroma and Twitter all from one client. They are looking for a #macOS developer to add to the already existing Linux, Android, and Windows support. #FediClients