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",
"Hashtag": "as:Hashtag"
}
],
"id": "https://infosec.exchange/users/heatsink/statuses/114687693075014064",
"type": "Note",
"summary": null,
"inReplyTo": "https://infosec.exchange/users/heatsink/statuses/114679286819251322",
"published": "2025-06-15T13:48:36Z",
"url": "https://infosec.exchange/@heatsink/114687693075014064",
"attributedTo": "https://infosec.exchange/users/heatsink",
"to": [
"https://www.w3.org/ns/activitystreams#Public"
],
"cc": [
"https://infosec.exchange/users/heatsink/followers"
],
"sensitive": false,
"atomUri": "https://infosec.exchange/users/heatsink/statuses/114687693075014064",
"inReplyToAtomUri": "https://infosec.exchange/users/heatsink/statuses/114679286819251322",
"conversation": "tag:infosec.exchange,2025-06-14:objectId=281123574:objectType=Conversation",
"content": "<p>After entirely too much research on how the Postgres container wants the storage to work, I ended up having to use a plain NFS mount for my persistent volume claim.</p><p>Under the hood, persistent volumes are hosted on my NAS anyways, but the UserID/GroupID permissions were not right for Postgres, and thus the container didn't want to work. I do map the NFS share users to admin, but Postgres wants 999 (and only 999) for its UID/GID. I might need to change that at some point in the future on whatever my next storage is.</p><p>Thankfully no documents were actually lost from Paperless, since it keeps copies of all the original docs and I could just reimport/retag them. Once I get through tagging all of them, I will work on the backup process and testing a restore.</p><p><a href=\"https://infosec.exchange/tags/homelab\" class=\"mention hashtag\" rel=\"tag\">#<span>homelab</span></a> <a href=\"https://infosec.exchange/tags/selfhosted\" class=\"mention hashtag\" rel=\"tag\">#<span>selfhosted</span></a> <a href=\"https://infosec.exchange/tags/linux\" class=\"mention hashtag\" rel=\"tag\">#<span>linux</span></a> <a href=\"https://infosec.exchange/tags/kubernetes\" class=\"mention hashtag\" rel=\"tag\">#<span>kubernetes</span></a></p>",
"contentMap": {
"en": "<p>After entirely too much research on how the Postgres container wants the storage to work, I ended up having to use a plain NFS mount for my persistent volume claim.</p><p>Under the hood, persistent volumes are hosted on my NAS anyways, but the UserID/GroupID permissions were not right for Postgres, and thus the container didn't want to work. I do map the NFS share users to admin, but Postgres wants 999 (and only 999) for its UID/GID. I might need to change that at some point in the future on whatever my next storage is.</p><p>Thankfully no documents were actually lost from Paperless, since it keeps copies of all the original docs and I could just reimport/retag them. Once I get through tagging all of them, I will work on the backup process and testing a restore.</p><p><a href=\"https://infosec.exchange/tags/homelab\" class=\"mention hashtag\" rel=\"tag\">#<span>homelab</span></a> <a href=\"https://infosec.exchange/tags/selfhosted\" class=\"mention hashtag\" rel=\"tag\">#<span>selfhosted</span></a> <a href=\"https://infosec.exchange/tags/linux\" class=\"mention hashtag\" rel=\"tag\">#<span>linux</span></a> <a href=\"https://infosec.exchange/tags/kubernetes\" class=\"mention hashtag\" rel=\"tag\">#<span>kubernetes</span></a></p>"
},
"attachment": [],
"tag": [
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/homelab",
"name": "#homelab"
},
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/selfhosted",
"name": "#selfhosted"
},
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/linux",
"name": "#linux"
},
{
"type": "Hashtag",
"href": "https://infosec.exchange/tags/kubernetes",
"name": "#kubernetes"
}
],
"replies": {
"id": "https://infosec.exchange/users/heatsink/statuses/114687693075014064/replies",
"type": "Collection",
"first": {
"type": "CollectionPage",
"next": "https://infosec.exchange/users/heatsink/statuses/114687693075014064/replies?min_id=114687705338146490&page=true",
"partOf": "https://infosec.exchange/users/heatsink/statuses/114687693075014064/replies",
"items": [
"https://infosec.exchange/users/heatsink/statuses/114687705338146490"
]
}
},
"likes": {
"id": "https://infosec.exchange/users/heatsink/statuses/114687693075014064/likes",
"type": "Collection",
"totalItems": 4
},
"shares": {
"id": "https://infosec.exchange/users/heatsink/statuses/114687693075014064/shares",
"type": "Collection",
"totalItems": 0
}
}