tv binge, the oa, no significant spoilers Show more

@vector Yeah, my personal preference is as close to 100% as can be achieved with the time allowed. It does look like the rare test module is located in the same places as the heaviest code modules.

Anyway, thanks for the pointers, I think I have enough foothold now to know what to research first.

@vector There's a test dir with a mocha settings file, some fixtures and some utils. The actual test coverage appears to be... not great. I'll need to have a closer look with a coverage measuring tool. Perhaps 'istanbul'?

@vector (That is, I grok promises just enough to dislike them; async/await seems like a sorta okay replacement for the boilerplate, even if they do appear to be way overused...)

@vector It looks like async/await is used fairly consistently, but now that I read up on what it does (essentially replacing promises, which I grok just enough to dislike) it worries me that there's no error handling code.

@ben I agree in principle, but I need to distinguish between bad things the last developer did from bad things everybody who writes node does, since the latter will likely match whatever tutorials / blog posts I end up consulting.

only partially joking Show more

Some brief digging suggests it is using something called Nxus, which appears to be a web application framework, because the world needs more JS frameworks.

So all of the controllers are subclasses of nxus-core or nxus-admin controllers. I guess the project implementation doesn't look utterly terrible, but Nxus is about 2.5 years old which doesn't fill me with confidence.


I'm maybe inheriting a project, as a part-time paying gig. I don't do node. I do the minimum amount of client-side JS to make something work.

If the project is sane, I'm confident I could skill up on-the-fly. If the project is terrible, I'd be in over my head. I don't have the expertise to judge, though.

If it was Python / Django, I'd be able to tell what I was in for in ten minutes.

Where do I look in a node project? What are best practices? What warning signs do I look for?

@DJWalnut Huh. This reminds me of some of the weirder cutups / mashups that Negativland did. Only goofier.


Me: This joke format bugs me. Nobody said nothing? Isn't this a double negative? Did it start in a language where that construction is normal?

Ah, yes, the Internet Of Owership's directory.

Powered by Google's Firebase.


@ceejbot This is an excellent talk. You laid out the corrupting influence of VC in FOSS really well.

I'm super excited for entropic and hope it succeeds beyond all hope and dreams. And without that success being a catastrophe.

Start a blog and write your first article, get $20. Write another 3 articles within six months and get another $20. Sweet! I'll be happy to help test for you.

I'm also just particularly familiar with the API because I re-implemented it in Python for . So I know what it is theoretically capable of, even if it is sometimes a bit weird about how it does things, like the difference between since_id and min_id, because both are poorly named.

Or, (and relevant to @binder) a command-line client that looks like Dave's Own Citadel.

Really, I should just build a bridge between Mastodon and my RSS reader, and use that to read my timeline. At least then I know I won't miss anything, everything can be sorted how I want, and unread/read status will be explicit rather than inferred. It may also help to know that my internet access is not fast. Doing any extra work to get to the toot I want to read is likely to take 10X more time than somebody on a decent broadband connection. I don't actually care much about the display order, I care about not spending the first half of my short reading sessions loading toots I'm not going to read yet.

The long-press option is news to me; I just tried it and it works for relatively short gaps, but I worry that trying to use it to load three days of toots at a time might either take several minutes anyway or get me rate limited. Loading the oldest 40 toots in a gap rather than the newest would have neither problem.

Finally got around to creating the issue for a giant annoyance that eats up over half my daily fediverse reading time:

I continue to be amazed at how many people assume 'reversed chronological' is the best sorting method for social media. I get wanting to know what's going on right now, but I want to read my timeline like a webcomic, not a firehose I dip into randomly without context. Firehoses are for twitter.

Show more is a cooperatively-run corner of the Fediverse. The instance is democratically governed by its members, who generally share an interest in the co-op model, but topics of discussion range widely.

If you are interested in joining our community, please review our Bylaws and Code of Conduct. If you agree with them, you may apply for membership on our instance via this link

Our instance is supported by sliding scale contributions of $1-10/mo made via Open Collective. You must have an active Open Collective account to apply for membership; you may set one up here