Our Elgg HybridAuth has crossposting feature.

Currently, crossposting is only available for blogs, but we can add it to The Wire as well.

Using Twitter API is no longer free. So, even if you get the Elgg site to cross-post Wire postings to Twitter, you'll probably need to pay a monthly fee to be allowed to add your postings to you Twitter account. Problem might be if Elgg site users want to add their Wire postings to their Twitter accounts. The would need to pay for Twitter API usage each on their own!!!

And maybe before thinking about (and paying someone for) letting someone updating the Twitter plugin to work on Elgg 4 AND with the Twitter API fees you might consider if you trust Mr E. Musk enough to NOT change his mind tomorrow once more and changing the Twitter API again for not allowing any posts getting added from external sources at all. Or Twitter closing once and for all..

@iionly

Using Twitter API is no longer free

Twitter Standart API is still free (yet).

Problem might be if Elgg site users want to add their Wire postings to their Twitter accounts. The would need to pay for Twitter API usage each on their own!!!

It's not correct. Only the site owner as the Twitter app creator will be charged for increasing the rates limit or using the Enterprise/Premium APIs. Users allow access to their accounts only to Twitter app.
You can check it in this Elgg app.

you might consider if you trust Mr E. Musk

That's right. For these reasons, we suggest that our users use Mastodon instead.

So no related additional activity in the access logs?

Maybe it's a cron job (maybe a bit of a weird time, maybe the server has a different timezone). It looks like some kind of spam login detection.

But from just the query alone it's very hard to tell (also because it's a Elgg <= 2.3 query).

But imagine a case scenario where I am creating an entity for internal need only - this entity is never exposed to the end user - (no user will be able to edit / delete / view / comment / like on this entity). In such case what's the use of subscribing the user to this entity?

Good point.

I like your suggestion of a capability.

For now you can always listen to the 'create', 'relationship' hook. You can than check if it's a notification relationship with your entity and return false.

Feature request https://github.com/Elgg/Elgg/issues/14301

Thanks for considering the feature request, and the clue Jerome :)