IMO some things that would help tremendously and that would be good to prioritize, ways:

* Of having a persistent identifier that is decoupled from your server. Whether this looks like the current #VC and #DID proposals is less important than that the decoupling takes place.

* Of sharing and pooling moderation, load, storage, privacy, and security resources (see my previous discussion of #APAF/#ActivityPubApplicationFirewall or #APRL).

Justice Arun Mishra’s Final ‘Gift’ of Rs 8,000 Crore to Adani

On August 31, 2020, a Supreme Court bench headed by Justice Arun Kumar Mishra, that included Justices Vineet Saran and M R Shah, ruled in favour of a company in the Adani group in a dispute with public sector power distribution companies in Rajasthan. The verdict, issued three days before Justice Mishra retired from the court on September 2, has granted Adani Power Rajasthan Limited (APRL) – which owns a 1,320 megawatt capacity thermal power station in Kawai, Baran district – “compensatory tariffs” worth over Rs 5,000 crore and penalties and interest payments of nearly Rs 3,000 crore.

#archives #ArunMishra #AdaniGroup #AdaniPower #APRL #adani #VineetSaran #MRShah #rajasthan #SupremeCourt #IndianJudiciary #GautamAdani #gujarat #CronyCapitalism #PSUs #business #industry #billionaires #india

https://www.newsclick.in/Justice-Arun-Mishra%27s-Final-Gift-of-8000-Crore-to-Adani

Kind of my vision here for an #ActivityPub DSL with #APRL/ #LcCircle is the ability to say things like…

allow {
authenticated_request(X)
} route("actor:circle.mydomain.example/circle/enqueue") {
rule(follow_request(Requester, Requestee, X))) {
follows(Requestee, Requester)
} annotate {
X.annotations += Annotation(
"follow_status": FollowStatus.FollowsRequester
)
}
}

Probably not with that exact syntax, but that's the idea.

Basically a rules engine let's me make declarations like "I am seeing this message, what do I want to do with it for handling" without writing eight million individual handlers.

If this were a serious project I would go out and grab someone else's and call it a day (or maybe #rego), but because this is a toy and I'm experimenting I'm going to create a little DSL—based on #datalog—and see if I can use that to implement some ideas in this space. I'll call it #APRL or #ActivityPubRulesLanguage.