|
What email reader are you using?
"Time flies like an arrow. Fruit flies like a banana."
|
|
|
|
|
Your not going to like my answer. But it is Eudora 7.1.0.9, with the update from the Hermes group who recently produced a way to put in TLS1.2 compliance, and proper handling of certificates. There are many possible candidates for a replacement email client, but I haven't found one yet that I'm willing to try, and I have 20 years worth of email in over 400 email folders within Eudora that I preserve. The junk and spam I delete, but I have my own reasons for saving things that way.
The Hermes Group was established to take on the job of updating Eudora with the Computer History Museum's release of the Eudora source code to the public. Right away a difficulty arose in that the source required some 3rd party libraries that are neither free, nor open source, and not particularly available any longer. That seems to have caused a huge slowdown in the project of producing a new replacement. I've read that they have a version that compiles, but is unstable. Before they got started on actual work, I was one person they contacted to work on the new project. I declined as I had just started a new, large project and didn't consider myself 'available'. I still have a time constraint, and am not yet available. And my work flow at present time is not very efficient.
Please forgive the boldface, but it is easier on my eyes.
Regards,
Steve Tabler
|
|
|
|
|
So sounds like an email client problem and not an email problem.
Myself I use a small email service which is browser based. So with years of Firefox (10 at least) and maybe a couple with Chrome I have not had a problem like you describe.
I doubt they want to attempt to support every email client themselves. And especially not variations like you mentioned. But there might be something in the page which you might find which they can easily restrict, if you identify it for them.
|
|
|
|
|
another example of an existing bug that has been reported a few times already. this time in the Lounge.
This happens when a parent thread is reported and removed through reporting but child threads/replies still remain.
Edit: and then when a user adds a new post, it become the parent thread to the orphaned child threads.
Edit 2: Griff has advised that it appears to be the new parent thread but it really is not.
modified 31-Jan-23 15:10pm.
|
|
|
|
|
It doesn't become the parent, it just looks that way. If you hover the mouse, the "parent line" that appears points above the visual parent.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I assume you haven't had time to think of one, so how about one of these?
Favourite TV SciFi series? : Expanse, Star Trek Picard, Babylon 5, ... loads of 'em
Favourite / current phone?
Favourite PC game? GTA V, Witcher, Doom, Solitaire, Fortnite, ...
Indentation style (always good for an argument) ... 
Worst computer language?
Worst computer company?
Worst computer software?
Car type: Petrol, Diesel, Electric, Hydrogen? Current and next, perhaps?
Most hated website characteristic? GDPR permissions every damn time, italics, comic sans, colour choice, paywall, slow loading, popups, too many ads, ...
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Great suggestions. I'll queue these up
cheers
Chris Maunder
|
|
|
|
|
I tried to import my github repo and noticed several errors with processing.
inferjs[^]
Images are not processed correctly and missing. Logo is missing. Header icon images missing except for the last one. Not sure what that is about.
JS pre code including
<span class="pl-k"></\span> around my js multiline comment lines.
.'\ /`.
.'.-.`-'.-.`.
..._: .-. .-. :_...
.' '-.(o ) (o ).-' `.
: _ _ _`~(_)~`_ _ _ :
: /: ' .-=_ _=-. ` ;\ :
: :|-.._ ' ` _..-|: :
: `:| |`:-:-.-:-:'| |:' :
`. `.| | | | | | |.' .'
`. `-:_| | |_:-' .'
`-._ ```` _.-'
``-------'</p
|
|
|
|
|
Looks like this has been resolved.
cheers
Chris Maunder
|
|
|
|
|
Still showing
<span class="pl-k"></span> in code blocks wrapped around code.
.'\ /`.
.'.-.`-'.-.`.
..._: .-. .-. :_...
.' '-.(o ) (o ).-' `.
: _ _ _`~(_)~`_ _ _ :
: /: ' .-=_ _=-. ` ;\ :
: :|-.._ ' ` _..-|: :
: `:| |`:-:-.-:-:'| |:' :
`. `.| | | | | | |.' .'
`. `-:_| | |_:-' .'
`-._ ```` _.-'
``-------'</p
|
|
|
|
|
Hey Chris, Did you fix the automated process yet? I updated a lot of code with my article today and the
<spans> around the comments are back.
I expect that you don't want to update the article and remove these everytime i post an update 
Thanks
.'\ /`.
.'.-.`-'.-.`.
..._: .-. .-. :_...
.' '-.(o ) (o ).-' `.
: _ _ _`~(_)~`_ _ _ :
: /: ' .-=_ _=-. ` ;\ :
: :|-.._ ' ` _..-|: :
: `:| |`:-:-.-:-:'| |:' :
`. `.| | | | | | |.' .'
`. `-:_| | |_:-' .'
`-._ ```` _.-'
``-------'</p
|
|
|
|
|
As the subject states, I would like to suggest a separate area for Wordles and, possibly, puzzles in general. What do y'all think?
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
Good point - better to have it separate than in Discussions.
|
|
|
|
|
Yeah, its getting crazy in the Lounge now with all the bloody wordle crap and CCCs. agreed.
then again, a Lounge anywhere in the world is where retired and bored people go to drink cheap booze, play puzzles, and think about days of old.
I highly doubt Chris will move on this.
|
|
|
|
|
but, take out the wordle's and CCC's, and Oi's, and detailed technical daily blogs ... what is left ?  
«The mind is not a vessel to be filled but a fire to be kindled» Plutarch
|
|
|
|
|
Message Removed
-- modified 25-Jan-23 15:38pm.
|
|
|
|
|
I think this item on page 3 may be incorrect:
|
|
|
|
|
I wish that all web developers - including CP developers - would try out all their web pages, including all dialog/popup boxes, with the zoom function (typically operated by ctrl-scrollwheel), from minimum to maximum, in relevant browsers!
I discovered more or less accidentally that the ragged layout of the author column in the forums could be straightened by zooming in a little! Zooming in will increase the author column width - but note that the entries making the ragged left are not the longest ones. There is lot of white space between the author and the date with both short and long names, but apparently there is some connection to the width of the date text. When you zoom out, and raggedness sets in, there is no further zooming of the character size; it remains unchanged to the minimum zoom level.
This is in Firefox. So I tried Edge. Here, the columns are straight all through the zoom range, and zooming out reduces character size to far below readable. If I zoom out to see all 50 entries in one screenful, it is still readable. With Firefox, there is no way (that I have discovered) to see all 50 entries in one go.
Then I tried going the other way, zooming in. As expected (based on experience from other web pages), menu lines and similar lists are terribly messed up. With Edge, the menu changes with zoom level - 'Home' disappears, 'Quick Answers' turn into 'Q&A' (which is a reasonable abbreviation), 'Discussions' change to 'Forums', 'Features' change to 'Stuff'(!), 'Community' to 'Lounge', 'Help' to '?'. Maybe these are all attempts to abbreviate texts, but some of them are outright misleading (e.g. 'Stuff', and 'Lounge' is one of several entries in the 'Community' menu).
With Edge, there are few if any cases of different fields being put on top of each other when zooming in. In the forum lists of posts, Edge will put the author on a line below the subject, which is a good solution. Generally speaking, zooming in with Edge is reasonably good.
When playing around with the zoom in FF, once it locked up - not completely; I could zoom from 250-300% to 500%, but not further back to get an overview of the page. A reload page fixed it; I don't know
Firefox is a a completely different story. It won't change the menu entries, but places items on top of each other, such as '15,553597 members' at the top of the top banner, which is not zoomed. The left side menu overlaps the list of posts, and the subject column is reduced to with of a single word, maybe two words - while the author column fills half the window width!
If you search for a selection of messages and zoom in close, in Edge the right hand column is dropped, and the window is given a horizontal scroll bar, at least from 250% and upwards. This is reasonable behavior. In FF, the left hand menu is chopped off (not overlying the hit list in this window!) so you can't see what the filters are, and there is no horizontal scroll bar. The right hand column is not dropped.
In this hit list, if you zoom the other way, all the way out, text lines are laid on top of each other, as if the characters were reduced in size - but they are not.
All taken together: Zooming in Edge is 'reasonable'. In Firefox, it is a mess. And I prefer Firefox.
A fair share of regular posters have quite a few years of professional experience. Or stated in a different way: A fair share of them may today, or within a few years, have a real need for a well functioning zoom.
|
|
|
|
|
That ragged alignment has been fixed but... the fix is in a branch of the code that has a full port to Bootstrap, along with a complete rewrite of the forum UI. It's a big, big change internally and it's been sitting there while a million other things get in the way. It's probably too big a change a this point, so what I will probably end up doing is back-porting the changes to the current codebase and, once and for all, fix that thing that's been annoying the daylights out of me.
FWIW I do test in multiple browsers and on multiple operating systems (Try Safari sometime - that'll truly make you tear out your hair). And then mobile. And tablets. And older browsers, because not all browsers were auto-updating (looking at you IE). It goes on and on and on and it has to work on every single one. And this is why I started the move to bootstrap: a solid framework that's well tested beats a homegrown solution that's grown through 20 years of browser evolution. The tradeoff is, however, size, as well as chasing the frameworks as they change. A huge part of the stall in dev was that while I was working on the port, Bootstrap moved from v4 to v5, which was a huge, huge breaking change. I'm pretty sure it'll happen again.
Once browsers started moving to WebKit I really thought this intensely painful time of browser incompatibility, but then Google very quickly forked to Blink, FireFox continues to use Gecko, Safari uses Chrome but has different default settings, and on it goes still.
It's the thing about standards: there are so many to choose from.
cheers
Chris Maunder
|
|
|
|
|
Chris Maunder wrote: It's the thing about standards: there are so many to choose from.
Sorry... I had to: xkcd: Standards[^]
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Would it be a good idea to order the articles awaiting moderation by age, so the oldest one is top of the list?
Today, we had one new member post some 60-odd spam articles, and because we only get 15 at a time in the queue it wasn't until they had all been vote closed (or deleted - I dumped loads of 'em once the member was kicked) that the article that had been sitting there unmoderated for 11 hours could be seen.
Surely, we should be moderating older material first?
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Would it be better if new members were prevented from posting articles until they had earned some minimum number of votes?
|
|
|
|
|
That seems a bit of a "sledgehammer approach" - it seems politer just to moderate older articles first as they have been waiting longest anyway.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Maybe, but it would prevent situations like the one we saw this morning.
|
|
|
|
|
Perhaps they should be restricted so they can't post a second article until their first one has been approved? Or at least have a sensible limit on the number of unapproved articles they can have in the queue at one time.
One for @chris-maunder to consider at least.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
