Hey there @Henk4U2 , really appreciate you making an effort to stay with us!
Good lord, never use an operating system that’s not receiving security updates anymore on the InterNet. Your machine probably was infected by … everything. 
2 Thanks
No. Not ever. I think the reason I never had trouble with malware is that malware also evolves, and my old laptop stopped coping with new HTML and scripts a long time ago. Maybe computers are like people. If you skip your health checks long enough, bad boys gradually lose all interest (just kidding).
I also never used a virus scanner on this one. Why? They took so much resources regular programs just stopped working. But I ran CCleaner at the end of every working day. To get rid of electronic lint.
Thanks SB, really appreciate it. I plan & hope to become more active again, with new flashlight & lantern projects. 
2 Thanks
Nice!!! Thanks a lot for saying so. We’re happy to have you here.
1 Thank
I think I found a bug. I haven’t been able to reproduce the bug though; it only happened once, and now it seems … stuck.
I bookmarked a PM from Bort, to remind me to respond. Then I responded, and deleted the bookmark. A day or two later, I noticed a weird icon by Bort’s name in comments, but I assumed he just added a unicode symbol or something. Didn’t really pay it much attention, and I don’t know when it started.
Now that I’m looking at it more closely though, it’s not part of his name… it’s a server error. It shows me this if I hover over the icon:
I’ve bookmarked (and unbookmarked) PMs and posts from other people, and didn’t run into any issues. I also tried bookmarking multiple posts in a single thread, both public and private, and didn’t get any errors. I even tried re-bookmarking the original post, and then deleting that bookmark again, but it didn’t seem to affect the sticky error.
The error is visible regardless of which client I connect from, so I think it’s a server-side issue.
So, not sure how it happened. Maybe I made (or deleted) the bookmark on an old browser tab with an outdated version of the client javascript, and now I can’t reproduce the issue because I only have current versions. Maybe it’s something else. Not sure. Regardless, I guess something weird got into the database, and Bort now has a speech bubble following him around.
Or maybe it’s not related to me at all. I still see the error when I’m logged out.
Edit: Not an error, I’m just a Discourse noob. The error was inside me all along. 
2 Thanks
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