I opted not to comment on GitHub about the proposed community attribute addition of local-only posting (sort of like moderator-only posting to a community now).
ADD COLUMN posting_restricted_to_local boolean
I encourage the project as a whole to move away from these single-bit flags, aka booleans. I suggest a SMALLINT postgresql type and define 0 or 1 for values. And name the field a little more generic such as “posting_restrictions” and let 1 = home community only.
Down the road… lemmy may have the ability to have private members-only communities, and a multi-value field could control different behaviors (0 = normal as Lemmy is today, 1 = home instance only, 2 = approved members only).
It is taking 20 source code changes to lemmy_server to add one single boolean. !multipass@bulletintree.com has the same level of concern when adding features… 20 source files.
I opted not to comment on GitHub about the proposed community attribute addition of local-only posting (sort of like moderator-only posting to a community now).
I encourage the project as a whole to move away from these single-bit flags, aka booleans. I suggest a SMALLINT postgresql type and define 0 or 1 for values. And name the field a little more generic such as “posting_restrictions” and let 1 = home community only.
Down the road… lemmy may have the ability to have private members-only communities, and a multi-value field could control different behaviors (0 = normal as Lemmy is today, 1 = home instance only, 2 = approved members only).
It is taking 20 source code changes to lemmy_server to add one single boolean. !multipass@bulletintree.com has the same level of concern when adding features… 20 source files.