Hacker Newsnew | past | comments | ask | show | jobs | submit | meltyness's commentslogin

I would speculate myself instead the more likely thing is related to:

- dns cache configuration

- wlan power saving which is kind of aggressive since Linux has had some power management issues

It's really why I go for a minimal distro, debian with xfce. There's not many components, they're not "tuned", and I can just kinda research any issues myself and find what works. Usually there's some pretty big gaps (missing a whole component, wildly malfunctioning, high resource utilization) and then it's easy to figure out. There's not much code, or really hard scripts to understand. Just maybe enable debug on the service. Learn where the developers put diagnostics (about:support is a godsend). You get to architect your hardware's success and get a rock-solid system. But yeah, if it's weird it might be weird for a while, haha.

For my setup I think the last few lessons were like:

- use gamescope for X11 Wine/Proton (huge.)

- Firefox profile reset to fix hardware decoding (followed some good guides and some bad guides)

- to make changes use the same git tag as your distro so the deps are easily in-reach.

My favorite new discovery for debian in particular is their extensive functional docs. https://www.debian.org/doc/manuals/debian-reference/

absolutely adore this.


Let's see the pool's at $88M with $670 average buy-in, so each of the 132k buyers will owe $15,000-$60,000 of outstanding debt so they can support solvency and to keep airline prices down, and become buyers in the not particularly exciting and highly regulated, volatile capex and opex expensive, fuel consuming and definitely not particularly environmentally friendly, with much larger competitors passenger air transport industry. What an opportunity!


... and room temperature superconductors! If only we could sort out the feasibility, interdependencies, and priorities, but we just don't know, or well, I just don't know haha.


It's interesting on the grounds of aligning incentives.

It's not interesting due to the fact that it suggests humans are still in the loop of some slow-cycle improvements. That'd never get by any board. In fact, selection of model modes implies it's your responsibility, so that meal was scraped into your flowerpot years ago.

I'd say fat chance.



I feel like the READMEs for these 3 large popular packages already illustrate tradeoffs better than hacker news argument


is this token friendly?


... but then why not a model model to perform that outer analysis and overcome the representations shortcomings of an encoder network?


  vocabulary*

  *In the code above, we collect all unique characters across the dataset


You can try and squeeze a free speech absolutism story out of it, but the reality is that this has been a story since Microsoft got into cable news.

At that point it was a game of "I'm not slandering you" to chip away at every other valuation, that could have easily have just been called antitrust because they didn't build it. That was 1996-2005 and went completely unchecked.

This is similar but the stack was even cheaper, and closer to more people's faces.

Even if governments take no recourse, I don't see an issue with government using it's position to put a food pyramid in citizen's faces to say like, "this can be harmful." The church probably would have if this were long ago, except, instead of fire and brimstone, some sort of epic story of social isolation, permanent dissatisfaction, and self-imposed constraints, alien abduction, transformation into a pig by a wizard?

There's probably a lot of visceral fears that would be worthy analogs to the harms of the feed.

I don't think that this narrative has been explored enough, honestly. Corps keep building crap like this, even amazon has (had?) an influencer feed.

People who are in play/leisure should probably practice tolerating more choices than "express mild, momentary dissatisfaction and receive an instantaneous reward"... that's probably not a life everyone should be trained to live


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: