GamingChairModel

"Whistleblows" as if he's some kind of NVIDIA insider.

I know way too many people who only used Twitter for sports. But after /r/nfl and /r/nba and all the sports subreddits blocked Twitter, I think a lot of the organic sports activity will die off.

Loops really isn't ready for primetime. It's too new and unpolished, and will need a bit more time.

I wonder if peertube can scale. YouTube has a whole sophisticated system for ingesting and transcoding videos into dozens of formats, with tradeoffs being made on computational complexity versus file size/bandwidth, which requires some projection on which videos will be downloaded the most times in the future (and by which types of clients, with support for which codecs, etc.). Doing this can require a lot of networking/computing/memory/storage resources, and I wonder if the software can scale.

Networking standards started picking winners during the PC revolution of the 80's and 90's. Ethernet, with the first standards announced in 1983, ended up beating out pretty much other LAN standard at the physical layer (physical plugs, voltages and other ways of indicating signals) and the data link layer (the structure of a MAC address or an Ethernet frame). And this series of standards been improved many times over, with meta standards about how to deal with so many generations of standards through autonegotiation and backwards compatibility.

We generally expect Ethernet to just work, at the highest speeds the hardware is capable of supporting.

The multiple lenses in a traditional professional photograph setup are stacked in front of each other, so they stick out a lot. The multiple cameras on a back of a phone are a workaround for trying to get good image quality and versatile zoom without making the lens stick out too far.

Each physical lens has a single focal length. "Wide" lenses have a wide field of view, and "telephoto" lenses can make very far away things look big in the screen. Have you ever tried to take a photo of the moon with your regular cell phone camera at default zoom? The moon itself is tiny, because the angular diameter of the moon from the surface of the earth is only about half of a degree (out of a 360 degree circle). So you need a very high focal length lens to be able to get the moon to fill up a photograph. Often, in sports, the sidelines have photographers with huge lenses trying to capture intricate detail (beads of sweat, texture of a ball) from 50-100 meters away.

You can stack multiple lenses in front of each other and vary the difference between them to "zoom" to different focal lengths. That versatility is great, and zoom lenses are very common on cameras. But because this feature requires the stacking of multiple lenses, the lens assembly as a whole will end up sticking out pretty far. Bad form factor for a phone.

So cell phones use a bunch of single-lens cameras to make the lens protrude less from the body of the phone, and use software to choose between the cameras: wide, medium, telephoto, or maybe even a super telephoto.

And once they had that in place, there were a few tricks that could be used where the software would evaluate 2 or more cameras simultaneously to try to capture more information with less blur to fill in more image detail than one camera could have, with that sensor hardware. So there are a bunch of computational photography tricks that make cell phone cameras look better with small, limited hardware.

It's still the same issue, RAID or Ceph. If a physical drive can only write 100 MB/s, a 36TB drive will take 360,000 seconds (6000 minutes or 100 hours) to write. During the 100-hour window, you'll be down a drive, and be vulnerable to a second failure. Both RAID and Ceph can be configured for more redundancy at the cost of less storage capacity, but even Ceph fails (down to read only mode, or data loss) if too many physical drives fail.

all the quadratic communication and caching growth it requires.

I have trouble visualizing and understanding how the Internet works at scale, but can generally grasp how page-by-page or resource-by-resource requests work. I struggle to understand how one could efficiently parse the firehose of activity coming from every user on every instance that your own users follow, at least in user-focused services like Mastodon (or Twitter or Bluesky). With Lemmy, there will be many more people following the biggest communities with the most activity, so caching naturally scales. But with Twitter-like follows of individual accounts, there are going to be a lot of accounts on the long tail, with lots of different accounts being followed only by a few people. The most efficient method is to just ignore the small accounts, but obviously that ends up affecting a large number of accounts. But on the other hand, keeping up with the many small accounts will end up occupying all the resources on stuff very few people want to see.

A centralized service has to struggle with this as well, but might have better control over caching and other on-demand retrieval of content in lower demand, without inadvertently DDoSing someone else's server.

The problem is that Canon locks the higher resolution capabilities behind a paywall, and this particular solution is also low resolution. So it's not really a bypass for this, at least not in the current state.

whatsoever she was doing didn't work why they fired her ass.

You're contradicting yourself, because you didn't understand (or didn't read) the article.

Bumble was a platform where only women could message first. It was a leading platform for a while. This CEO changed that to be a more conventional system where men could message first. After that change, the user base dwindled and the stock tanked, as you noted.

In other words, they were much more successful as a woman-message-first platform.

Works for me on Sync.