- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Mar 22 2022
Mar 14 2022
Feb 27 2022
Feb 23 2022
Feb 10 2022
Thanks! LGTM :-)
Jan 31 2022
Jan 17 2022
Jan 3 2022
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.
Dec 8 2021
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
Dec 7 2021
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?
Dec 6 2021
Dec 2 2021
+1, and ok to put the Events entry in the News menu
Nov 29 2021
Nov 28 2021
Nov 26 2021
Nov 25 2021
Nov 19 2021
Nov 16 2021
Nov 13 2021
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
Nov 2 2021
Oct 24 2021
Oct 22 2021
Thank you, tried again, and now it works! :-)
Oct 21 2021
Oct 17 2021
Oct 6 2021
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/ )
Oct 5 2021
Sep 21 2021
Sep 20 2021
Sep 19 2021
The agreement has been signed, so we can move forward and publish the blog post.
Sep 14 2021
Sep 5 2021
Aug 31 2021
Cool! LGTM
Aug 30 2021
In the future we will also need to answer a more complex use-case where the iframe resembles more as an embedded copy of the archive.
Do you have an example of a complex usecase to get a better idea of your needs ?
Aug 28 2021
Thanks for all this great work...
A few questions/remarks:
- where is the Permalinks tab? I do not see it in the images
- for the url, what about "/embed/" instead of "/iframe/"? "embed" seems to be the canonical term used to designate this kind of things (see YouTube, etc.)
- instead of "go to the archive", why not "View in the Software Heritage Archive"?
- it's great that the iframe can use the width and height attibutes! How do you plan to handle strange values (e.g.: width=10px height=200%)?
Aug 23 2021
Jul 26 2021
Thanks for looking into this.
What about sending logs to a separate dedicated logging machine instead of storing them locally?
Jul 22 2021
In T3127#67581, @anlambert wrote:I am a bit puzzled by the numbers shown: eeally we have only 200k origins for GitLab.com.?
Indeed there is something weird here as we have more than one million gitlab.com origins in database.
softwareheritage=> select count(*) from origin where url like 'https://gitlab.com/%'; count --------- 1023499 (1 row)Looks like something was missed when computing lister metrics from scheduler database, this needs further investigations.
Jul 21 2021
I am a bit puzzled by the numbers shown: eeally we have only 200k origins for GitLab.com.?
And we know we had some 1.5m origins for Google code, why only 700k shown here?
Jul 20 2021
Jun 26 2021
Jun 22 2021
Nice to see this moving forward!