silverpill on Nostr: nprofile1q…3kzgj nprofile1q…v3dhj Most services have hard-coded lists of ...
nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqh73s7j2mdwzzv6a2fm9tfjchlaw4r7a59pfl0keqrahfja2k3stqf3kzgj (nprofile…kzgj) nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqku30mphs68tg30c4jj0d80g698resvue70hhrvnawxvdfaq4p0uspv3dhj (nprofile…3dhj) Most services have hard-coded lists of supported types, and will drop any object with unusual type like MusicRelease (see FunFedi data, only Mitra accepts objects with arbitrary types, because it uses duck typing).
>I think I was trying to follow FunkWhale’s model, to be as compatible with it as possible. But the two object types probably will be more trouble than they’re worth.
Can it handle [Album, Article]? If so, that might be a good argument in favor of that value.
Their docs describe Album object, but say type should be a string.
>I think I was trying to follow FunkWhale’s model, to be as compatible with it as possible. But the two object types probably will be more trouble than they’re worth.
Can it handle [Album, Article]? If so, that might be a good argument in favor of that value.
Their docs describe Album object, but say type should be a string.