henfredemars

All refers to everything that your instance knows about. Your instance only retrieves data for which users are actually subscribed.

All can be weird on small instances if the user subscriptions don't have a nice distribution.

This is a good point for not choosing too small. I've made a couple of accounts, and it looks like when a servers crosses that 1,000 or 2,000 user mark you start getting much better consistency than the micro instances with only a few hundred users.

I usually find that I have to reload a few times if I'm the first person to try to subscribe to a community. That happens uncomfortably too often if the instance is small. Even then, it can take a days or possibly never to properly federate.

I'm sure these issues will be fixed, but for now, I'd like myself a small instance but not too small so as to avoid issues with consistency.

Only 47%? You'd be a fool to invest.

It's a pretty picture but oh do I hate spider webs.

It's bizarre how despite these recommendations I've had multiple workplaces that change passwords monthly. Add stringent complexity requirements, and you get sticky notes everywhere with full logon details.

A sign in button would be about the same level of security.

I feel like a gigabyte of installation materials is probably a bit more than necessary.

Eczema, where your typical lotion just won't cut it.

Who knew that removing functionality and limiting access to your product was the path to social media success.

I always access from a smaller instance. I didn't even notice I was looking at older content.

I don't think shortage means what they think it means. Just because you can't find people at the price and working conditions you're willing to offer doesn't mean there's a shortage. It might just mean that you're cheap.

I think they require that builds happen on their build servers using public source to make sneaking in something unsavory harder. A maintainer can't just say here ship this binary.

Here you can see that they use an automated build system and a means to track what is getting built.

What is your threat model? I would be more worried about those proprietary firmware blobs that you have to use with your hardware irrespective of what ROM you choose. If you're worried about a maintainer sneaking in a back door, I would think that unlikely because it would leave a paper trail.

I did not read the HN comments about this, but at a glance, the SoC appears to be the RK3568 which is really lame. It comes in the NanoPi, and you're looking at four Cortex-A55, the smallest efficiency core they still use in the last couple year's smartphones. This strikes me as massively underpowered to be called a real "Desktop" experience.

Flagship smartphone from five years ago will run circles around it.