chirospasm

[email protected] may be a community to look into, OP. While audio focused, you might be able to shake out some general entertainment hardware conversation, as well!

Top comment, should be pinned. We need a gaggle of these. A gagglebyte.

“We did the back-of-napkin math on what ramping up this experiment to the entire brain would cost, and the scale is impossibly large — 1.6 zettabytes of storage costing $50 billion and spanning 140 acres, making it the largest data center on the planet.”

Look at what they need to mimic just a fraction of our power.

+1 for Netdata

Maybe against the grain, here, with all the comments saying No, but: If you were interested in trying something out, I would give Hypatia a go. It’s a FOSS-based app, available on F-droid. It’s basically a ClamAV front-end. Pulls from their signature lists for Android, alongside other more general AV signature lists. Just an option.

Soulseek introduced me to so much new music! It was also the first software I had encountered that would randomize its port on connect – or at least let you customize it – to avoid firewalls.

Even though there’s a small monthly cost, the results have been consistent for Kagi. But consistency meets only half of my needs for search: I also want to make decisions quickly from what I find within the contents. If I were to to go to a link, wait for it to load, scroll the content, etc. – does that listed forum post have the answer I am looking for? Does this news article cover the nuances I have been tracking and would like to read more of? Kagi offers an AI-based summarize feature that helps. And that’s been meeting the other half of my needs, as well.

EDIT, an opinion: Search services may well be eventually replaced by small, niche LLMs trained to perform summerization tasks, such as Consensus, which I have used for work research, and Perplexity.ai. The AI summarize feature of Kagi is why I see the service as more useful than straight indexes, even when self-hosted. Kagi is a stepping stone toward this for me, and why I recommend it.

Duskers looks fantastic. Thanks for sharing the link!

Good bot.

I suspect it may be a bit more along how you’re describing here – we expect some user experience patterns to already be in place, if not considered, like not being able to select inappropriate handles. Former Twitter folks should know ‘better.’ From the outside looking in, it tracks.

I wonder if the Bluesky team, right now at least, is more engineer / dev heavy, and they have not brought on UX folks to help drive a product design that considers patterns we’d be used to experiencing. They may be operating pretty lean.

An idea, at least.