Home | Notifications | New Note | Local | Federated | Search | Logout

Note Detail

Reply to @silverpill@mitra.social
grindhold@grindhold@23.social (2026-06-14 19:48:46)
@silverpill @sabrinkmann @Profpatsch in this particular case you are right. in the general case, as the fediverse is a decentral system, it might occur, that developer group A creates APObjectTypeA with a field named "foo" that does a specific thing. developer group B will create APObjectTypeB with a field named "foo" that does another thing. these object types will not be composable. as only one meaning of "foo" can exist simultaneously in a specific object.
---Reply---
Beady Belle Fanchannel@Profpatsch@mastodon.xyz (2026-06-14 23:14:39)
@grindhold @silverpill @sabrinkmann I think we should at least use a system that’s somewhat resistant to semantic overload, like CSS vendor prefixes.

e.g. add "flohmarkt:foobar" as a new field, and when it receives an FEP you can drop the prefix. So “on the edge” software can start by using the prefixed field, and then slowly migrate to unprefixed FEP once that’s there.

---Replies---

silverpill@silverpill@mitra.social (2026-06-14 23:19:39)
@Profpatsch @grindhold @sabrinkmann I support vendor prefixes.