>Servers MUST NOT publish incorrect usage statistics.
Pokemon GoToSocial enters the chat
Pokemon GoToSocial enters the chat
Timeline
Post
Remote status
Context
2
@silverpill I don't wanna pollute activitypub.rocks thread for some W3C orbiter to get mad, so here goes.
>I don't like "incorrect" here, but haven't found a better word yet.
"Intentionally skewed" or "intentionally incorrect" mean similar things. As far as I understand, you want to prevent the GTS way of crying about indexers all the time to the point of poisoning data. That case would be covered there. To be pedantic, a bug would technically be FEP-compliant since it is not intentional, but once the bug is reported, or maintainers are aware of it and refuse to fix it, it becomes intentional.
>There is a FEP about advertising capabilities using metadata (FEP-9fde), I want to discourage this practice
Do you have a valid alternative? Sticking fields into Actors is not it since those aren't instance-wide.
>On the other hand, I can't think of any good reason to rely on software.
misskey.io did exactly that when they wrongly thought Pleroma's MediaProxy fetching their millions of emojis was causing them issues (it was a different Pleroma issue). If you need to filter data instance-wide based on software version in case of buggy behavior causing you issues/known vulnerabilities allowing breakage of trust on the network like account impersonation etc. this can be very useful when the version is correct.
RE: https://mitra.social/objects/019c6d68-fa49-1614-56bc-525473060337
>I don't like "incorrect" here, but haven't found a better word yet.
"Intentionally skewed" or "intentionally incorrect" mean similar things. As far as I understand, you want to prevent the GTS way of crying about indexers all the time to the point of poisoning data. That case would be covered there. To be pedantic, a bug would technically be FEP-compliant since it is not intentional, but once the bug is reported, or maintainers are aware of it and refuse to fix it, it becomes intentional.
>There is a FEP about advertising capabilities using metadata (FEP-9fde), I want to discourage this practice
Do you have a valid alternative? Sticking fields into Actors is not it since those aren't instance-wide.
>On the other hand, I can't think of any good reason to rely on software.
misskey.io did exactly that when they wrongly thought Pleroma's MediaProxy fetching their millions of emojis was causing them issues (it was a different Pleroma issue). If you need to filter data instance-wide based on software version in case of buggy behavior causing you issues/known vulnerabilities allowing breakage of trust on the network like account impersonation etc. this can be very useful when the version is correct.
RE: https://mitra.social/objects/019c6d68-fa49-1614-56bc-525473060337
@silverpill
Also on the note of FEP compliance. Is there some test data for compliance testing for some of them? lain worked on something similar from fedidev.fun which is now dead I think. Eventually in the future I would like to make a FEDERATION.md that is not created just by winging it from reading the specs.
Also on the note of FEP compliance. Is there some test data for compliance testing for some of them? lain worked on something similar from fedidev.fun which is now dead I think. Eventually in the future I would like to make a FEDERATION.md that is not created just by winging it from reading the specs.
Replies
1
>Is there some test data for compliance testing for some of them?
Yes, I wrote "feature" files for some of my FEPs:
https://codeberg.org/fediverse/fep/src/branch/main/fep/8b32/fep-8b32.feature
The idea belongs to @helge, see also https://codeberg.org/helge/fediverse-features
I think in many cases JSON schemas can be added too https://codeberg.org/funfedidev/schemas/issues/18
>fedidev.fun which is now dead I think
It's https://funfedi.dev