<![CDATA[#AntiPatterned™]]>™

Do NOT create out-of-bound custom and app-centric mechanisms that define new and expected behavior on protocol level.

Link Preview Image
#Botiquette

fediverse-ideas - Ideas for new applications and services on the Fediverse.

favicon

Codeberg.org (codeberg.org)

Link Preview Image
]]>https://citiverse.it/topic/0eea6837-f276-45eb-b6fc-85b862015a3e/antipatternedRSS for NodeSun, 26 Apr 2026 03:04:15 GMTMon, 13 Apr 2026 01:34:39 GMT60<![CDATA[Reply to #AntiPatterned™ on Mon, 13 Apr 2026 12:00:06 GMT]]>@smallcircles Anyway, yes, the way the extra fields work and their limited number is a product decision by Mastodon.

]]>https://citiverse.it/post/https://cosocial.ca/users/evan/statuses/116397284183434003https://citiverse.it/post/https://cosocial.ca/users/evan/statuses/116397284183434003Mon, 13 Apr 2026 12:00:06 GMT<![CDATA[Reply to #AntiPatterned™ on Mon, 13 Apr 2026 11:56:36 GMT]]>@smallcircles I'm not sure what you mean by app-centric. I think you mean Mastodon-centric, that is, how do we work around the Mastodon software and the Mastodon team? I agree that it is a frustrating part of working on the Fediverse.

]]>https://citiverse.it/post/https://cosocial.ca/users/evan/statuses/116397270457321343https://citiverse.it/post/https://cosocial.ca/users/evan/statuses/116397270457321343Mon, 13 Apr 2026 11:56:36 GMT<![CDATA[Reply to #AntiPatterned™ on Mon, 13 Apr 2026 11:51:24 GMT]]>@smallcircles Long term, I think it would be great to have a structured way to add properties and collections to actors that don't depend on the server software.

So, I could say, if you don't want tags.pub to boost your content, set the `https://tags.pub/ns/noTagsPub` property on your actor object to true. Or have a collection of allowed tags, or denied tags, or object types to boost, or object types not to boost.

]]>https://citiverse.it/post/https://cosocial.ca/users/evan/statuses/116397249923323727https://citiverse.it/post/https://cosocial.ca/users/evan/statuses/116397249923323727Mon, 13 Apr 2026 11:51:24 GMT<![CDATA[Reply to #AntiPatterned™ on Mon, 13 Apr 2026 11:44:06 GMT]]>@smallcircles I think the question you are asking is how we let people express their preferences for interacting with different types of automated actors. I think the NoBots solution is fine; it reminds me of robots.txt. "indexable" and "discoverable" are also fine.

]]>https://citiverse.it/post/https://cosocial.ca/users/evan/statuses/116397221235725568https://citiverse.it/post/https://cosocial.ca/users/evan/statuses/116397221235725568Mon, 13 Apr 2026 11:44:06 GMT<![CDATA[Reply to #AntiPatterned™ on Mon, 13 Apr 2026 11:35:05 GMT]]>@smallcircles when you say things are my "personal" preference, you make it sound like I am just some guy off the street. I'm not. I wrote StatusNet and pump.io. I developed OStatus, and cowrote AS2 and AP. I wrote the book about ActivityPub. My personal preferences were built into the standard a long time ago.

]]>https://citiverse.it/post/https://cosocial.ca/users/evan/statuses/116397185810626160https://citiverse.it/post/https://cosocial.ca/users/evan/statuses/116397185810626160Mon, 13 Apr 2026 11:35:05 GMT<![CDATA[Reply to #AntiPatterned™ on Mon, 13 Apr 2026 11:29:55 GMT]]>@smallcircles for choosing object types for software, I think the difference between a client and a server can be tricky, but in the case of tags.pub, everything is implemented on the server, so I think Service is a good choice. Why do you think Application?

]]>https://citiverse.it/post/https://cosocial.ca/users/evan/statuses/116397165509061123https://citiverse.it/post/https://cosocial.ca/users/evan/statuses/116397165509061123Mon, 13 Apr 2026 11:29:55 GMT<![CDATA[Reply to #AntiPatterned™ on Mon, 13 Apr 2026 11:23:36 GMT]]>@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.

]]>https://citiverse.it/post/https://cosocial.ca/users/evan/statuses/116397140642700889https://citiverse.it/post/https://cosocial.ca/users/evan/statuses/116397140642700889Mon, 13 Apr 2026 11:23:36 GMT<![CDATA[Reply to #AntiPatterned™ on Mon, 13 Apr 2026 06:40:12 GMT]]>@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'?

]]>https://citiverse.it/post/https://social.coop/users/smallcircles/statuses/116396026233864387https://citiverse.it/post/https://social.coop/users/smallcircles/statuses/116396026233864387Mon, 13 Apr 2026 06:40:12 GMT<![CDATA[Reply to #AntiPatterned™ on Mon, 13 Apr 2026 04:16:20 GMT]]>@smallcircles I think it might be possible to do something with the "extra profile fields", but we get so few by default!

]]>https://citiverse.it/post/https://cosocial.ca/users/evan/statuses/116395460574202499https://citiverse.it/post/https://cosocial.ca/users/evan/statuses/116395460574202499Mon, 13 Apr 2026 04:16:20 GMT<![CDATA[Reply to #AntiPatterned™ on Mon, 13 Apr 2026 04:15:28 GMT]]>@smallcircles thanks! Service is for servers, Application is for clients.

]]>https://citiverse.it/post/https://cosocial.ca/users/evan/statuses/116395457127255927https://citiverse.it/post/https://cosocial.ca/users/evan/statuses/116395457127255927Mon, 13 Apr 2026 04:15:28 GMT<![CDATA[Reply to #AntiPatterned™ on Mon, 13 Apr 2026 01:51:42 GMT]]>cc @evan relating to earlier 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 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 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.

]]>https://citiverse.it/post/https://social.coop/users/smallcircles/statuses/116394891862404385https://citiverse.it/post/https://social.coop/users/smallcircles/statuses/116394891862404385Mon, 13 Apr 2026 01:51:42 GMT