Notices by mike (mike@unfediverse.com)
-
Embed this notice
mike (mike@unfediverse.com)'s status on Sunday, 04-Sep-2022 15:46:37 JST 
mike
The comment policy is provided in the activity using an ad hoc field 'commentPolicy'; since nobody else has stepped up to the plate with anything better. It's documented in our FEDERATION.md . You can try to inter-operate or propose something better. You can also ignore it or even remain in the dark that comment permissions exist in the fediverse. We don''t care. We're not accepting your comments if they violate our local policy or our members' permissions. -
Embed this notice
mike (mike@unfediverse.com)'s status on Thursday, 25-Aug-2022 07:02:11 JST
mike
Methinks you should read the spec again. Implementations are free to ignore extensions they don't know about. The spec actually recommends that if you wish to provide an extension type such as a "Frumble" that can gracefully devolve into and be displayed as a "Note" you identify it as a [ "Note", "Frumble" ]. Some projects will try and display this. If you do this backward and call it a [ "Frumble", "Note" ] or just call it a "Frumble", and we have no idea what a Frumble represents, we've every right to throw it into the bitbucket. -
Embed this notice
mike (mike@unfediverse.com)'s status on Tuesday, 16-Aug-2022 22:59:17 JST
mike
I just find it all amusing. The fediverse of today is finally beginning to catch up with the fediverse of a decade ago. Meanwhile we're working on things you'll probably discover a decade from now once other projects "invent" it, because if we do something novel and interesting nobody will ever notice or care.
All GNU social JP content and data are available under the