1,303 karma · joined May 2, 2015
That is hard to say, if you were to look up my final thread, all my comments were deleted, and you have no way of evaluating if the judgement was fair or not. I held the same position, assuming the moderation team was doing a good job until the hammer hit me.
> Regarding the thread you linked, I'll agree it was the admin's fault for writing the passive-aggressive banner that led to that (well-respected) user leaving.
That is what I am getting at. He has "joked"[0] that the job of moderation is stressful, and it is known that he has other problems[1] that aren't making the job easier for him. I believe that this shapes his moderation style, and not for the better. He errs on the side of over-moderation, which was exactly one of the faults HN hat, that motivated the creation of that site.
[0] https://lobste.rs/s/mox75k/2021_mod_applications#c_ad4hj0 [1] https://lobste.rs/s/ugprwi/what_does_it_take_get_new_tag_acc...
When I was banned, I sent a message to the administrators whether I could get a machine readable file of all my comments. I thought to myself, if I had already spent all that time commenting, I might as well repost them on my own site. But the administrators all refused to even discuss this with me. I sent them SQL queries and everything, but they didn't even regard me worthy of a response. This was very disappointing and unprofessional.
So what I want to say to the sibling comments who are looking for invites, consider it twice. There are annoying people everywhere, and I haven't found a website format that can prevent these from popping up.
Also note that (besides dash), emacs-devel decided against adding any of these packages to the ELPAs. This has made it harder to add a number of packages to NonGNU ELPA, but has been a good excuse to get rid of the dependencies. If anyone is looking for some good Elisp exercise consider sending a patch to replace f/s/... with built-in functionality.
In case dash/f/s/... provide functionality that is not available on older releases of Emacs that one still intends to support, consider using compat (https://elpa.gnu.org/packages/compat.html), a library that I have been developing that attempts to backport recent developments for older releases.
Full independence seems inprobable, or at least I cannot imagine anyone adding support for all the external types: https://orgmode.org/manual/External-Links.html. IMO Org is a markup language imersed into Emacs, and there is nothing wrong with that.
This is the first time I would have heard that point of view, could you elaborate?
Debatable part of hacker culture. I'd say it's more a part of postmodern culture.
My issue is that you can still have a nice readme (often even giving a better, brief overview) by sticking to HTML-free Markdown.
Gitlab seems to be slightly better than Github, by allowing things like badges to be listed outside of the README, in the header of the repository page.
Also it is avalaible on GNU ELPA, so you don't need to configure MELPA before downloading it.
Or to put it this way, if the "woke mob" decided to protest capitalism or even higher/stricter taxes, do you think that anything would change? Probably not, because production for profit it still at the core of every corp while at the same time the woke crowd has a limited understanding of capitalism to begin with (as can be seen by the claims that capitalism is by necessity based on racism). It is the worst of both worlds.
I mixed the two up, will fix.
> and the article wasn't particularly illuminating other than boiling down to "..."
Yeah, I usually don't like writing these kinds of things. When reading about a distribution, especially a new and interesting one, one (or at least I) tend to forget what could go wrong. This text (I intentionally avoid using the word "article") is a reminder to stop, think and consider if one is up for the challenge. As in my case university just started last week, my conclusion was I didn't have the time.
> It's interesting that Guix uses scheme instead of a home-baked configuration language like NixOS.
I consider that to be one of Guix selling points. An established language, with many independent libraries make it a joy to work with (assuming a set up environment). From what I head, that's not really the case with Nix, although I understand the lure of a type system.
I personally use it on my raspberry pi, which operates as my server/home page (http://phi.k.vu/) and it's been fantastic for me. Far lower memory usage and much easier to configure. Xbps is fast and efficient, runit keeps it simple. It's like rediscovering linux or arch all over again, if that analogy means anything to anyone. Really deserves to be better known.
The one thing that keeps me back from using it on my laptop (where I run Debian) is that texlive has to be installed as one whole package, and the incomplete wiki is the other (although arch wiki can cover up quite well for tt's blindspots)
Features
--------
- Log of all commits from HEAD.
- Log and diffstat per commit.
- Show file tree with linkable line numbers.
- Show references: local branches and tags.
- Detect README and LICENSE file from HEAD and link it as a webpage.
- Detect submodules (.gitmodules file) from HEAD and link it as a webpage.
- Atom feed log (atom.xml).
- Make index page for multiple repositories with stagit-index.
- After generating the pages (relatively slow) serving the files is very fast,
simple and requires little resources (because the content is static), only 144 a HTTP file server is required.
- Usable with text-browsers such as dillo, links, lynx and w3m.
Cons
----
- Not suitable for large repositories (2000+ commits), because diffstats are 152 an expensive operation.
- Not suitable for repositories with many branches, a quite linear history is
assumed (from HEAD).
- Relatively slow to run the first time (about 3 seconds for sbase,
1500+ commits), incremental updates are faster.
- Does not support some of the dynamic features cgit has, like:
- snapshot tarballs.
- file tree per commit.
- history log of branches diverged from HEAD.
- stats (git shortlog -s).
this is by design, just use git locally.
>Perhaps the default view should be README and file listing like in GitHub, so it would have been even more obvious.This would actually be pretty easy go do, since one would just have to re-link "index.html" from pointing to "log.html" to "./file/README.html"