Subtle changes, bugs and feedback

Why has the forum got this confused with me?

https://www.lfgss.com/comments/17524266/

It's in my 'following' feed and I got email notification.

My guess, the author originally had your name in there by mistake, then they edited their post

Sounds plausible enough that I feel daft for not realising, thanks.

was trying to access lfgss from LNER train wifi earlier & was fully locked out by CloudFlare (no captcha, just "you're barred mate") - not a massive deal, but ray id was 8c92a8038cd69568 in case you're interested

I'm not getting images loading on chrome (mobile) as attachments. Tried again in incognito mode, same result.

1 Attachment

Hilariously I can't even view my own screenshot in the previous post lol

1 Attachment

FWIW they are coming through fine for me

yeah no clue what's going on here. Nothing viewable for me on chrome desktop either. vov

Now they're back. Bizarre.

Andyp appearing on Today as a new user despite joining in 2007. This a bug?

1 Attachment

If you edit your bio you appear as a new user

1 Attachment

There seems to be an issue with rendering formatting in a "details" html tag, which I use to hide spoilers.

If you look at post https://www.lfgss.com/comments/17563617/, it renders nicely in the preview pane, with line spacing and italics, but then looks horrible in the actual post.

I wonder if this is a feature to prevent some form of code injection attack? But it kinda sucks.

For reference the source of that post is :

<details>
<summary>Click for detailed spoiler explanation:</summary>
The answer is *ammo*.

The definition is *bullet*.

This is arrived at by:

Taking a (compass) point, in this case "*e*" (for East), out of the word *memo*, giving "*mmo*".

This is then put after the third letter of *draft*, which is an "*a*", to give the answer of "*ammo*". 


</details>

EDIT - looks like the spoiler thing ruins the formatting. It looks fine in the preview pane. I will raise a bug.

Are we not previewing youtube links any more?

https://www.lfgss.com/comments/17609515/

The parser seems to object to the "si=" argument

It's based on regular expressions:

match: ^(?:https?:|)(?:\/\/)(?:https?://www.|)(?:­youtu\.be\/|youtube\.com(?:\/embed\/|\/v­\/|\/watch\?v=|\/ytscreeningroom\?v=|\/f­eeds\/api\/videos\/|\/user\S*[^\w\-\s]))­([\w\-]{11})(?:\W.*)?$

replace: <iframe width="560" height="315" src="https://www.youtube-nocookie.com/embed/$1" frameborder="0" allowfullscreen></iframe>

And that does match: https://www.debuggex.com/r/vrwGLfnHAkpxyime

Which would yield https://www.youtube-nocookie.com/embed/KKdfiQLkG9Y

I'll make a test in Go after my next meeting.

Test case shows it should work: https://go.dev/play/p/pzaySgaeEDM

Actual test on the code in question shows it does not work: https://go.dev/play/p/e7yEWJ8a_EU

The query string has become sorted...

This test shows that query.Encode() https://go.dev/play/p/eiU5CbfpMof sorts the query string, which results in it not matching the regexp.

A week and a bit ago I upgraded the Go programming language version, which also updated the dependency libraries, and means that this is new behaviour that came in via that.

I will update my regular expression to match the querystring no matter where it appears.

This appears to fix it: https://go.dev/play/p/QeaawZ-9Kjh

Yup... it fixes it.

Confirmed that Go team changed the behaviour in May, but I hadn't updated the language in half a year so I'd only just pulled that change in.

All understood and resolved... change in core language library behaviour broke my regexp which was written with the assumption that the order of query strings would not change. I see the Go team had the epiphany that ordering query strings increases cache hit ratios.... good epiphany, but it broke my assumption :)

All that said... si is a tracking parameter to show up who shared a video and which page it was shared on.

Fuck that shit... am going to strip the si variable from URLs.

Also done.

am going to strip the si variable from URLs.

I do that with youtube and IG links manually on our chats. No one else does it for me :(