Symfony Profiler

{
    "@context": [
        "https:\/\/join-lemmy.org\/context.json",
        "https:\/\/www.w3.org\/ns\/activitystreams"
    ],
    "actor": "https:\/\/lemmy.world\/c\/asklemmy",
    "to": [
        "https:\/\/www.w3.org\/ns\/activitystreams#Public"
    ],
    "object": {
        "id": "https:\/\/midwest.social\/activities\/create\/5f9a10ce-be2f-43f2-8046-3a0f1f98d5c6",
        "actor": "https:\/\/midwest.social\/u\/sxan",
        "@context": [
            "https:\/\/join-lemmy.org\/context.json",
            "https:\/\/www.w3.org\/ns\/activitystreams"
        ],
        "to": [
            "https:\/\/www.w3.org\/ns\/activitystreams#Public"
        ],
        "object": {
            "type": "Page",
            "id": "https:\/\/midwest.social\/post\/26343846",
            "attributedTo": "https:\/\/midwest.social\/u\/sxan",
            "to": [
                "https:\/\/lemmy.world\/c\/asklemmy",
                "https:\/\/www.w3.org\/ns\/activitystreams#Public"
            ],
            "name": "Invisibly locked posts?",
            "cc": [],
            "content": "<p>Several times now, I\u2019ve tried to reply to a comment \u2013 usually, I\u2019m doing this on a mobile app \u2013 and when I hit \u201cpost\u201d I get an error. Then, when I refresh, I get a \u201cpost not found\u201d error. Until now, I just move on, because, it\u2019s only Lemmy.<\/p>\n<p>But this morning, I got the same error, and in frustration I opened the post in Firefox, and went to reply to the comment, and in the web page all of the post editing stuff was disabled. I mean, I could click \u201cReply\u201d and open the reply widget, but the text editor area and all of the buttons are disabled.  The post in question is <a href=\"https:\/\/midwest.social\/post\/26284842\" rel=\"nofollow\">this one<\/a>.<\/p>\n<p>Before, I speculated that the mobile app would only load so many posts back in time, and maybe they were aging out or something. Or, perhaps, some were removed by mods or the author. Although irritating, I didn\u2019t much care.<\/p>\n<p>This, though, is weird, and I wonder how many of the posts I\u2019ve had this issue with is because of it. It\u2019s as if the post is locked, except that there\u2019s no indication I can find that it\u2019s locked. On the web site, it at least prevents you from trying to reply \u2013 on Voyager, it\u2019ll merrily let you spend ten minutes composing a reply only to fail to submit, but that\u2019s just a Voyager bug. However, the fact that the post is for all intents and purposes locked, but the official Lemmy UI provides no indication of this \u2026 is this also a bug?<\/p>\n<p>And is is \u201clocked\u201d, or is this some behavior relating to cross-site blocking, where blaha.zone won\u2019t let midwest.social users post, and the server knows it and so prevents the user from <em>trying<\/em> to post? Or is it because I\u2019ve blocked the poster, and Lemmy will show me, but won\u2019t let me comment on, posts by blocked users? Or is this some weird situation where the poster deleted the post but it\u2019s still showing up?<\/p>\n<p>In any case, this feels like a bug. The site should clearly indicate that posts are locked, or blocked, or whatever the reason commenting is disabled. The web interface clearly knows that the post is un-comment-able; it should show this, and preferably, display why.<\/p>\n<p>Or, am I missing something obvious?<\/p>\n",
            "mediaType": "text\/html",
            "source": {
                "content": "Several times now, I've tried to reply to a comment -- usually, I'm doing this on a mobile app -- and when I hit \"post\" I get an error. Then, when I refresh, I get a \"post not found\" error. Until now, I just move on, because, it's only Lemmy.\n\nBut this morning, I got the same error, and in frustration I opened the post in Firefox, and went to reply to the comment, and in the web page all of the post editing stuff was disabled. I mean, I could click \"Reply\" and open the reply widget, but the text editor area and all of the buttons are disabled.  The post in question is [this one](https:\/\/midwest.social\/post\/26284842).\n\nBefore, I speculated that the mobile app would only load so many posts back in time, and maybe they were aging out or something. Or, perhaps, some were removed by mods or the author. Although irritating, I didn't much care. \n\nThis, though, is weird, and I wonder how many of the posts I've had this issue with is because of it. It's as if the post is locked, except that there's no indication I can find that it's locked. On the web site, it at least prevents you from trying to reply -- on Voyager, it'll merrily let you spend ten minutes composing a reply only to fail to submit, but that's just a Voyager bug. However, the fact that the post is for all intents and purposes locked, but the official Lemmy UI provides no indication of this ... is this also a bug?\n\nAnd is is \"locked\", or is this some behavior relating to cross-site blocking, where blaha.zone won't let midwest.social users post, and the server knows it and so prevents the user from _trying_ to post? Or is it because I've blocked the poster, and Lemmy will show me, but won't let me comment on, posts by blocked users? Or is this some weird situation where the poster deleted the post but it's still showing up?\n\nIn any case, this feels like a bug. The site should clearly indicate that posts are locked, or blocked, or whatever the reason commenting is disabled. The web interface clearly knows that the post is un-comment-able; it should show this, and preferably, display why.\n\nOr, am I missing something obvious?",
                "mediaType": "text\/markdown"
            },
            "attachment": [],
            "sensitive": false,
            "published": "2025-04-16T12:37:49.309311Z",
            "audience": "https:\/\/lemmy.world\/c\/asklemmy",
            "tag": [
                {
                    "href": "https:\/\/midwest.social\/post\/26343846",
                    "name": "#asklemmy",
                    "type": "Hashtag"
                }
            ]
        },
        "cc": [
            "https:\/\/lemmy.world\/c\/asklemmy"
        ],
        "type": "Create",
        "audience": "https:\/\/lemmy.world\/c\/asklemmy"
    },
    "cc": [
        "https:\/\/lemmy.world\/c\/asklemmy\/followers"
    ],
    "type": "Announce",
    "id": "https:\/\/lemmy.world\/activities\/announce\/create\/12ab8271-add2-4841-a816-7e72ca9ec2df"
}

{"@context":["https://join-lemmy.org/context.json","https://www.w3.org/ns/activitystreams"],"actor":"https://lemmy.world/c/asklemmy","to":["https://www.w3.org/ns/activitystreams#Public"],"object":{"id":"https://midwest.social/activities/create/5f9a10ce-be2f-43f2-8046-3a0f1f98d5c6","actor":"https://midwest.social/u/sxan","@context":["https://join-lemmy.org/context.json","https://www.w3.org/ns/activitystreams"],"to":["https://www.w3.org/ns/activitystreams#Public"],"object":{"type":"Page","id":"https://midwest.social/post/26343846","attributedTo":"https://midwest.social/u/sxan","to":["https://lemmy.world/c/asklemmy","https://www.w3.org/ns/activitystreams#Public"],"name":"Invisibly locked posts?","cc":[],"content":"<p>Several times now, I’ve tried to reply to a comment – usually, I’m doing this on a mobile app – and when I hit “post” I get an error. Then, when I refresh, I get a “post not found” error. Until now, I just move on, because, it’s only Lemmy.</p>\n<p>But this morning, I got the same error, and in frustration I opened the post in Firefox, and went to reply to the comment, and in the web page all of the post editing stuff was disabled. I mean, I could click “Reply” and open the reply widget, but the text editor area and all of the buttons are disabled.  The post in question is <a href=\"https://midwest.social/post/26284842\" rel=\"nofollow\">this one</a>.</p>\n<p>Before, I speculated that the mobile app would only load so many posts back in time, and maybe they were aging out or something. Or, perhaps, some were removed by mods or the author. Although irritating, I didn’t much care.</p>\n<p>This, though, is weird, and I wonder how many of the posts I’ve had this issue with is because of it. It’s as if the post is locked, except that there’s no indication I can find that it’s locked. On the web site, it at least prevents you from trying to reply – on Voyager, it’ll merrily let you spend ten minutes composing a reply only to fail to submit, but that’s just a Voyager bug. However, the fact that the post is for all intents and purposes locked, but the official Lemmy UI provides no indication of this … is this also a bug?</p>\n<p>And is is “locked”, or is this some behavior relating to cross-site blocking, where blaha.zone won’t let midwest.social users post, and the server knows it and so prevents the user from <em>trying</em> to post? Or is it because I’ve blocked the poster, and Lemmy will show me, but won’t let me comment on, posts by blocked users? Or is this some weird situation where the poster deleted the post but it’s still showing up?</p>\n<p>In any case, this feels like a bug. The site should clearly indicate that posts are locked, or blocked, or whatever the reason commenting is disabled. The web interface clearly knows that the post is un-comment-able; it should show this, and preferably, display why.</p>\n<p>Or, am I missing something obvious?</p>\n","mediaType":"text/html","source":{"content":"Several times now, I've tried to reply to a comment -- usually, I'm doing this on a mobile app -- and when I hit \"post\" I get an error. Then, when I refresh, I get a \"post not found\" error. Until now, I just move on, because, it's only Lemmy.\n\nBut this morning, I got the same error, and in frustration I opened the post in Firefox, and went to reply to the comment, and in the web page all of the post editing stuff was disabled. I mean, I could click \"Reply\" and open the reply widget, but the text editor area and all of the buttons are disabled.  The post in question is [this one](https://midwest.social/post/26284842).\n\nBefore, I speculated that the mobile app would only load so many posts back in time, and maybe they were aging out or something. Or, perhaps, some were removed by mods or the author. Although irritating, I didn't much care. \n\nThis, though, is weird, and I wonder how many of the posts I've had this issue with is because of it. It's as if the post is locked, except that there's no indication I can find that it's locked. On the web site, it at least prevents you from trying to reply -- on Voyager, it'll merrily let you spend ten minutes composing a reply only to fail to submit, but that's just a Voyager bug. However, the fact that the post is for all intents and purposes locked, but the official Lemmy UI provides no indication of this ... is this also a bug?\n\nAnd is is \"locked\", or is this some behavior relating to cross-site blocking, where blaha.zone won't let midwest.social users post, and the server knows it and so prevents the user from _trying_ to post? Or is it because I've blocked the poster, and Lemmy will show me, but won't let me comment on, posts by blocked users? Or is this some weird situation where the poster deleted the post but it's still showing up?\n\nIn any case, this feels like a bug. The site should clearly indicate that posts are locked, or blocked, or whatever the reason commenting is disabled. The web interface clearly knows that the post is un-comment-able; it should show this, and preferably, display why.\n\nOr, am I missing something obvious?","mediaType":"text/markdown"},"attachment":[],"sensitive":false,"published":"2025-04-16T12:37:49.309311Z","audience":"https://lemmy.world/c/asklemmy","tag":[{"href":"https://midwest.social/post/26343846","name":"#asklemmy","type":"Hashtag"}]},"cc":["https://lemmy.world/c/asklemmy"],"type":"Create","audience":"https://lemmy.world/c/asklemmy"},"cc":["https://lemmy.world/c/asklemmy/followers"],"type":"Announce","id":"https://lemmy.world/activities/announce/create/12ab8271-add2-4841-a816-7e72ca9ec2df"}