Two Kinds of Updates
I have begun a new topic category for Cluster, as things really seem to be taking off.
Eric’s automobile-related weekend tragedies are discussed allegorically in this new update. An interesting read, for sure.
I have updated the Cluster code to allow for line breaking within the input. Input validation has also been made more robust with regard to line breaking and (theoretical, likely intentional) attempts to break the flat file format.
It seems like people have been expecting to have line breaking capability, so I did my best to put them in by hand where it looked like they were filtered out. If there is an issue with my judgment calls, drop me a comment.
Beyond simply cleaning up the code and doing the little Ball API idea, there have been suggestions to fork and broaden the functionality of the program a bit. I am not sure as to whether flat text file data sources would be suitable for such an expansion, which would probably include user ratings of articles (of some consequence to the system) and a system of endorsed user malfeasance.
I think I could still make flat files work. What I envision are a set of rules (I keep thinking of the special cards in Uno) that allow for certain trickery. I see two main actions:
- a “timebomb card,” which you are allowed to play on the current ball-holder. If the user fails to update within the timespan of the timebomb, he “drops the ball.” The first person to the site has the ability to pick it up.
- a “reverse” card, which changes the ball progression from, metaphorically, clockwise to counterclockwise.
I have to go prep for a presentation, but I’ll keep this going when I get done.