> Even after a repository has been taken down due to what appears to be a valid claim, we will ensure that repository owners can export their issues and PRs and other repository data that do not contain the alleged circumvention code, where legally possible.

So they have the ability to export issues and PRs already, but it isn't exposed to users?

Exporting your issues and PRs is easy: file a DMCA claim against yourself.

Jokes aside, you might also be able to make a claim under GDPR, as with Spotify.

As a heads-up, the "wannehireme.com/" overlaps your input on Firefox.

thank you, will look into it.

The best description of dates and CSV files I've heard by far. Bravo.

"Csv files are a little bit like like dates: superficially simple, with lots of corner cases. Largely for the same reason: lack of standardization."

I just attempted to run some government data through Python using the csv module. It worked like a charm, until it told me that a field had exceeded the maximum allowable length. A close look showed that a field began but did not end with a quotation mark. Using the csv.QUOTE_NONE flag resolved that, but did not remedy such quirks as short or long records.

CSV files, depending on who generates them, are a bit like dates if the status of a year as leap or not depended on whether the date of Easter were 0 mod 4.

My gripe with the Python csv.reader module is that it has no skip_lines parameter. Ill-formatted lines at the top/bottom of a CSV file are quite common

Hey, this seems really cool! At a glance, they look really well designed. Did you create all of these?

So sorry for the late reply, yes i created all of them. Thanks :)

Here, I found this really useful to understand hashes: https://crackstation.net/hashing-security.htm

I love this. It's ridiculous and interesting and it's the kind of software I love. Good job! I'm a fan.

Thank you, I might quote this at some point :D

:D. Creating quotable content since 2020 ;p

Wow, this is awesome! Great concept and a beautiful result!

I think I know what you mean. I try to wrap at 80 col. and I often need to go back and edit a paragraph, which breaks all my wrapping.

I'll bite: Why?

Rust is designed for a fairly small number of relatively modern systems; there are many close-to-POSIX systems that can’t (and I would guess likely will never) be able to run Rust code in any formal capacity. To the hopeful: even C++ has been unable to win here, despite having many more years of a head start and much more accommodation for stranger platforms. It’s just not going to happen.

Linux on ARM is a very mainstream platform from the perspective I’m looking at this from, I’m afraid. I’m talking about strange Unices running on architectures that GCC may or may not maintain a backend for, or maybe a BusyBox available on some debug interface, maybe a school project to build a simple POSIX-compatible OS or a bootstrap for a platform that had been recently jailbroken. In these cases C is almost always the go-to language and I suspect it will remain so for the foreseeable future as this is precisely the long tail of distributions that standards were intended to provide a base set of tooling for.

Could you give some actual examples? This sounds interesting but I'm not sure I've ever seen something like that in the wild.

This is clearly not one of the examples saagarjha was thinking of, but an actual example where Rust is not an option is the x32 ABI for x86_64 platforms. This ABI works well with GCC, but LLVM suffers from multiple code generation bugs. As Rust is based on LLVM, Rust for the x32 ABI does not work well either. While it's possible to use a mixture of ABIs, so that you have a mostly-x32 system but with some x64 binaries, this requires a multilib setup with multiple copies of system libraries. A pure x32 system cannot currently have Rust utilities.

(I have some patches to improve things but I have not been able to submit them to LLVM yet, and with those patches I did manage to get a working x32 build of rg on my system. I hope to be able to do so in the future.)

Rust supports many platforms but only has "tier 1 support" on a handful of mainstream architectures.

https://doc.rust-lang.org/nightly/rustc/platform-support.htm...

MIPS and SPARC to name a few. Almost all routers are on MIPS and most of them are running some form of Linux or BSD.

AFAIK, rust is still marked as "guaranteed to build" on these platforms, but assume only Linux. BSDs, not so much.

In my experience, most consumer routers are ARM?

Maybe new ones, but there's a ton of MIPS ones too.

You're not likely to even find full-fat grep on such platforms (only busybox)

I don't know what language you're using, but if you want help I'd be happy to do it. I just built an E-commerce site with NodeJS using Stripe as the payment processing (PayPal is next). My contact information should be on my profile.