Reorganizing PSL learning page?

[Ian Williams]

Hello PSL community,

The PSL learning page (https://publicsuffix.org/learn/) lists all known use-cases of the PSL.
Right now, the "Uses" section is laid out a bit like this:

• Known browser use-cases
• Known app-but-not-browser use-cases
• Every library that parses the PSL, across all languages (quite a long list)
• Standards which cite the PSL
• Other (proprietary?) use-cases of the PSL

I'd posit that, for most visitors of the PSL, they're not as-concerned about which libraries you can use to parse the PSL; rather, they're looking at where the PSL is otherwise used.
I agree that developers in the PSL space should know about the libraries that can parse the PSL, but this isn't the majority of end consumers of the PSL.

I think the known use-cases should be organized like this:

• Applications which use the PSL
  • Browsers
  • Non-browser (Proprietary usage could go here, or in another section below)
• Standards which cite the PSL
• Libraries which can parse the PSL
  • (separated by language, ordered alphabetically)

How do other members of the community feel about this?
I'm aware the site is open-source, and am more-than-willing to submit a PR for this.

[Jothan Frakes]

It could use a little organizing, for sure, as it has likely only been updated when there's some kind of a review by someone seeking to take over the project, but the breakdown is typically where folks are not so talkative about their use cases.  This may have changed.

This is something we've tried a few iterations of before when the project was better resourced.  Typically it results in low response due to devs just downloading and using without engaging.

The number of languages that a PSL lib exists for has likely expanded a lot in the last 5-8 years since some of these were updated.  A search of github shows many, but we've typically noticed that there are parties who clone libs so there is some time investment in ensuring you're getting viable candidates and not branches.  It takes time investment to do correctly, and we've directed attention to the most crucial stuff, with ever diminishing volunteer resources, and ever growing z axis of _stuff_ to apply those resources to.

If Amazon has (or you personally have) the cycles to invest, bring it w a PR on for that wiki page, and you're volunteering, let's see what you can come up with.

-J

--
You received this message because you are subscribed to the Google Groups "psl-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to publicsuffix-dis...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/publicsuffix-discuss/7615d851-24d8-4c0b-a023-198d335961d5n%40googlegroups.com.