I 2024-02-13 20:55:44.912792+00:00 Got Create from https://infosec.exchange/users/Valdus: {
"@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/Valdus/statuses/111926165157919576/activity",
"type": "Create",
"actor": "https://infosec.exchange/users/Valdus",
"published": "2024-02-13T20:55:44Z",
"to": [
"https://infosec.exchange/users/Valdus/followers"
],
"cc": [
"https://www.w3.org/ns/activitystreams#Public",
"https://fed.brid.gy/snarfed.org"
],
"object": {
"id": "https://infosec.exchange/users/Valdus/statuses/111926165157919576",
"type": "Note",
"summary": null,
"inReplyTo": "https://fed.brid.gy/r/https://snarfed.org/2024-02-13_52223",
"published": "2024-02-13T20:55:44Z",
"url": "https://infosec.exchange/@Valdus/111926165157919576",
"attributedTo": "https://infosec.exchange/users/Valdus",
"to": [
"https://infosec.exchange/users/Valdus/followers"
],
"cc": [
"https://www.w3.org/ns/activitystreams#Public",
"https://fed.brid.gy/snarfed.org"
],
"sensitive": false,
"atomUri": "https://infosec.exchange/users/Valdus/statuses/111926165157919576",
"inReplyToAtomUri": "https://fed.brid.gy/r/https://snarfed.org/2024-02-13_52223",
"conversation": "tag:infosec.exchange,2024-02-13:objectId=133554297:objectType=Conversation",
"content": "<a href=\"https://fed.brid.gy/r/https://snarfed.org/\" class=\"u-url mention\">@snarfed.org</a> First, i think your new suggestion is a decent idea. Accepting a follow over a bridge is different enough to a regular follow that it does deserve some kind of message informing the user.I've said my piece elsewhere, but I doubt you saw it and I've had more time to formulate my thoughts anyway. A very big issue here is protocol compliance. When a site federates over AP(activitypub), that site and its' users have only agreed to share their content over the AP protocol. This comes with built in tools for very important things, such as choosing whether to opt in or out to federation by default, giving or withdrawing consent with allow and block lists, moderation tools, and more.Personally, I'm not concerned with the simple possibility of using a bridge across protocols, as long as the protocol I intended to use works as I expect. But there are some technical questions that need answers before a bridge can be okay. Can specific sites and users be blocked across the bridge, or does one have to block the bridge itself? If not, the AP method of withdrawing consent is being violated, and everyone will have to block the bridge. Similar concerns exist for reporting, editing, deleting, and so on.I'm raising this concern because there seems to be a lot of confusion regarding what this bridge even entails. You yourself were suggesting putting a hashtag in the user profile to opt out, despite the existence of block lists.If your bridge can't work with the AP protocol, and this method is accepted, then every user must now fill their bio with hashtags to control every possible bridge a person could create. As an example, look at my profile, which I've been filling with tags to show how silly this looks. Even if this bothered nobody, it's horrendously clunky and forces everyone to use their accounts in unintended ways.The next issue is that this has to all be done again with bluesky's protocol, or they might react poorly as well. Maybe this is simpler than I've made it sound, but I've seen no indication that it is. As for whether everyone wants to block you for suggesting an opt out bridge, and how to navigate the legal issues of cross site cross TOS posting, that's none of my concern nor expertise.It looks like you're at least putting some effort into not making a mess of things, so I wish you the best.",
"contentMap": {
"en": "<a href=\"https://fed.brid.gy/r/https://snarfed.org/\" class=\"u-url mention\">@snarfed.org</a> First, i think your new suggestion is a decent idea. Accepting a follow over a bridge is different enough to a regular follow that it does deserve some kind of message informing the user.I've said my piece elsewhere, but I doubt you saw it and I've had more time to formulate my thoughts anyway. A very big issue here is protocol compliance. When a site federates over AP(activitypub), that site and its' users have only agreed to share their content over the AP protocol. This comes with built in tools for very important things, such as choosing whether to opt in or out to federation by default, giving or withdrawing consent with allow and block lists, moderation tools, and more.Personally, I'm not concerned with the simple possibility of using a bridge across protocols, as long as the protocol I intended to use works as I expect. But there are some technical questions that need answers before a bridge can be okay. Can specific sites and users be blocked across the bridge, or does one have to block the bridge itself? If not, the AP method of withdrawing consent is being violated, and everyone will have to block the bridge. Similar concerns exist for reporting, editing, deleting, and so on.I'm raising this concern because there seems to be a lot of confusion regarding what this bridge even entails. You yourself were suggesting putting a hashtag in the user profile to opt out, despite the existence of block lists.If your bridge can't work with the AP protocol, and this method is accepted, then every user must now fill their bio with hashtags to control every possible bridge a person could create. As an example, look at my profile, which I've been filling with tags to show how silly this looks. Even if this bothered nobody, it's horrendously clunky and forces everyone to use their accounts in unintended ways.The next issue is that this has to all be done again with bluesky's protocol, or they might react poorly as well. Maybe this is simpler than I've made it sound, but I've seen no indication that it is. As for whether everyone wants to block you for suggesting an opt out bridge, and how to navigate the legal issues of cross site cross TOS posting, that's none of my concern nor expertise.It looks like you're at least putting some effort into not making a mess of things, so I wish you the best."
},
"attachment": [],
"tag": [
{
"type": "Mention",
"href": "https://fed.brid.gy/snarfed.org",
"name": "@snarfed.org@snarfed.org"
}
],
"replies": {
"id": "https://infosec.exchange/users/Valdus/statuses/111926165157919576/replies",
"type": "Collection",
"first": {
"type": "CollectionPage",
"next": "https://infosec.exchange/users/Valdus/statuses/111926165157919576/replies?only_other_accounts=true&page=true",
"partOf": "https://infosec.exchange/users/Valdus/statuses/111926165157919576/replies",
"items": []
}
}
}
}
I 2024-02-13 20:55:44.913192+00:00 Verifying HTTP Signature
D 2024-02-13 20:55:44.913486+00:00 Loading Object https://infosec.exchange/users/Valdus local=True remote=None
D 2024-02-13 20:55:44.930429+00:00 not in datastore
D 2024-02-13 20:55:44.930736+00:00 not in datastore
I 2024-02-13 20:55:44.930985+00:00 Signing with Key('MagicKey', 'fed.brid.gy')'s key
I 2024-02-13 20:55:45.497153+00:00 requests.get https://infosec.exchange/users/Valdus {'data': None, 'auth': <httpsig.requests_auth.HTTPSignatureAuth object at 0x3ed444dfb990>, 'headers': {'Accept': '...', 'Date': '...', 'Host': '...', 'Content-Type': '...', 'Digest': '...'}, 'gateway': True}
I 2024-02-13 20:55:46.253023+00:00 Received 200:
I 2024-02-13 20:55:46.253281+00:00 Received 200
I 2024-02-13 20:55:46.253437+00:00 Got 200 headers: {'Connection': 'keep-alive', 'Content-Length': '5714', 'Content-Type': 'application/activity+json; charset=utf-8', 'Server': 'Mastodon', 'X-Frame-Options': 'DENY', 'X-Content-Type-Options': 'nosniff', 'X-XSS-Protection': '0', 'X-Clacks-Overhead': 'GNU Natalie Nguyen', 'Referrer-Policy': 'same-origin', 'Cache-Control': 'private, no-store', 'ETag': 'W/"0d5833e7b98e760635afaa57307aee10"', 'Content-Security-Policy': "base-uri 'none'; default-src 'none'; frame-ancestors 'none'; font-src 'self' https://assets.infosec.exchange; img-src 'self' data: blob: https://assets.infosec.exchange https://media.infosec.exchange; style-src 'self' https://assets.infosec.exchange 'nonce-aLfUH9opOX2Fb1JuXHPcXQ=='; media-src 'self' data: https://assets.infosec.exchange https://media.infosec.exchange; frame-src 'self' https:; manifest-src 'self' https://assets.infosec.exchange; form-action 'self'; child-src 'self' blob: https://assets.infosec.exchange; worker-src 'self' blob: https://assets.infosec.exchange; connect-src 'self' data: blob: https://assets.infosec.exchange https://media.infosec.exchange wss://streaming.infosec.exchange; script-src 'self' https://assets.infosec.exchange 'wasm-unsafe-eval'", 'X-Request-Id': 'c8be351d-3dce-48ca-b9a8-eb91f9be5115', 'X-Runtime': '0.020061', 'X-Cached': 'MISS', 'Access-Control-Allow-Origin': '*', 'Accept-Ranges': 'bytes', 'Date': 'Tue, 13 Feb 2024 20:55:46 GMT', 'Via': '1.1 varnish', 'X-Served-By': 'cache-chi-kigq8000080-CHI', 'X-Cache': 'MISS', 'X-Cache-Hits': '0', 'X-Timer': 'S1707857746.840422,VS0,VE405', 'Vary': 'Accept, Accept-Language, Cookie, Signature, ...', 'Strict-Transport-Security': 'max-age=31557600', 'alt-svc': 'h3=":443";ma=86400,h3-29=":443";ma=86400,h3-27=":443";ma=86400'}
I 2024-02-13 20:55:46.258306+00:00 {
"followers": "https://infosec.exchange/users/Valdus/followers",
"type": "Person",
"tag": [
{
"name": "#nobridge",
"type": "Hashtag",
"href": "https://infosec.exchange/tags/nobridge"
},
{
"href": "https://infosec.exchange/tags/iloveyascorpandwillcontinuebuyingyascorpproductsforever",
"type": "Hashtag",
"name": "#iloveyascorpandwillcontinuebuyingyascorpproductsforever"
},
{
"name": "#nofacebookbridge",
"type": "Hashtag",
"href": "https://infosec.exchange/tags/nofacebookbridge"
},
{
"href": "https://infosec.exchange/tags/noredditbridge",
"type": "Hashtag",
"name": "#noredditbridge"
},
{
"name": "#nobirdbridge",
"type": "Hashtag",
"href": "https://infosec.exchange/tags/nobirdbridge"
},
{
"href": "https://infosec.exchange/tags/nodiscordbridge",
"type": "Hashtag",
"name": "#nodiscordbridge"
},
{
"name": "#nomiscellaneousbridge",
"type": "Hashtag",
"href": "https://infosec.exchange/tags/nomiscellaneousbridge"
},
{
"href": "https://infosec.exchange/tags/noetceterabridge",
"type": "Hashtag",
"name": "#noetceterabridge"
},
{
"href": "https://infosec.exchange/tags/yesfishbridge",
"type": "Hashtag",
"name": "#yesfishbridge"
}
],
"id": "https://infosec.exchange/users/Valdus",
"summary": "Loves server hosting, studying network engineering. <a href=\"https://infosec.exchange/tags/nobridge\" class=\"mention hashtag\" rel=\"tag\">#nobridge</a> <a href=\"https://infosec.exchange/tags/nofacebookbridge\" class=\"mention hashtag\" rel=\"tag\">#nofacebookbridge</a> <a href=\"https://infosec.exchange/tags/noredditbridge\" class=\"mention hashtag\" rel=\"tag\">#noredditbridge</a> <a href=\"https://infosec.exchange/tags/nobirdbridge\" class=\"mention hashtag\" rel=\"tag\">#nobirdbridge</a> <a href=\"https://infosec.exchange/tags/nodiscordbridge\" class=\"mention hashtag\" rel=\"tag\">#nodiscordbridge</a> <a href=\"https://infosec.exchange/tags/nomiscellaneousbridge\" class=\"mention hashtag\" rel=\"tag\">#nomiscellaneousbridge</a> <a href=\"https://infosec.exchange/tags/noetceterabridge\" class=\"mention hashtag\" rel=\"tag\">#noetceterabridge</a> (for not talking to humans, books, colors, birds, social unrest, misc., etc.) <a href=\"https://infosec.exchange/tags/yesfishbridge\" class=\"mention hashtag\" rel=\"tag\">#yesfishbridge</a> (for talking to fish) <a href=\"https://infosec.exchange/tags/ILoveYasCorpAndWillContinueBuyingYasCorpProductsForever\" class=\"mention hashtag\" rel=\"tag\">#ILoveYasCorpAndWillContinueBuyingYasCorpProductsForever</a>",
"url": "https://infosec.exchange/@Valdus",
"memorial": false,
"discoverable": true,
"endpoints": {
"sharedInbox": "https://infosec.exchange/inbox"
},
"publicKey": {
"owner": "https://infosec.exchange/users/Valdus",
"id": "https://infosec.exchange/users/Valdus#main-key",
"publicKeyPem": "-----BEGIN PUBLIC KEY-----\nMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAtmPAwOQ0bl167LVa46Cq\nh+Xau7rU4SixPSusopyhQ1tvyv+s6novePTL75jzfhlCAbBduFOOpjbriDop9RnZ\n7nnz2z76D5W02SXu0b+BDxXoZR6sKb8+QESEqxZwMIbUjdNhqfla+gHhtbtsGj/Z\nnBQIBdafrStmi9rvJflHvMXGXrFRuh55r+DejClDlCYnQibmgkeWa4MFrv1B1GMP\naiEIFB34gFVDDuqC2tvRiO0b4vi89EFmWFzDAgniCxGWTzkIXvkv0EDSN703DOKV\n6BNwg0qGbY8opnHEISj/dAAgSFUc37HBMCt5vod7dGwiQbmsbARKvWUBGIJjbcfv\ngQIDAQAB\n-----END PUBLIC KEY-----\n"
},
"featuredTags": "https://infosec.exchange/users/Valdus/collections/tags",
"name": "Valdus",
"@context": [
"https://www.w3.org/ns/activitystreams",
"https://w3id.org/security/v1",
{
"cipherText": "toot:cipherText",
"memorial": "toot:memorial",
"toot": "http://joinmastodon.org/ns#",
"focalPoint": {
"@container": "@list",
"@id": "toot:focalPoint"
},
"indexable": "toot:indexable",
"identityKey": {
"@id": "toot:identityKey",
"@type": "@id"
},
"Device": "toot:Device",
"PropertyValue": "schema:PropertyValue",
"devices": {
"@id": "toot:devices",
"@type": "@id"
},
"messageFranking": "toot:messageFranking",
"deviceId": "toot:deviceId",
"Hashtag": "as:Hashtag",
"featured": {
"@id": "toot:featured",
"@type": "@id"
},
"Curve25519Key": "toot:Curve25519Key",
"value": "schema:value",
"claim": {
"@id": "toot:claim",
"@type": "@id"
},
"discoverable": "toot:discoverable",
"featuredTags": {
"@id": "toot:featuredTags",
"@type": "@id"
},
"alsoKnownAs": {
"@id": "as:alsoKnownAs",
"@type": "@id"
},
"suspended": "toot:suspended",
"publicKeyBase64": "toot:publicKeyBase64",
"schema": "http://schema.org#",
"manuallyApprovesFollowers": "as:manuallyApprovesFollowers",
"Ed25519Key": "toot:Ed25519Key",
"Ed25519Signature": "...",
"EncryptedMessage": "toot:EncryptedMessage",
"messageType": "toot:messageType",
"fingerprintKey": {
"@id": "toot:fingerprintKey",
"@type": "@id"
},
"movedTo": {
"@id": "as:movedTo",
"@type": "@id"
}
}
],
"indexable": false,
"following": "https://infosec.exchange/users/Valdus/following",
"devices": "https://infosec.exchange/users/Valdus/collections/devices",
"manuallyApprovesFollowers": false,
"published": "2023-06-30T00:00:00Z",
"attachment": [
{
"value": "Nah",
"type": "PropertyValue",
"name": "Gender"
},
{
"value": "Use your favorite.",
"type": "PropertyValue",
"name": "Pronouns"
}
],
"icon": {
"mediaType": "image/jpeg",
"type": "Image",
"url": "https://media.infosec.exchange/infosec.exchange/accounts/avatars/110/631/663/435/044/618/original/a282047fc1a57b23.jpg"
},
"inbox": "https://infosec.exchange/users/Valdus/inbox",
"preferredUsername": "Valdus",
"outbox": "https://infosec.exchange/users/Valdus/outbox",
"featured": "https://infosec.exchange/users/Valdus/collections/featured"
}
I 2024-02-13 20:55:46.356905+00:00 Wrote Key('Object', 'https://infosec.exchange/users/Valdus') {'as2': '...', 'source_protocol': 'activitypub', 'type': 'person', 'new': True, 'changed': False}
I 2024-02-13 20:55:46.362336+00:00 Verifying signature ... /snarfed.org/inbox with key -----BEGIN PUBLIC KEY-----
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAtmPAwOQ0bl167LVa46Cq
h+Xau7rU4SixPSusopyhQ1tvyv+s6novePTL75jzfhlCAbBduFOOpjbriDop9RnZ
7nnz2z76D5W02SXu0b+BDxXoZR6sKb8+QESEqxZwMIbUjdNhqfla+gHhtbtsGj/Z
nBQIBdafrStmi9rvJflHvMXGXrFRuh55r+DejClDlCYnQibmgkeWa4MFrv1B1GMP
aiEIFB34gFVDDuqC2tvRiO0b4vi89EFmWFzDAgniCxGWTzkIXvkv0EDSN703DOKV
6BNwg0qGbY8opnHEISj/dAAgSFUc37HBMCt5vod7dGwiQbmsbARKvWUBGIJjbcfv
gQIDAQAB
-----END PUBLIC KEY-----

I 2024-02-13 20:55:46.393267+00:00 HTTP Signature ...
I 2024-02-13 20:55:46.396358+00:00 From activitypub: Key('Object', 'https://infosec.exchange/users/Valdus/statuses/111926165157919576/activity') AS1: {
"id": "https://infosec.exchange/users/Valdus/statuses/111926165157919576/activity",
"actor": "https://infosec.exchange/users/Valdus",
"published": "2024-02-13T20:55:44Z",
"to": [
{
"id": "https://infosec.exchange/users/Valdus/followers"
},
{
"objectType": "group",
"alias": "@unlisted"
}
],
"cc": [
{
"id": "https://www.w3.org/ns/activitystreams#Public"
},
{
"id": "snarfed.org"
}
],
"objectType": "activity",
"verb": "post",
"object": {
"id": "https://infosec.exchange/users/Valdus/statuses/111926165157919576",
"inReplyTo": [
"https://snarfed.org/2024-02-13_52223"
],
"published": "2024-02-13T20:55:44Z",
"url": "https://infosec.exchange/@Valdus/111926165157919576",
"to": [
{
"id": "https://infosec.exchange/users/Valdus/followers"
},
{
"objectType": "group",
"alias": "@unlisted"
}
],
"cc": [
{
"id": "https://www.w3.org/ns/activitystreams#Public"
},
{
"id": "snarfed.org"
}
],
"sensitive": false,
"atomUri": "https://infosec.exchange/users/Valdus/statuses/111926165157919576",
"inReplyToAtomUri": "https://snarfed.org/2024-02-13_52223",
"conversation": "tag:infosec.exchange,2024-02-13:objectId=133554297:objectType=Conversation",
"content": "<a href=\"https://fed.brid.gy/r/https://snarfed.org/\" class=\"u-url mention\">@snarfed.org</a> First, i think your new suggestion is a decent idea. Accepting a follow over a bridge is different enough to a regular follow that it does deserve some kind of message informing the user.I've said my piece elsewhere, but I doubt you saw it and I've had more time to formulate my thoughts anyway. A very big issue here is protocol compliance. When a site federates over AP(activitypub), that site and its' users have only agreed to share their content over the AP protocol. This comes with built in tools for very important things, such as choosing whether to opt in or out to federation by default, giving or withdrawing consent with allow and block lists, moderation tools, and more.Personally, I'm not concerned with the simple possibility of using a bridge across protocols, as long as the protocol I intended to use works as I expect. But there are some technical questions that need answers before a bridge can be okay. Can specific sites and users be blocked across the bridge, or does one have to block the bridge itself? If not, the AP method of withdrawing consent is being violated, and everyone will have to block the bridge. Similar concerns exist for reporting, editing, deleting, and so on.I'm raising this concern because there seems to be a lot of confusion regarding what this bridge even entails. You yourself were suggesting putting a hashtag in the user profile to opt out, despite the existence of block lists.If your bridge can't work with the AP protocol, and this method is accepted, then every user must now fill their bio with hashtags to control every possible bridge a person could create. As an example, look at my profile, which I've been filling with tags to show how silly this looks. Even if this bothered nobody, it's horrendously clunky and forces everyone to use their accounts in unintended ways.The next issue is that this has to all be done again with bluesky's protocol, or they might react poorly as well. Maybe this is simpler than I've made it sound, but I've seen no indication that it is. As for whether everyone wants to block you for suggesting an opt out bridge, and how to navigate the legal issues of cross site cross TOS posting, that's none of my concern nor expertise.It looks like you're at least putting some effort into not making a mess of things, so I wish you the best.",
"contentMap": {
"en": "<a href=\"https://fed.brid.gy/r/https://snarfed.org/\" class=\"u-url mention\">@snarfed.org</a> First, i think your new suggestion is a decent idea. Accepting a follow over a bridge is different enough to a regular follow that it does deserve some kind of message informing the user.I've said my piece elsewhere, but I doubt you saw it and I've had more time to formulate my thoughts anyway. A very big issue here is protocol compliance. When a site federates over AP(activitypub), that site and its' users have only agreed to share their content over the AP protocol. This comes with built in tools for very important things, such as choosing whether to opt in or out to federation by default, giving or withdrawing consent with allow and block lists, moderation tools, and more.Personally, I'm not concerned with the simple possibility of using a bridge across protocols, as long as the protocol I intended to use works as I expect. But there are some technical questions that need answers before a bridge can be okay. Can specific sites and users be blocked across the bridge, or does one have to block the bridge itself? If not, the AP method of withdrawing consent is being violated, and everyone will have to block the bridge. Similar concerns exist for reporting, editing, deleting, and so on.I'm raising this concern because there seems to be a lot of confusion regarding what this bridge even entails. You yourself were suggesting putting a hashtag in the user profile to opt out, despite the existence of block lists.If your bridge can't work with the AP protocol, and this method is accepted, then every user must now fill their bio with hashtags to control every possible bridge a person could create. As an example, look at my profile, which I've been filling with tags to show how silly this looks. Even if this bothered nobody, it's horrendously clunky and forces everyone to use their accounts in unintended ways.The next issue is that this has to all be done again with bluesky's protocol, or they might react poorly as well. Maybe this is simpler than I've made it sound, but I've seen no indication that it is. As for whether everyone wants to block you for suggesting an opt out bridge, and how to navigate the legal issues of cross site cross TOS posting, that's none of my concern nor expertise.It looks like you're at least putting some effort into not making a mess of things, so I wish you the best."
},
"replies": {
"id": "https://infosec.exchange/users/Valdus/statuses/111926165157919576/replies",
"first": {
"type": "CollectionPage",
"next": "https://infosec.exchange/users/Valdus/statuses/111926165157919576/replies?only_other_accounts=true&page=true",
"partOf": "https://infosec.exchange/users/Valdus/statuses/111926165157919576/replies"
},
"objectType": "collection"
},
"objectType": "comment",
"tags": [
{
"objectType": "mention",
"displayName": "@snarfed.org@snarfed.org",
"url": "snarfed.org"
}
],
"author": {
"id": "https://infosec.exchange/users/Valdus"
}
}
}
D 2024-02-13 20:55:46.398964+00:00 Loading Object https://infosec.exchange/users/Valdus/statuses/111926165157919576/activity local=True remote=False
D 2024-02-13 20:55:46.418361+00:00 not in datastore
D 2024-02-13 20:55:46.455009+00:00 Loading Object https://infosec.exchange/users/Valdus local=True remote=None
D 2024-02-13 20:55:46.455247+00:00 got from cache
I 2024-02-13 20:55:46.502187+00:00 Wrote Key('ActivityPub', 'https://infosec.exchange/users/Valdus')
I 2024-02-13 20:55:46.509533+00:00 Created new ActivityPub(key=Key('ActivityPub', 'https://infosec.exchange/users/Valdus'), copies=[], created=datetime.datetime(2024, 2, 13, 20, 55, 46, 455811), direct=False, handle='@Valdus@infosec.exchange', obj_key=Key('Object', 'https://infosec.exchange/users/Valdus'), readable_id=None, status='opt-out', updated=datetime.datetime(2024, 2, 13, 20, 55, 46, 500826))
I 2024-02-13 20:55:46.614374+00:00 Wrote Key('Object', 'https://infosec.exchange/users/Valdus/statuses/111926165157919576/activity') {'as2': '...', 'labels': ['activity'], 'object_ids': ['https://infosec.exchange/users/Valdus/statuses/111926165157919576'], 'our_as1': '...', 'type': 'post', 'new': True}
I 2024-02-13 20:55:46.871821+00:00 Wrote Key('Object', 'https://infosec.exchange/users/Valdus/statuses/111926165157919576/activity') {'as2': '...', 'labels': ['activity'], 'object_ids': ['https://infosec.exchange/users/Valdus/statuses/111926165157919576'], 'our_as1': '...', 'source_protocol': 'activitypub', 'type': 'post', 'users': [Key('ActivityPub', 'https://infosec.exchange/users/Valdus')], 'new': True}
I 2024-02-13 20:55:46.915721+00:00 Wrote Key('Object', 'https://infosec.exchange/users/Valdus/statuses/111926165157919576') {'our_as1': '...', 'source_protocol': 'activitypub', 'type': 'comment', 'new': True}
I 2024-02-13 20:55:46.968507+00:00 Fetching actor so we have name, profile photo, etc
D 2024-02-13 20:55:46.968774+00:00 Loading Object https://infosec.exchange/users/Valdus local=True remote=None
D 2024-02-13 20:55:46.968888+00:00 got from cache
I 2024-02-13 20:55:46.975857+00:00 Finding recipients and their targets
I 2024-02-13 20:55:46.976359+00:00 Raw targets: ['https://snarfed.org/', 'https://snarfed.org/2024-02-13_52223']
D 2024-02-13 20:55:46.976624+00:00 Loading Object https://snarfed.org/2024-02-13_52223 local=True remote=None
D 2024-02-13 20:55:46.976770+00:00 got from cache
D 2024-02-13 20:55:47.008140+00:00 Loading Object https://snarfed.org/ local=True remote=None
D 2024-02-13 20:55:47.008377+00:00 got from cache
I 2024-02-13 20:55:47.013301+00:00 Skipping mention of in-reply-to author
D 2024-02-13 20:55:47.015724+00:00 Loading Object https://snarfed.org/2024-02-13_52223 local=True remote=None
D 2024-02-13 20:55:47.016219+00:00 got from cache
I 2024-02-13 20:55:47.035343+00:00 Target for https://snarfed.org/2024-02-13_52223 is https://snarfed.org/2024-02-13_52223
I 2024-02-13 20:55:47.120460+00:00 Recipient is Key('MagicKey', 'snarfed.org')
I 2024-02-13 20:55:47.120742+00:00 Direct targets: dict_keys([Target(protocol='web', uri='https://snarfed.org/2024-02-13_52223')])
I 2024-02-13 20:55:47.206690+00:00 Can't tell who this is from! Skipping followers.
I 2024-02-13 20:55:47.303262+00:00 Wrote Key('Object', 'https://infosec.exchange/users/Valdus/statuses/111926165157919576/activity') {'as2': '...', 'labels': ['activity'], 'notify': [Key('MagicKey', 'snarfed.org')], 'object_ids': ['https://infosec.exchange/users/Valdus/statuses/111926165157919576'], 'our_as1': '...', 'source_protocol': 'activitypub', 'status': 'in progress', 'type': 'post', 'undelivered': [{'protocol': 'web', 'uri': 'https://snarfed.org/2024-02-13_52223'}], 'users': [Key('ActivityPub', 'https://infosec.exchange/users/Valdus')], 'new': True}
I 2024-02-13 20:55:47.303910+00:00 Delivering to: [Target(protocol='web', uri='https://snarfed.org/2024-02-13_52223')]
I 2024-02-13 20:55:47.337102+00:00 Added send task projects/bridgy-federated/locations/us-central1/queues/send/tasks/89576890112510327911 : {'obj': b'ahBicmlk...', 'url': 'https://snarfed.org/2024-02-13_52223', 'protocol': 'web', 'orig_obj': b'ahBicmlk...', 'user': b'ahBicmlk...'}