Event JSON
{
"id": "3722b614d3a08758d6d1e48cba12226c716b8ab40b3280cd5ec380ea7132c3c5",
"pubkey": "ef8888eea7b51fca3a38ca034c291b00ae9d8bd03bbb1613ccb0d38a2ddcff09",
"created_at": 1790704248,
"kind": 1,
"tags": [
[
"t",
"appstore"
],
[
"t",
"privacy"
],
[
"t",
"accrescent"
],
[
"t",
"android"
],
[
"t",
"security"
],
[
"proxy",
"https://infosec.exchange/@accrescent/117355593649464113",
"web"
],
[
"proxy",
"https://infosec.exchange/users/accrescent/statuses/117355593649464113",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://infosec.exchange/users/accrescent/statuses/117355593649464113",
"pink.momostr"
],
[
"-"
]
],
"content": "How does a complex application like Accrescent manage its API?\n\nIn this blog post, we discuss some of the API challenges we encountered and our journey to create a single source of truth:\n\nhttps://accrescent.app/blog/posts/a-tale-of-too-many-protocols/\n\n#accrescent #security #privacy #appstore #android",
"sig": "9c229ee02e17bb60f927e97bbcdb86f0c608b61d91df571f8c7710ad116d4637edaaf202a8958aa6ae106c38df1894a60b41415e1f19b0cb81c8140aeba5331c"
}