cc @evan relating to earlier #TagsPub discussion we had on the matter.

This bot is already combining logic, has multiple 'profle logic' tags. Dunno if "NoBots" is also already common protocol-decaying practice.

Maybe a solution might be that an #ActivityPub bot actor - OT: which I'd personally perhaps had chosen to be Application, not Service actors - would have a botFlags property. Simple to implement, and #FEP that.

More involved but also much more versatile might be a "Botiquette" as:Profile, or even a bots:Botiquette type, and a namespace to register them at, and where others may find what they mean and how they operate exactly.

#NoBots #nobot #fedi22 #NoTagsPub #Botiquette

@evan 2x protocol decay in a row? 🤔

Is there any formalized approach on choosing actor type, or did you express your personal app-centric preference? Is there anything not app-centric to having a max. amount of app-centric 'profile fields'? Genuine questions. Am I holding it wrong when I say 'app-centric'?

@smallcircles you use an idiosyncratic jargon sometimes and that makes it hard to talk to you.

Evolution of a protocol is not "decay". Nor is the Postel principle. Learning and adapting protocols and data types to new situations or creating extensions is success, not failure.

@evan

What I thought to do the other day we had the discussion, but didn't have time for, was create the hypotethical future Mastodon profile of my account, where some technical construct of tags took all the available profile bio characters leaving just enough to say "Hi, I am Arnold (out or chars)" followed by a combinatorial mismash of app-specific profile-logic I require to have to operate my account on the fedi to work well.

It is protocol decay. AP let's you express that kinda logic, and it was made to convey these things.

@evan

It is both protocol decay as well as "misconception" in the way Rich Hickey meant in his Hammock Driven Development talk.

The longer such practices are allowed to exist, the more inertia and reluctance to there is to come to better practices, and the question about evolution is again Im Frage.

"Look we all have bio profile processors in our apps, and now you are telling us to drop that, just to make it look more like activitypub? We can see that it may be an improvement, but this is a past station now."

@evan

There are more aspects to evolution. When I use the word, it is from the full scope and against the principles of SX methodology I am working on, which holistically considers the entirety of the ecosystem as a whole.

The fediverse ecosystem evolved to have most day to day conversation on microblog channels.

But if those are ephemeral and fleety, fragmented, where before the discussions on more cohesive commucation hubs that kept an archive of what was said in one place, from that perspective and measured against power that is now lost, one may conclude devolution to place in hindsight.

@evan

To me it is very sad this shift to fragmented microblog being the source of truth to discuss de-facto standards and upcoming potential post-facto interoperabiliy tech debt, in a communication medium where only you and I may ever read our discussion, and it is gone in timeline history the next day.

@evan it was more a general remark, as I am having these kinds of discussions all over the fedi place now, and always to people who miss context on what I sent just previously in another branch or toot thread. I sighed about the general fragmentation of things, where more cohesion is not just a boon, but perhaps a requirement for healthy standard evolution.

In my brainstorm encouragement about Grassroots standardization processes, and my line of thinking this could be tackled property, and on fedi space, integrated in the social fabric.

Other than that a forum or issue/discussion tracker might work for the time being.