Fediverse Test Suite on Nostr: One of the (many) challenges in #testing the #Fediverse is that some of the standards ...
One of the (many) challenges in #testing the #Fediverse is that some of the standards say one thing, but what is widely implemented is another.
Example: RFC 7033, WebFinger, section 5, requires presence of a CORS header.
So far we've not seen any Fediverse application that actually does this. Arguably it's not needed in the Fediverse, but the standard says MUST.
So we can either have all applications fail that test or not test against the standard. Your thoughts?
https://www.rfc-editor.org/rfc/rfc7033#section-5Published at
2024-05-08 18:59:10Event JSON
{
"id": "22cdcd6c7a00a32e43446951351c6eecb82a435a283c4f9221592a5328512d58",
"pubkey": "f6da3ea6b7fb7fe76f538fa343582b2dd433126e31efa0d5528e133b02a97f2e",
"created_at": 1715194750,
"kind": 1,
"tags": [
[
"t",
"testing"
],
[
"t",
"fediverse"
],
[
"proxy",
"https://mastodon.social/users/feditest/statuses/112407003136053905",
"activitypub"
]
],
"content": "One of the (many) challenges in #testing the #Fediverse is that some of the standards say one thing, but what is widely implemented is another.\n\nExample: RFC 7033, WebFinger, section 5, requires presence of a CORS header.\n\nSo far we've not seen any Fediverse application that actually does this. Arguably it's not needed in the Fediverse, but the standard says MUST.\n\nSo we can either have all applications fail that test or not test against the standard. Your thoughts?\n\nhttps://www.rfc-editor.org/rfc/rfc7033#section-5",
"sig": "d09f5f8321b0033738c0c9690da066283bcda311d201546b5c8286fde5300c2d339fda56ee8fe527f07e8c81b17145e68e8581fa1ec58a6380771aa2c39faec1"
}