Is this fixed now, or is the issue still open?

In T3230#83166, @VickyMerzOwn wrote:

Hey, I would like to work on this issue.

Sometimes these variants site side by side with the plain text ones

I didn't understand what site here means.

Thanks! LGTM :-)

Dec 31st is now past, so I asked Marla to remove the "until Dec 31st" from the image,
and we can leave the banner up for a month more.

In T3134#75077, @anlambert wrote:

SWHID v2 should also prevent the hash collision issues we are currently facing (some related to the SHAttered attack on SHA1), see T3775 and SWH-LOADER-GIT-JT.

Updated task name and description to reflect the findings from @anlambert

Thanks a lot @anlambert for looking into this.
It is possible that more key cryptographic software will include these files.
We need a strategy to handle this situation, may you add this example to the SWHID v2 task?

+1, and ok to put the Events entry in the News menu

A task to add to this hackaton:

• add to https://github.com/citation-file-format/ruby-cff/tree/main/test/files/formatted a few examples of Bib(La)TeX entries for software and their corresponding .cff
  • this will ensure that the cff-latex exporter produces proper biblatex-software entries, and uses all the available fields in biblatex-software
  • since .cff is not able to handle BibTeX's crossref fields, use the expanded entries attached to this task

Thank you, tried again, and now it works! :-)

Yes, we must filter this stuff out (we discussed this issue with @zack some time ago, and you may see Torvalds' opinion too https://www.zdnet.com/article/linux-boosts-microsoft-ntfs-support-as-linus-torvalds-complains-about-github-merges/ )