This is a proposal for an entirely free and open source rant like site/app.

devrant today has a couple of problems that I hate:
* Posts in the wrong categories (usually by new users)
* Low effort posts in the "recent" feed
* Good posts in the "algo" feed that are too old
* Longtime bugs
* No official code format in comments, ffs.
* Unimplemented features (like inability to search posts in android, or inability to mute posts in web desktop)
* Lack of admin involvement with the community

but it also has some aspects that I like a lot:
* Admins aren't trigger happy to suspend/ban you
* The avatars are awesome and help to associate users to faces
* The ++ system is good enough
* The community isn't too big so you know pretty much everyone
* There's a lot of variety in the roles and techonologies used by users
* Experienced ranters are usually smart
* Super simple UI
* The comments have only one level (as opposed to reddit comment trees)

This project should try to reimplement the good things while fixing the bad things.

I wrote two posts about a possible manifesto, and an implementation proposal and plan.
https://rantcourse.ddns.net/t/...
https://rantcourse.ddns.net/t/...

I think the ideas outlined there are very aligned to concerns of privacy and freedom users here vouch for.

This project is not meant to **purposefully** replace/kill/make users abandon devrant. People can continue using devrant as much as they want.

I'm hosting a discourse site on a 5$ linode machine to discuss these things. I don't know if it's better than just github.

If you feel that you would like to just use github issues, let me know. I'll create a github org tomorrow, and probably setup gitter for more dynamic discussion.

It powers nodejs.org. It has 7.8k stars on Github.
It was installed 5x as much on NPM in the last 4 months as it was in the previous 5 years. https://metalsmith.io

I've been doing a lot of outreach to individual users, websites, and related Github projects, yet community involvement is hard to get by. If you value copy-left or free open-source software and are interested in bloat-free nodejs static site generation or build pipelines, please reach out.

I have a full-time job and am thankful for any help, be it feedback on the Gitter chat: https://gitter.im/metalsmith/... maintaining one of the 15+ core plugins, creating starters or writing blog posts.

Metalsmith is an older but still awesome NodeJS static site generator. Due to metalsmith's original founding company not having done a complete open-source ownership transfer however, active development has stalled for years.

I am super-happy to have been accepted as a member of the Github metalsmith org today in the role of maintainer. Hope I can help bring it back on track. If you're curious please npm i metalsmith and head over to the newly created Gitter chat to share your input: https://gitter.im/metalsmith/... !

I am doing some vue tutorial, then I came across this: https://github.com/vuejs-templates/...

One comment says:

This issue is closed, and ideally, issues are not for support questions, but only for bugs and feature discussions.

Please ask your question on the forum , Stack Overflow or on gitter and are happy to help you out there.

It gets down-votes.

The following comment:
........
........
Lastly, I really appreciate the Elixir community's philosophy that poor documentation and unintuitive error messages are considered bugs.

#Suphle Rant 7: transphporm failure

In this issue, I'll be sharing observations about 3 topics.

First and most significant is that the brilliant SSR templating library I've eyed for so many years, even integrated as Suphle's presentation layer adapter, is virtually not functional. It only works for the trivial use case of outputting the value of a property in the dataset. For instance, when validation fails, preventing execution from reaching the controller, parsing fails without signifying what ordinance was being violated. I trim the stylesheet and it only works when outputting one of the values added by the validation handler. Meaning the missing keys it can't find from controller result is the culprit.

Even when I trimmed everything else for it to pass, the closing `</li>` tag seems to have been abducted.

I mail project owner explaining what I need his library for, no response. Chat one of the maintainers on Twitter, nothing. Since they have no forum, I find their Gitter chatroom, tag them and post my questions. Nothing. The only semblance of a documentation they have is the Github wiki. So, support is practically dead. Project last commit: 2020. It's disappointing that this is how my journey with them ends. There isn't even an alternative that shares the same philosophy. It's so sad to see how everybody is comfortable with PHP templating syntax and back end logic entagled within their markup.

Among all other templating libraries, Blade (which influenced my strong distaste for interspersing markup and PHP), seems to be the most popular. First admission: We're headed back to the Blade trenches, sadly.

2nd Topic: While writing tests yesterday, I had this weird feeling about something being off. I guess that's what code smell is. I was uncomfortable with the excessive amount of mocking wrappers I had to layer upon SUT before I can observe whether the HTML adapter receives expected markup file, when I can simply put a `var_dump` there. There's a black-box test for verifying the output but since the Transphporm headaches were causing it to fail, I tried going white-box. The mocking fixture was such a monstrosity, I imagined Sebastian Bergmann's ghost looking down in abhorrence over how much this Degenerate is perverting and butchering his creation.

I ultimately deleted the test travesty but it gave rise to the question of how properly designed system really is. Or, are certain things beyond testing white box? Are there still gaps in the testing knowledge of a supposed testing connoisseur? 2nd admission.

Lastly, randomly wanted to tweet an idea at Tomas Votruba. Visited his profile, only to see this https://twitter.com/PovilasKorop/.... Apparently, Laravel have implemented yet another feature previously only existing in Suphle (or at the libraries Arkitekt and Deptrac). I laughed mirthlessly as I watch them gain feature-parity under my nose, when Suphle is yet to be launched. I refuse to believe they're actually stalking Suphle