mark

Renovate is great. Plus there's just something about Github owning dependabot that always bothered me.

The issue with node is the single threading and having to scale with worker threads AFAIK

People always say this but its not technically correct and can be misleading.

Technically, JavaScript runs single threaded but not Node.js itself and certainly not when using it on the backend in something like Express. IO operations and other things tooling libraries do can cause you to run out of a thread pool. But Node.js, when handling requests, gives you much of the benefit of multithreading without having to deal with multithreaded code.

Yeah, JavaScript/TS doesn't get a great rep being used on the backend. But I use it on quite a few of my projects, one of which gets thousands of requests per minute. I was skeptical of whether or not using Node on the backend would hold up, but the performance has been stellar.. pretty surprising, actually.

Inoreader. Syncs across multiple devices too.

This is a duplicate post of https://lemm.ee/post/4849736. Was that intentional?

This was always a no-brainer imo. Love what node has been doing so far 👏

I think you meant to link to https://podcast.asknoahshow.com instead?

We're talking about blocking all content on an instance though--not necessarily a few nasty communities or posts or users. Blocking an instance blocks all content, including non-offensive content that may be posted by legitimate users.

For an admin to block everyone on an instance from all of their users just because of a few bad actors still seems weird to me. It's just gonna lead to every instance blocking each other, which destroys the experience for users and defeats the point of federation.

I like RoR but "Ruby on Rails" and "modern" in the same sentence seems kind of funny.

But then again, "modern" is subjective in itself and most of the websites I see these days (even built and maintained by large companies) seem pretty ancient.

No semantic HTML, still using divs everywhere, no accessibility, all these useless third-party dependencies and lockins vs the new APIs being introduced natively in the browser every day, ajax, jquery instead of using the web platform, hell-- most web developers don't even know what a dialog element is.

I've always felt like the blocking should happen at the user level and muting should be at the instance-level. Feels odd for admins be able to prevent users from seeing content.

Awesome, can't wait to help contribute to the project!

Oh ok seems fine as long as the code continues to merge cleanly with upstream. But once that stops happening, could be hard to continue development without branching off and going our own way.

Will the custom code be open source and made available to us? If so, where would that be?