@mwichary Based on https://unsung.aresluna.org/before-pixels-modular-industrial-dashboards/ you will probably enjoy some of the displays on show in https://www.youtube.com/watch?v=omYfLDlt-MA

Was looking like the clouds might ruin the #eclipse over #valencia, and then...

@mwichary For example, in https://pachli.app, tapping the "Bookmark" button bookmarks a post and animates. The taps are throttled, so if the user inadvertently double-taps the bookmark button they don't accidentally un-bookmark the post. This has nothing to do with the animation.

@mwichary Re https://unsung.aresluna.org/if-youre-a-button-you-have-one-job/

I don't see anything that suggests this is because of animation. It looks more like typical tap throttling/debouncing.

As you undoubtedly know, but just in case the audience doesn't, an app might do this when a "double-tap" on a control doesn't make sense, but where tapping the control twice might either undo an action the user has taken, or take them further from their desired action.

#Collections bypass your filters.

If someone posts a link to a collection in your timeline (or you receive a collection notification), and you have filters that match the collection's name, description, or hashtag, those filters **are not applied**.

/fin

Other issues:

#Collections can have an associated hashtag. If you follow that hashtag you should see all posts that use that hashtag. If someone posts a link to a collection that uses that hashtag it does not appear in your home timeline.

Each hashtag also has a timeline you can follow, to see all posts with that hashtag. Posts that reference a collection with a hashtag do not appear in this timeline either.

Unlisted #collections can be shared by posting a link to them. If someone does this:

1. The poster is not warned before posting that the collection they are sharing is unlisted. So they may inadvertently share a collection more widely than the owner intended.

2. As a member of the collection you are not notified that a link to the collection has been posted.

However, currently:

1. The UI for viewing #collections does not show if the collection is "unlisted" or "public", so it's difficult to provide informed consent initially.

2. If the collection owner changes the collection from "unlisted" to "public" **you are not notified**, so it's difficult to provide ongoing consent.

3. If accounts are added or removed from the collection **you are not notified**, again making ongoing consent difficult.

Someone may add you to a one or more #collections and mark them as "unlisted". This means the collection is only visible to people with the link to the collection; it is not visible on the collection owner's account, in recommendations, or search results.

Your consent for your account to be in the collection may be contingent on this. It may also be contingent on the other members of the collection.

If you're going to use the new Mastodon #Collections feature there are a few things you should know before you consent for your account to be included in a collection.

(source: I've been experimenting with the API for the past month to implement it in #pachli)

RE: https://mastodon.bsd.cafe/@stefano/116237813725167002

I'm where I am in my career because a lot of people did (and still do) take the time to explain things to the newcomers.

It's always nice to hear when paying that forward has helped.

RE: https://masto.es/@cavalleto/115820657000569516

@cheeaun Does Phanpy let people quote posts and add attachments? I thought Mastodon didn't allow that.

If you're waiting for the #tusky timeline rewrite before new features arrive then you will probably enjoy #pachli, https://pachli.app.

You're already familiar with the UI, and there are countless quality of life improvements.

Well, not literally countless. I've listed some of them at https://gist.github.com/nikclayton/2244d5ce547706983ca9f79a76ebbabd

And #quoteposts at the end of this month.

@cstross Hi, just flagging -- in case you weren't aware -- that while www.antipope.org is available over https, your Atom feed (https://www.antipope.org/charlie/blog-static/atom.xml) references everything over plain http. Also, the `head` in each page appears to load all resources, including Javascript, over plain http too.

Hey @Codeberg - do you have a budget / financial plan / runway stats somewhere?

I see lots of projects migrating to your service, and before I consider that I want to have some idea of the stability of the organisation I'm moving to. The tech field is littered with organisations with big ideas that ran out of money.

I read e.g. https://blog.codeberg.org/letter-from-codeberg-looking-into-2025.html, but couldn't find anything that discussed Codeberg's financial situation and plans. Is that something only available to members?

[This is very likely only going to be of interest to Mastodon client developers, so a very small niche]

There are some very odd configuration choices exposed by Mastodon/Mastodon-like servers. Some are probably errors, others desperate cries for attention.

https://gist.github.com/nikclayton/ebba4c76261b377094d31fe72f503ec9

I've posted an update re the #tusky invoices and financial situation at https://write.as/nikclayton/update-on-1-stepping-back

This addresses notes from:

at-kevin@km6g.us, at-datatitian@social.coop, at-UncivilServant@med-mastodon.com, at-wraptile@fosstodon.org, at-whvholst@eupolicy.social, at-maloki@rage.love

Thank you for providing commentary or asking questions.

[Edit: Replaced the leading "@" in user names with "at-", so they are not notified on replies that do not edit the user list]

I **do not** have a conflict of interest; I have not taken money from the #Tusky project in the past, I do not have any open expenses with the project now, and none of my income is remotely related to the project or any competing projects.

I'll be reading any replies with questions, collating the questions directed at me, and then writing a single response addressing all of them (or one per day if the questions run over multiple days).

I am stepping back from the #Tusky project with immediate effect.

I discovered severe lapses in how the Tusky project's donations (received via #OpenCollective) were being handled. When I reported those to the project's private "Tusky Contributors" Matrix channel the financial admins tone policed the feedback, refused to engage with the concerns I and others raised, and demanded the discussion be stopped.

There is too much detail for a thread, so please read https://write.as/nikclayton/stepping-back-from-the-tusky-project.

Viewing images in #Tusky is about to get better, https://github.com/tuskyapp/Tusky/pull/3894