Are you sure it’s an error and not a “status message” set by the user?
It’s not just you; I see the same message.
For “fun” I’ve set my status to the same message.
2 Thanks
i asked sb about this earlier:
1 Thank
Thanks. I guess it was just coincidental timing, then… an “error” (er, custom status) about bookmarks showed up right after I tried the bookmark feature for the first time, and it was coincidentally attached to exactly the user whose post had been bookmarked.
In other words, I R noob. 
1 Thank
That is just my current status 
Sorry about that.
I got that error after bookmarking a post but also already having it open in another tab and forgetting i bookmarked it, so i tried to bookmark it again. Its a bit of a gag from another forum i visit, setting statuses or signatures from website/forum error messages.
Like error, failed to verify referrer or you can’t upvote the same post twice and so forth 
It appears to be a feature not included, when new posts are posted a thread autoupdates as does the numbers in the top right avatar, but bookmarks do not.
Time for a new status
3 Thanks
Sorry @Hoop for the slow reply. Thanks a lot for the detailed analysis of your findings.
Right. It just doesn’t create multiple line breaks with multiple <Enter> .
Yes, I would agree there’s no point in keeping <p> for manual edits , they were mainly maintained to prevent run-on lines and paragraphs in the un-edited imported posts.
Test preceding text
https://i.imgur.com/cgSU8WC.jpg
Test succeeding text
Test preceding text
https://i.imgur.com/cgSU8WC.jpg
Test succeeding text
Ok it looks like it does add a <br> . Edit: The final published post does not show a vertical space. This is the HTML code that it generates:
<p>Test preceding text
<br>
<a href="https://i.imgur.com/cgSU8WC.jpg" target="_blank" rel="nofollow ugc noopener" class="onebox" tabindex="-1">
<img src="https://i.imgur.com/cgSU8WC.jpg" loading="lazy">
</a>
<br>
Test succeeding text</p>
This is an interesting point.
This might be worth me applying it to the default BLF Theme too and/or somebody submitting an upstream PR.
Yep, this is an important point. In this aspect of editing web content and also text/word processing in general, there has always been a debate between two paradigms: WYSIWYG (“What You See Is What You Get”) and WYSIWYM (“What You See Is What You Mean”). Usually WYSIWYG is more of an ideal, and in practice it’s quite unpredictable and tends to lead to the user micro-formatting elements that will break if any later change is made. In the old forum, the Advanced Post Editor was supposed to be WYSIWYG, but even there the final published post could look significantly different from what the preview showed. So what Discourse uses here is WYSIWYM, because instead of saying “I want this heading to have 18pt bold Verdana font centered” you simply put a # in front of the heading text to say “I mean for this to be a heading”, and then the site defines how headings are supposed to look. I understand that there are strong user preferences for both editor paradigms. But generally WYSIWYM is preferable for composing large amounts of text, because it favors content over presentation and lets the author concentrate more on the actual information instead of tweaking individual aspects of the formatting that will later get out of whack if the document changes.
1 Thank
Yep, the old Drupal forum sometimes did some really weird stuff in its database with the timestamp when posts were edited, which I imagine is what happened to that one. I actually caught the issue at the very last minute before the final migration and tweaked the migration script; otherwise those posts would have been in the wrong order in Discourse.
1 Thank
Ok so it’s in the right place, just the date that is wrong, which is much less problematic, I was sort of confused for a moment there.
Right, the other alternative would have been a lot more confusing. 
It’s not necessarily that the date is wrong, but rather, it’s arguably the wrong date. By that, I mean it’s probably showing the modification time, not the creation time. If someone edited their posts on the old platform, it changed the post date to match the edit date.
So the date is probably correct… it just isn’t the type of date one might expect.
Thanks for the dark theme! I’m using it as my default!
2 Thanks
Yep, TK’s Dark Theme for BLF is awesome!
(I like it even more than her After Dark theme for the old BLF.) 
2 Thanks
Been gone a min… wow things are different.
How long has the site been like this?
1 Thank
Around February 6th, 2023…
EDIT:
Looks like it was February 10th, 2023 for Pacific Standard Time (and EST.)
1 Thank
Hey @Pulsar , great to see you! Please take a look at this information about the new forum and why the change was necessary:
1 Thank
I agree the old forum was way out dated. Just thought I was in the wrong place when it loaded up lol.
I was kind of worried when my password didnt work, but I created a new pass before I saw racoons post and was able to log back in to my original account just fine
2 Thanks
I find the “draft” functionality to be problematic, but I may be using it wrong or missing a step?
When I “create new topic,” then write up the post, then save the draft for later, there is no longer the option of “create new topic,” it only says “open draft.”
As a work around I save my drafts in a .txt file on my computer and abandon the saved draft on BLF in order to be able to create a new thread.
Ideally the site would have two buttons: “create new topic” and “open draft.” Or otherwise, when “save draft for later” is clicked, it should put the draft in the “drafts” area of the user control panel, and with the draft stored over there, it should then allow a new thread to be created…
Also: the site does not seem to allow a proper trailing ellipse at the end of a sentence, which is FOUR periods.... it removes the fourth period.
1 Thank
These days I use Notepad more than I used to about a year ago 
Hi there Hoop, good observation. It looks like it’s working as designed at the moment in Discourse, which only allows for one new topic draft at a time. It’s not ideal, and hopefully Discourse will improve this feature in the future. It does however allow for multiple draft replies in different topics to be saved under /my/activity/drafts .
The current workaround suggestion from the Discourse developers regarding this limitation is to keep a running PM thread with yourself, and then copy/paste from there into a new public topic once it’s ready. The advantage with the PM-to-yourself workaround over Notepad is that it will let you save the draft text on the BLF server and you can access it from any device. You can have one public new topic draft and one draft PM to yourself both being tracked under /my/activity/drafts, and when it’s ready you can turn your PM draft into a public new topic:
If you still need more concurrent new topic drafts then you can hit send on the unfinished PM reply to yourself, and then come back to it and hit the edit button, and once it’s ready you can copy/paste the text into a new topic.
5 Thanks
Nice!
Although I do have a running PM to myself, I rarely use it for this.
I use Notepad++ instead, which is freeware that is much better than Micro$oft’s Notepad that comes with Windows.
EDIT:
I even have the colors set up so that it sort of mimics the Commodore 64, my family’s first computer.
(By the way, this is not super easy, but it is doable.)
