@rimu@piefed.social@rimu@mastodon.nzoss.nz c2pa is for a whole lot more than just AI detection, it's full provenance embedded — stream.place uses it iirc for adding all the licensing data to live streams
@rimu on "Tokens used by mobile apps can be set to expire, using the JWT_EXPIRY_DAYS environment variable" let me know if you need any review from an OAuth perspective, happy to try to give info/feedback!
@jdlh oh, and it gets even worse with this tidbit of history from @by_caballero
“P.S. Adding to the tech debt/specification backlog, preferredUsername was never in ActivityStreams, it was yolo'd/retconned, and One Does Not Simply yolo new terms into the ontology without the whole W3C normative 3-step.”
@jdlh It does beget the question: how do you standardise to fix a problem in something you don't technically have? Handles are a design construct in the fediverse and not actually a protocol concept.
@thisismissem is a webfinger resource but doesn't appear in Actor objects, and is instead constructed from preferredUsername and the webfinger domain. Handles don't exist in ActivityPub, but almost all ActivityPub software has some concept of them.
@ernest you could always schedule the deletion? Like mark the account as scheduled for deletion so you can't post or anything, but you can access this page to cancel the scheduled deletion.
Involving a second factor of email for confirmation also sounds wise here
@ernest Also careful with that “suspend account" language, as it means a very different thing in a trust & safety context across the fediverse — perhaps “pause account” or "take a break”?
@rimu@piefed.social @rimu@mastodon.nzoss.nz c2pa is for a whole lot more than just AI detection, it's full provenance embedded — stream.place uses it iirc for adding all the licensing data to live streams
@rimu on "Tokens used by mobile apps can be set to expire, using the JWT_EXPIRY_DAYS environment variable" let me know if you need any review from an OAuth perspective, happy to try to give info/feedback!
@jdlh oh, and it gets even worse with this tidbit of history from @by_caballero
“P.S. Adding to the tech debt/specification backlog,
preferredUsernamewas never in ActivityStreams, it was yolo'd/retconned, and One Does Not Simply yolo new terms into the ontology without the whole W3C normative 3-step.”@jdlh It does beget the question: how do you standardise to fix a problem in something you don't technically have? Handles are a design construct in the fediverse and not actually a protocol concept.
@thisismissem is a webfinger resource but doesn't appear in Actor objects, and is instead constructed from preferredUsername and the webfinger domain. Handles don't exist in ActivityPub, but almost all ActivityPub software has some concept of them.
cc @jdlh see also https://www.w3.org/community/reports/socialcg/CG-FINAL-apwf-20240608/#reverse-discovery
@poVoq @fediverse there's also a proposal (from google) for IdP Initiated FedCM, instead of relying party initiated
@ernest enjoy your holidays!
@ernest Will the spoiler system also be compatible with Mastodon? This would be very good to have.
(or, alternatively, can we get a FEP for a proper spoiler system other than using the
summaryfield?)@ernest as always, feel free to reach out for help on moderation tooling design.
@ernest you could always schedule the deletion? Like mark the account as scheduled for deletion so you can't post or anything, but you can access this page to cancel the scheduled deletion.
Involving a second factor of email for confirmation also sounds wise here
@ernest Also careful with that “suspend account" language, as it means a very different thing in a trust & safety context across the fediverse — perhaps “pause account” or "take a break”?
@ernest Why does the admin need to be told you want to delete your account? Why isn't it self-service?