Did you see the instructions on running a HN clone at the bottom of https://github.com/arclanguage/anarki/blob/master/README.mar...? Basically you add a username you want to designate as the admin, then you use HN as that user. Let me know if you have more questions.
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.
Thanks again.
Guy
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.
Ah, I just remembered seeing various special pages just for admins in news.arc. For example /badsites seems to show sites that have been nuked in the past.
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 updated my script to auto-upgrade Anarki tests[1], and things look pretty good. Just a couple of minor comments:
a) I see a message about redefining assert. Perhaps we should change the name in Anarki or unit-test.arc?
b) The new version complains about duplicate nested suite names inside a test suite. That seems like a reasonable idea, and I just want to confirm that it's intended.
c) If you have a duplicate test name in a suite the error is confusing. Here's the example I ran into from Anarki:
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."
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).
"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.
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).
Looks like Scala has some experimental macro feature: http://docs.scala-lang.org/overviews/macros/overview.html. I imagine people will be about as likely to use it as they've been to use previous non-lisp macros (i.e. not very likely).
OP isn't about macros because the output of the function isn't automatically evaluated. It's a step in the direction of allowing any programmer to perform compiler transformations and optimizations on his/her own code. I'm very interested in that area.
If you've seen something like the Rust Handbook, that would be one end-goal of documentation I would want to implement. For most other programming languages, there's a multitude of resources available for people to study and learn with. Arc just has a couple of web pages focused towards it, to be honest. We have the tutorial and the various documentation on the different functions of the Arc language.So, I DID spot a couple of web pages, but I'm not so sure if they'll be helpful for new programmers to the language.
I was wondering which pages you're aware of, since that will help put your statements in context. Can you share a few links?
I no longer do much programming in Arc. I mostly just hang out here to talk about interesting programming language ideas, and to answer any questions from newcomers. It's unclear how much benefit there is in polishing a language nobody uses. But if you choose to create new docs I'd love to help proof-read them. Who knows, maybe I'll even be inspired to contribute.
