A small tool to view real-world ActivityPub objects as JSON! Enter a URL
or username from Mastodon or a similar service below, and we'll send a
request with
the right
Accept
header
to the server to view the underlying object.
{
"@context": [
"https://www.w3.org/ns/activitystreams",
{
"ostatus": "http://ostatus.org#",
"atomUri": "ostatus:atomUri",
"inReplyToAtomUri": "ostatus:inReplyToAtomUri",
"conversation": "ostatus:conversation",
"sensitive": "as:sensitive",
"toot": "http://joinmastodon.org/ns#",
"votersCount": "toot:votersCount",
"litepub": "http://litepub.social/ns#",
"directMessage": "litepub:directMessage"
}
],
"id": "https://infosec.exchange/users/jerry/statuses/110952823935549318",
"type": "Note",
"summary": null,
"inReplyTo": null,
"published": "2023-08-25T23:22:16Z",
"url": "https://infosec.exchange/@jerry/110952823935549318",
"attributedTo": "https://infosec.exchange/users/jerry",
"to": [
"https://www.w3.org/ns/activitystreams#Public"
],
"cc": [
"https://infosec.exchange/users/jerry/followers"
],
"sensitive": false,
"atomUri": "https://infosec.exchange/users/jerry/statuses/110952823935549318",
"inReplyToAtomUri": null,
"conversation": "tag:infosec.exchange,2023-08-25:objectId=90074409:objectType=Conversation",
"content": "<p>So far, I am pretty impressed by the simplicity of fastly. </p><p>I am contemplating a major refactoring that is focused on performance. I believe I will consolidate down from the 13 servers today to 4 larger servers colocated on a 10gbps network, and moving back to a local minio storage provider. </p><p>The 16 core DB server is regularly saturating, so will likely go with one of the 64 core sapphire rapids servers for that and redis, and another for puma. </p><p>Fastly seems like a much better solution than setting up a bunch of nginx reverse proxies around the world, and so far it seems to be working really well.</p>",
"contentMap": {
"en": "<p>So far, I am pretty impressed by the simplicity of fastly. </p><p>I am contemplating a major refactoring that is focused on performance. I believe I will consolidate down from the 13 servers today to 4 larger servers colocated on a 10gbps network, and moving back to a local minio storage provider. </p><p>The 16 core DB server is regularly saturating, so will likely go with one of the 64 core sapphire rapids servers for that and redis, and another for puma. </p><p>Fastly seems like a much better solution than setting up a bunch of nginx reverse proxies around the world, and so far it seems to be working really well.</p>"
},
"attachment": [],
"tag": [],
"replies": {
"id": "https://infosec.exchange/users/jerry/statuses/110952823935549318/replies",
"type": "Collection",
"first": {
"type": "CollectionPage",
"next": "https://infosec.exchange/users/jerry/statuses/110952823935549318/replies?only_other_accounts=true&page=true",
"partOf": "https://infosec.exchange/users/jerry/statuses/110952823935549318/replies",
"items": []
}
},
"likes": {
"id": "https://infosec.exchange/users/jerry/statuses/110952823935549318/likes",
"type": "Collection",
"totalItems": 56
},
"shares": {
"id": "https://infosec.exchange/users/jerry/statuses/110952823935549318/shares",
"type": "Collection",
"totalItems": 1
}
}