One way I use skills, which I don’t see mentioned very often, is as “shortcuts”. Imagine some frequently issued prompt like “fetch origin and rebase this branch onto origin/master and resolve conflicts”. I make that into a little skills file called “rebase” with a one sentence description, and next time just type something like “/reb-tab-enter”.
Ah yes, something like prefix tree would work well storing reverse domain names like com.abc.www (although this is such a well known thing I feel like I must be missing things).
Definitely. Even a custom compression/encoding that knows to treat the different fields differently -- just a 4-byte binary IP address for A records, normal LZ-based text compression of the domain name (perhaps using a custom starting dictionary and/or Huffman table), etc.
This doesn’t seem to mention that having AI aggressively optimize software will result in code that is too clever / complex to be maintained by the original human author. For something with a very stable API and can be tested to death like a regex engine it’s likely
workable. Other things, not so much. We have enough trouble maintaining AI generated code _without_ aggressive optimizations as is!
The software detects when an identical URL is submitted and will mark it as a duplicate (with certain conditions like how recently it was last submitted and whether it had any front page time and discussion).
When similar URLs or different versions of the same story are submitted and get votes/comments, we have to use discretion to work out which URL is best, who submitted first, which discussion is most active/healthy, and we'll try to consolidate the discussion into one thread with the most informative/canonical URL as the main link.
