I rolled out an improvement to the site's message processing template. =)
tl;dr:
(1) Based on a user preference, the site can send a message to inform you someone had replied to a comment you had posted. The message *now* contains links that take you directly to the *comment* instead of to the *story*. The message appears at https://soylentnews.org/my/inbox
(2) I made a mistake rolling out the change which will show up as extra text (__seclev__ 500 __version__ $Id$) below the text of the message. That was live for about an hour and is now fixed. I apologize for my error.
(3) Enjoy the added convenience!
[TMB note]:
(4) Also just added &noupdate=1 to the links to your comment and the reply so clicking on one reply won't mark every comment on the story as read anymore.
[/note]
Read on for more details, if you are curious.
Previously, when you got a message that a user had replied to a comment you posted, you'd get links in the message that took you to the *story*. Then, you'd have to scroll down to see the actual comment. *Now*, clicking on either link takes you directly to the *message*, itself. It might help to see an example:
Before:
The Mighty Buzzard has posted a comment, Re:resolution choice, in reply to your comment, resolution choice, attached to Fraunhofer HHI Announces Finalization of H.266/VCC Codec, With Up to 50% Bitrate Reduction vs. H.265.
After:
The Mighty Buzzard has posted a comment, Re:resolution choice, in reply to your comment, resolution choice, attached to Fraunhofer HHI Announces Finalization of H.266/VCC Codec, With Up to 50% Bitrate Reduction vs. H.265.
Though they *appear* the same, as *text*, the *links* under "Re:resolution choice" and "resolution choice" are different.
Unfortunately, I made a mistake in updating the *in-memory* copy of the template (default;comments;reply_msg). I accidentally included text that is needed in the template *file* (/rehash-master/plugins/Messages/templates/reply_msg;comments;default)
The Mighty Buzzard noticed the error and was instrumental in tracking it down. (Thanks Buzz!)
Any messages that were *generated* during this time (today between 1400-1500 UTC give-or-take) will show:
__seclev__ 500 __version__ $Id$
at the bottom of the message text.
Newly *generated* new messages (I.e. after 1500 UTC) should be back to normal; I apologize for any inconvenience my mistake caused.
(That said, I'd prefer you think it was part of my Sooper Sekret plan to get TMB to help test my changes! =)
Related Stories
H.266/VVC Standard Finalized With ~50% Lower Size Compared To H.265
The Versatile Video Coding (VVC) standard is now firmed up as H.266 as the successor to H.265/HEVC.
[...] Fraunhofer won't be releasing H.266 encoding/decoding software until this autumn. It will be interesting to see meanwhile what open-source solutions materialize. Similarly, how H.266 ultimately stacks up against the royalty-free AV1.
Through a reduction of data requirements, H.266/VVC makes video transmission in mobile networks (where data capacity is limited) more efficient. For instance, the previous standard H.265/HEVC requires ca. 10 gigabytes of data to transmit a 90-min UHD video. With this new technology, only 5 gigabytes of data are required to achieve the same quality. Because H.266/VVC was developed with ultra-high-resolution video content in mind, the new standard is particularly beneficial when streaming 4K or 8K videos on a flat screen TV. Furthermore, H.266/VVC is ideal for all types of moving images: from high-resolution 360° video panoramas to screen sharing contents.
Versatile Video Coding (VVC/H.266):
In October 2015, the MPEG and VCEG formed the Joint Video Exploration Team (JVET) to evaluate available compression technologies and study the requirements for a next-generation video compression standard. The new algorithms should have 30-50% better compression rate for the same perceptual quality, with support for lossless and subjectively lossless compression. It should support resolutions from 4K to 16K as well as 360° videos. VVC should support YCbCr 4:4:4, 4:2:2 and 4:2:0 with 10 to 16 bits per component, BT.2100 wide color gamut and high dynamic range (HDR) of more than 16 stops (with peak brightness of 1000, 4000 and 10000 nits), auxiliary channels (for depth, transparency, etc.), variable and fractional frame rates from 0 to 120 Hz, scalable video coding for temporal (frame rate), spatial (resolution), SNR, color gamut and dynamic range differences, stereo/multiview coding, panoramic formats, and still picture coding. Encoding complexity of several times (up to ten times) that of HEVC is expected, depending on the quality of the encoding algorithm (which is outside the scope of the standard). The decoding complexity is expected to be about twice that of HEVC.
See also: MPEG: What Happened?
Sisvel Announces AV1 Patent Pool
(Score: 2) by fyngyrz on Tuesday July 07 2020, @04:15PM (10 children)
BTW, the <strike>strike</strike> regression from a little while back remains broken.
delstill works but it's a half full glass. :)(Score: 2) by The Mighty Buzzard on Tuesday July 07 2020, @04:18PM (2 children)
Was it a regression or did we put it in broken?
My rights don't end where your fear begins.
(Score: 0) by Anonymous Coward on Tuesday July 07 2020, @04:52PM (1 child)
del
deldel perhaps? But it looks ok in preview.(Score: 1, Funny) by Anonymous Coward on Tuesday July 07 2020, @06:14PM
looks ok here.__seclev__ 500 __version__ $Id$
(Score: 2) by The Mighty Buzzard on Tuesday July 07 2020, @04:41PM (5 children)
Wait, nevermind, <strike> is not in the allowed html list, so it shouldn't work.
My rights don't end where your fear begins.
(Score: 2) by fyngyrz on Tuesday July 07 2020, @08:33PM (4 children)
You made <strike>strike</strike> work when I asked you to some time back — then much later, martyb (I think...) disabled it, because it was, according to him, not completely implemented and misbehaving somehow. I never had it misbehave myself, but I don't generally hand-write my HTML, either, I use my macro generator / Soylent-post-prep system, which makes posting a lot easier and less-error prone.
It would be nice to have <strike>strike</strike> work, as it's pretty basic HTML, but again, we have a half-full cup with <del>del</del> so it's just one of those not-quite-right but not critical things about Soylent.
It always seemed to me, at least, that the "right" tag to strike something out was <strike>strike</strike>, as <del>del</del> implies deletion which isn't what happens when you use it.
--
On the Canary Islands, there isn't even one canary.
On the Virgin Islands... still no canaries.
(Score: 2, Interesting) by The Mighty Buzzard on Tuesday July 07 2020, @10:12PM (2 children)
Think it was supposed to be 86'd after someone got butthurt over it not being valid in the HTML5 spec. Really don't remember though.
My rights don't end where your fear begins.
(Score: 3, Informative) by deimtee on Wednesday July 08 2020, @12:07AM
I thought it was something to do with it not closing properly sometimes (nested tags maybe?) and striking the rest of the page.
200 million years is actually quite a long time.
(Score: 3, Informative) by martyb on Wednesday July 08 2020, @12:11AM
Nope. See https://soylentnews.org/meta/comments.pl?noupdate=1&sid=38369&page=1&cid=1017931#commentwrap [soylentnews.org], below, for more details.
Wit is intellect, dancing. I'm too old to act my age. Life is too important to take myself seriously.
(Score: 0) by Anonymous Coward on Tuesday July 07 2020, @11:33PM
Strike is on strike
(Score: 4, Informative) by martyb on Wednesday July 08 2020, @12:06AM
Yes, that's correct. The fix mentioned in this story pertained to a change in another template. Those changes can be made relatively easily.
The situation with STRIKE, as was explained at the time, arose because the perl code had support built in to auto-close dangling DEL tags, but DID NOT automatically close dangling STRIKE tags.
Someone went and wrote a comment that had a <STRIKE> in it, but omitted the </STRIKE> tag. This resulted in every single word following that comment being struck out. I mean in the comment titles, in the text of subsequent comments... everything. The "quick" fix was to edit the comment in the database and close the errant strike tag. But, anybody who saw that manifest (and there were more than a few) could easily repeat the act — I really don't enjoy hand-editing comments in the DB.
I checked the DEL tag and verified that it *did* auto-close dangling (open) DEL tags. I updated a SITE VAR which listed allowed tags and removed STRIKE from the list. It will remain that way until someone can get around to updating the perl code to auto-close STRIKE tags.
In short, the original problem with the STRIKE tag can no longer reoccur (because that tag is no longer allowed) and there is a workaround using the functionally-equivalent DEL tag.
When TMB finishes with his home construction work and has some spare time, then we can start looking at making the deeper (perl) changes.
Thanks for the reminder.
Wit is intellect, dancing. I'm too old to act my age. Life is too important to take myself seriously.
(Score: 5, Insightful) by stretch611 on Tuesday July 07 2020, @06:53PM (2 children)
Damn, how can you let such a grievous error out into production!!! Had I actually been online and looking during that hour it would have forever tainted my experience on this site forever. You should have your pay docked and be fired!!!
Oh, wait... You are a volunteer and do this for free. In that case I guess I should be thanking you.
Well, let me just say Thank you!!!
To all those who work in upkeep of SN, THANK YOU ALL!!!
I am sure that you rarely get the praise that you all deserve.
Now with 5 covid vaccine shots/boosters altering my DNA :P
(Score: 2) by The Mighty Buzzard on Tuesday July 07 2020, @10:17PM
We just gave everyone a five percent raise. Had to. We can't have his monthly checks losing value because of inflation. They're already worth $0, so if they drop any further we'll have to use a signed int instead of an unsigned one.
My rights don't end where your fear begins.
(Score: 2) by martyb on Wednesday July 08 2020, @12:17AM
Wit is intellect, dancing. I'm too old to act my age. Life is too important to take myself seriously.
(Score: 2) by inertnet on Tuesday July 07 2020, @09:20PM (1 child)
Just testing my new sig.
(Score: 2) by inertnet on Tuesday July 07 2020, @09:22PM
Thank you very much for all the work people.
I'll remove the sig after this...