In the old forum my bookmark to the forum pointed to “My posts” (ego_search) which showed the topics where I participated, with newest first. So I could quickly see if there was any followup in those.
What is the new way to do that? I do not want to “pin” those topics, I only want to have a query to show them but still have the flexibility to go to the full view (ignoring this selection) after I have read those topics and want to check if there is more.
It seems that the migration process has pinned a number of topics for me, but unclear what was the criterium.
First read my long posts in WinBox 4 topic regarding ~30 interface issues and ~10 scaling issues, where every issue was described and argumented. Then talk about bullshit.
My bad. Yes. I can see the same issue when switching to compact. Will check if we can fix it in theme.
thx
… I didn’t fight my way through from top to bottom here ![]()
Also, please be aware that because all edit histories, even for deleted posts, are visible to all, we should always make sure to not include sensitive information in the configuration exports that we post on the forum. Here is an example:
If you look at the edit history of the OP, you’ll see that our moderator @holvoetn has made an edit to censor the serial number of OP’s router. But it’s futile because the serial number is still there in the edit log.
Same for post that have been deleted, such as this one above Migration process from our old phpBB instance to Discourse is now done - #229 by rekeds
As some other have already mentioned here. Discourse does show sticky topics there till they are marked as read or unmarked with that icon on left near title.
We will check/rethink on how we could manage announcement articles in future to maybe avoid sticking our announcement articles there. But for that we’ll need to wait for @normis return. As mentioned he usually makes decisions on these kind of changes in our community sites.
Just disabled public history for posts. Now those are visible only to MT staff users.
Only for the record. and I am not particularly whining, I now have to use another computer to access the forum (because Discourse is stupidly non-compatible with my - admittedly old - browser on my “normal” PC) and the standard view is unbearable on the LCD of the laptop I am now using (too d@mn white/bright), so I had to go on the dark side
and use the dark theme (which is something I normally hate) to make it usable, but all this is not “news” on every board I have been there have been (sometimes dramatic) changes of software/looks/colours, I remember a phbb update on a board that came out like an LCARS screen (please read as unreadable for human eyes before the 22nd century) and I had to start the light blue ribbon campaign for freedom of skin:
http://jaclaz.altervista.org/Projects/freedom_of_skin.htm
(and yes, it is http:, you may well be subject to MITM attacks, don’t click on it if you believe that only https: is safe)
at that time it worked out nicely and we managed to have back a readable theme, let’s see if we can do something on Discourse too.
Are you serious? People should keep up with latest updates for critical software, this is especially true for a browser. So you do not care that yours is stuffed with a wide range of security vulnerabilities?
As of now I have only 1 complaint remaining - please find a better default theme for dark mode - neutral tones would definitely be more preferable than this dark blue/purple awfulness. It almost looks like current dark theme was choosen by colour-blind person…
Yes, I am serious, you are very nice to care about my security, but I am fine, thanks.
Agreed. All that blue is bad for OLED screens too.
Using old browser which probably translates to outdated browser? Tbh it is maybe more secure to run ROS 3.x somewhere inside your network than surfing the internet with an outdated browser. ![]()
This shade of blue is actually unpleasant for eyes even on light theme. More subtle choice would be nice.
When his browser is that old that it is incompatible with this forum, it likely also does not yet have all those security vulnerabilities ![]()
People often forget that when they update all the time to get fixes for the vulnerabilities, they also are downloading the new vulnerabilities that will be fixed in a later upcoming release.
It was already suggested, but again: please make a normal timestamp for posts instead of these stupid ‘5m’, ‘2h’, etc. And its format should be adjustable somewhere in forum preferences, NOT taken from browser, OS, etc.
I find it much more convenient and immediate to understand this way instead of the normal timestamp.
It is not possible to accommodate everyone, we have different preferences.
Just wonder, how would you understand, if a post was made 1 day ago in the morning or in the evening?
Then make it switchable. As I said, some setting in the forum preferences.
I am familiar with these relative timestamps in GitLab. It is annoying to look through old issues and Gitlab prints “2 years ago” and in fact it is 2y and 11 months old - quite 3 years already.
Imho it makes sense for everything < 24h. But for longer periods it gets very inaccurate.
There might be one more issue with timestamps - at least what comes to view when not logged in. That probably depends on whether visitor timezone can be detected or not. I read some other forums where timezone is way off when I am not logged in and therefore timestamps are quite useless…