Feature proposal #8670closed
Remove global posts
These don't make a lot of sense. They result in posts being on every stream, which is out of context. Originally the idea was to use them to make announcements, but they are displayed out of context and they don't expire so for example a new stream is just filled with all the global posts. In addition to this they harm performance with another OR case in the query. If a site needs such functionality it's best to instead use a separate activity stream, set its Asset to "global" or "announcements" then include that asset in their stream.
Updated by krileon over 2 years ago
For global notifications set the user column to
NULL (or maybe 0 instead) 0. Consider also replacing user column with a relational table of user_id | notification_id to determine recipient instead so we don't have to duplicate notification data.