at://did:plc:44ybard66vv44zksje25o7dz/sh.tangled.feed.comment/3myb6o2qjtx22

Back to Collection

Record JSON

{
  "$type": "sh.tangled.feed.comment",
  "body": {
    "$type": "sh.tangled.markup.markdown",
    "original": "[`proposal.md:104`](/opensocial.group/proposal/pulls/4/round/0#proposal.md-N104)\nI'm hoping that there will be multiple ways to support group account creation, including flows which do not require bouncing out of the app into an OAuth flow on the group host web interface. This isn't important for \"serious\" community accounts, but it is important for casual situations where friction would be a barrier.\nI'm a little concerned that the way this is written it implies that this is the one true correct way to do it.\nI do think it might be worth saying that group hosts \"SHOULD\" implement an OAuth flow like this for interoperability. But that other flows are also fine.",
    "text": "[`proposal.md:104`](/opensocial.group/proposal/pulls/4/round/0#proposal.md-N104)\nI'm hoping that there will be multiple ways to support group account creation, including flows which do not require bouncing out of the app into an OAuth flow on the group host web interface. This isn't important for \"serious\" community accounts, but it is important for casual situations where friction would be a barrier.\nI'm a little concerned that the way this is written it implies that this is the one true correct way to do it.\nI do think it might be worth saying that group hosts \"SHOULD\" implement an OAuth flow like this for interoperability. But that other flows are also fine."
  },
  "createdAt": "2026-10-20T01:37:18+03:00",
  "pullRoundIdx": 0,
  "subject": {
    "cid": "bafyreifiw5nllr5jl3fm5eugchxs3aubbwvwqg3hv6eyaveoqrws2qnzce",
    "uri": "at://did:plc:epbi6paber3mxm7237xkwvj5/sh.tangled.repo.pull/3mxhnuffagg22"
  }
}