There isn't much by way of admin tools. Basically what the admin can do is block content in various ways: http://i.imgur.com/bmQXByS.png. Beyond that you're expected to rely on the Arc commandline, or to manipulate the files created under anarki/www/news.
Thanks for your reply akkartik.
Yes..I did see what you referred to....
I have created an account using the user name I entered while setting up the software. Opening my admin user account is not the problem.
The question I have is where is the admin panel...or how do I administer admin controls?
For instance, while being logged in as admin how do I delete a comment? Or a thread? Look at a list of users, etc?
One more thing now that I have have your attention, if I may.
Do you know of any instructions on how to put anarki HN on my server so anyone can access it? I want to put a forum online for all to use.
Yes, it's a desired feature that a suite can't contain two things with the same name -- either suites, tests, or one suite and one test. This is because I want names to be unique. Saying (test cut.finds-element-in-suite) shuld run only one test.
What you ran into is actually a bug I fixed at a meetup on Tuesday. The current error message is:
Error: "In suite cut, there are two things named finds-element-in-string."
I just want to point out a conversation I had with fauria on GitHub, in case others here have ideas. Currently the HN code doesn't support keeping the HN data (.../anarki/www) on a separate partition from the code (.../anarki) as Docker would like to do to maintain stateless containers. This is because any file creation which performs a create-then-rename first creates the temporary file in .../anarki/tmp. Renames then fail if .../anarki/www is in a different volume.
Heh, no worries. It's taken me, oh, 202 days to update the dang library (I feel like my macro skills have something to be desired, or it would be easier). So no worries about taking four to see this. I was planning on pinging you in a few days if you hadn't seen this.
A coordinated launch would be cool. I'm pretty much ready here; the readme is updated (although it does not explicitly have a version number, which I should add).
But before we get into that, would you mind playing with it a little bit to see if there's anything broken or not working? Thanks.
I've reread the article and You are right, the author's intention seems to be getting rid of unnecessary constructs. I guess then that I'm looking for something that Arc is not (powerful abstractions included in the language from the get-go).
I don't think there is any one particular feature that is groundbreaking in Arc, although as a whole, Arc does have some interesting qualities. For example, code in Arc is much more succinct than code in other languages. When designing Arc, Graham would write a piece of code. He would then look at that piece of code and figure out what features would allow him to make that piece of code shorter. From there, he would implement that feature and rewrite the code. Due to this process, Arc has a large number of very simple utilities (e.g. check). With all of these utilities, code in Arc is much more concise than the equivalent code in other languages.
"Hundred Year Language" is a bit of misnomer. Graham's original essay is a thought experiment on what the language we will be using in a hundred years will look like. Graham believed it would be useful to try and implement the language we will be using in a hundred years and in doing so, came up with Arc.
Others may disagree here, but I don't think Arc was really intended to contain new concepts. The phrasing of "Hundred Year Language" was I think a nod to timelessness rather than novelty. It was an attempt to take questionable novelties out of Lisp (like hygienic macros) and to clean up ill-thought-out interfaces (the keyword choices you alluded to).