chaosharmonic

Is there a reason such a thing couldn't present a bunch of neutral options, but with affiliate links that provide revenue back to Mozilla?

(I mean, that could still steer it toward places that have affiliate programs, but if you're running a local AI tool to help you search for these things that seems like something you should reasonably be able to toggle on and off/configure in a system prompt/something.)

> RISC is China/Eastern

RISC-V was developed at UC Berkeley. It's roughly as Western as West realistically gets, short of being made in Hawaii.

> That's a geopolitical question

Sure, but that's not actually about where RISC-V is from. It's that it's a purposely open platform -- so much so that its governing body literally moved to Switzerland.

The reason it's a geopolitical question is more to do with what we did to their supply chains with sanctions on companies like Huawei and ZTE, and what COVID did to everyone's supply chains independently of that. Both of those things made it really evident that some domestic supply chains are critical. (On both sides -- see: the CHIPS Act)

Where RISC-V comes back in is that open source doesn't really have a functioning concept of export restrictions. Which makes it an attractive contingency plan to develop further in the event of sanctions happening again, since these measures can and have extended to chip licenses.

(Edit: I'm not saying any of this is mutually exclusive with valid concerns about Huawei, raised by various other sources. I'm less familiar with ZTE's history, but my point in either case is more of a practical one.)

I mean.

There was that time Zuck made a bad bet on VR and then the entire dept working on it got slashed...

> I don't think you need to "justify layoffs". If a company feels an employee is not being productive, they should be allowed to let them go.

Layoffs, by definition, aren't about individual employees.

Tech side project: crawlers that doomscroll job boards for me, and a Tinder clone that swipes through them. I recently broke out the actual automation logic into something more recyclable for scaling out to new targets (and broke out the HTML parsing for possible use outside my browser automation flow). Still figuring out how I want to handle datasources as both an API and a plugin architecture, but the goal is to eventually be able to configure searches through the API, to manually trigger and/or setup scheduled runs.

github: [username]/escape-rope, /escape-rope-ui | UI demo: escape-rope.bhmt.dev

Personal side project: extensive cleanup of my family's place. I'm just now approaching a decent first pass at the outside, and have to tear apart a basement next. It's taken most of this year. It's not the specific reason I've farmed collecting search results off to a bot

For-fun thing: CTF puzzles. I'm not very good at them, but they're useful for other things. I fell down the scraping rabbit hole this way, and I'm currently using a series of them to finally get some exposure to Python. I also have a writeup half-written about this exact process

It's doing even more work when you're aware that, at one point, the NLRB had banned non-disparagement clauses in severances and employment agreements outright, stating that even offering these terms amounted to coercive behavior that prevented people from discussing their working conditions. [1]

[1] https://www.reuters.com/legal/us-labor-board-limits-gag-clau...

This disaster is why I've built a whole side project automating the act of doomscrolling through job boards, so I can focus on actually talking to people when I find something that does interest me. (And can track the results in one place without repeatedly running into duplicates.)

> But is a 30-year-old who moves back in with their parents "homeless"?

Depends -- how safe is their parents' home?

That answer can vary, for a lot of reasons.

The (smaller) laptop mainboards, on the other hand...

As a Deno user, this news also makes me see more value in JSR. (Relative to npm's ownership, that is.)

Right, but in the same vein, the British crown has a documented history of applying that label to dissidents. It was part of why were revolted in the first place.

Our definition for what constitutes treason is purposely narrow specifically due to the abuse potential.

Lots of things are anti-American behavior.

Most of those things aren't joining up with a foreign adversary with whom we're officially at war.

Even things that are treasonous in a colloquial sense are still pretty narrow, and tend to refer to other specific forms of betraying your country, that just happen to be other crimes -- like espionage, or insurrection.

Can confirm, I myself was a one person support desk (for a restaurant chain) and just never officially had a title. The internal moniker of "the IT guru" was fine for an email signature, but certainly not for a resume. (I've since made other retroactive edits to that, both for something more sensible and to better represent years of scope creep.)

Bit of both. It stores available jobs via JSON upload, but also lets you log interviews and track their overall lifecycles.

This demo is just the UI and isn't thorough about API mocking (and the interview forms have a couple snags I need to work through still so I've left it out of the test data), but the full application also includes crawler flows for collecting results.

> Since the license ban the use and installation in EU, I would ask: It is possible to formulate a license that claims: "The restriction A is motivated to protect our ass but we will not directly or indirectly enforce it against you"?, Such kind of phrasing in the license could be categorized or called "isolating clause" but I don't know if judges could consider it a circumvention of the law.

Maybe not the exact thing you're talking about, but that description reminds me of the Alliance for Open Media -- their codec licenses are royalty-free, but the same terms revoke your usage rights if you sue anyone for the use of these formats.

I don't disagree with this either -- it's very clearly just a free market working both ways.

It also immediately reminds me of the no-call agreements companies had with each other last decade 10 or 15yrs ago.

I don't at all disagree with you, but at the kind of money you'd be making at an org like OAI, it's easy to envision there being a ceiling, past which the additional financial compensation doesn't necessarily matter that much.

The problem with the argument is that most places saying this are paying more like a sub-basement, not that there can't genuinely be more important things.

That said, Sam Altman is also a guy who stuck nondisparagement terms into their equity agreement... and in that same vein, framing poaching as "someone has broken into our home" reads like cult language.

I actually just shared a Show HN post about mine before finding this...

I recently shipped a first-draft UI demo that you can play around with for my self-hosted jobs tracker:

https://escape-rope.bhmt.dev

> I don't know of a single person who has switched to a smaller phone after having a bigger one

Consider how small the overlap is between devices in a product lineup in the first place and an audience that can buy them -- whether that's through carrier availability to put them on plans if in the US, or the resources to spend on them up-front.

That trend also is based on touch as the primary method of interaction -- but given the tethered AR devices we're starting to see trickle out, and Android's desktop mode finally hitting prime time, that assumption might not hold long-term. I'm not saying this will be the timeline we live on, but considering some of the experiments with dedicated, external devices for powering them, it's not hard to envision the pendulum swinging back toward smaller phones that focus more on things like the compute and sensors and less around a screen you look at all day.

Think of the (modern) Moto Razr. You could, hypothetically, have a compute device that more so resembles the folded-down version of this -- aimed more toward external displays, and less toward being regularly looked at.

> Sony tried to compete with the bet camera, best DAC and I don't think those phones sold.

They were also priced like it -- and worse, many of them weren't available through US carriers, which is prohibitive to a market that often won't spend Kaz Hirai money all at once on a phone.

You're otherwise restating my point, though. Many of the niche hardware features don't have to be built into the device if you just offer more baseline extensibility.

My hotter take is that this is the same problem as IR blasters, and relative to the old normal -- when device makers like LG were specifically advertising how awesome their built-in DAC was -- this whole thing could be solved in a much more elegant, flexible way if anyone at all would just give us a second fucking USB port.

Various interviews. Ideally putting various other things back together thereafter.

Conversely, tearing apart a bunch of things, around my family's house -- invasive vines, old worn-down structures, an extensive amount of brush, etc.

Aside from that, getting a landing page working for my side project along with various ancillary tasks for a demo deploy.

Funny, one of mine also involves trees -- but is mostly outdoor cleanup. The kind that involves decades' worth of it, thanks to what I'll just say is a lot of maintenance that wasn't done over a long time. There's an extensive amount of brush, leaves, etc of varying ages that could maybe be shredded up into something useful, invasive vines I'm still trying to deal with, and more old trash than I've fully figured out how to properly dispose of.

It's turning into various DIY rabbit holes, actually, with the next one (outside of various related landscaping stuff) being to gut a basement.

Just as an FYI, your "link to a project you're proud of" and "link to a piece of code you wrote" questions use different formats, with the latter triggering a submit if you attempt to add line breaks.

Hopefully it doesn't irritate you too much that in order to finish my answers I had to submit this twice.

I know the OP was a mixup, but related question... do you only reach back out if it's for an interview? I had an experience last year myself where I never heard anything at all. Which was unfortunate, bc this place actually fascinated me on a bunch of levels.

Who do you think foreshadowed masculine energy coming back to tech?

GB, with the Box 3 Gavin Belson Signature Edition?

Or Russ Hanneman, with... everything?

(Or was it Jared, with Russ being right about him?)

You mean the one he took "personal responsibility" for, while laying off >10000 people and conveniently still having a job for himself?

I've been on a similar thread w my own crawler project -- conceptually at least, since I'm intentionally building as much of it by hand as possible... Anyway, after a lot of browser automation, I've realized that it's more flexible and easier to maintain to just use a DOM polyfill server-side and then use the client to get raw HTML responses wherever possible. (And, in conversations about similar LLM-focused tools, that if you generate parsing functions you can reuse, you don't necessarily need an LLM to process your results.)

I'm still trying to figure out the boundaries of where and how I want to scale that out into other stuff -- things like when to use `page` methods directly, vs passing a function into `page.evaluate`, vs other alternatives like a browser extension or a CLI tool. And I'm still needing to work around smaller issues with the polyfill and its spec coverage (leaving me to use things like `getAttribute` more than I would otherwise). But in the meantime it's simplified a lot of ancillary issues, like handling failures on my existing workflows and scaling out to new targets, while I work on other bot detection issues.

  Location: MA, USA
  Remote: Yes
  Willing to relocate: No
  Technologies: JavaScript (and some TypeScript), Express, 
  React, Node, Deno, MongoDB, SQL, Ruby, Rails, Tailwind

Email, LinkedIn, GitHub, and a small blog of project writeups can be found on my website at bhmt.dev

General professional background: primarily self taught, through a tinkering habit;[1] spent several years doing various tech ops work, ranging from restaurants to SaaS, before eventually jumping to frontend dev at the latter. Worked in FE-leaning full-stack roles in a couple different fintech companies, but that's more luck of the draw and less any particular attraction to that industry. (I'd like to work in something else, but it's not a hard line.)

Current side project is to automate the act of doomscrolling job boards.[2] I've been building a Tinder clone in my spare time around the results, albeit repeatedly rabbit-holed into various escapades around upstream PRs and efforts to evade bot detection methods.

Other things I tinker with include Llamafile, IoT, creative code,[3] and the occasional CTF puzzle. Areas of curiosity that are not in my background include things like cybersecurity, infra, and eCommerce.

Hard no's: Crypto, military contractors, Amazon, anything owned or operated by Elon Musk.

  [1] bhmt.dev/blog/diy
  [2] bhmt.dev/blog/scraping
  [3] bhmt.dev/blog/sonic_pi

I've got a piece sitting somewhere in my blog's drafts folder that I need to dig up photos for, literally titled "I fucking love Framework."

So full disclosure, even being immensely interested in their mission, I would have waited for the AMD version if my previous machine hadn't gotten wrecked in a car crash. Since insurance paid for it, it was essentially free. But. I've been daily driving a FW13 since early into their launch (Batch 4) and it absolutely holds up.

I'm still on a lot of the original hardware, and some of it is showing its age -- I'm particularly hard on keyboards -- but I'm aware that this is replaceable on its own. I also know I can just get the upgraded battery when my current one gives out, or eventually swap in a new display kit and also deal w the hinges in one go.

One thing that was exactly as magical as promised was upgrading the board. I opted for more RAM over a better CPU the first time but also had weird graphics driver issues under Arch when I tried running games on the 11th gen Intel board generally. Being able to clear up hardware-level issues by just installing better hardware, and then suddenly seeing a huge capability boost in what your machine is able to run, cannot be overstated. (I can also run smaller LLMs on it without pushing the limits of my CPU now.)

Some other gripes/musings:

- The DIY config should just bake the basic components into the up-front price. It's one thing to upsell on more expensive components (different expansion cards for instance), but as a customer it's irritating to see individual upcharges for things like bezels that I need as part of the build.

- Aside from wishing there were a good first-party way of recycling the monitor, I would be really interested in seeing a board that's just a USB hub, enabling the use of the body as an I/O device.

- I realize this isn't a Framework issue, but I wish there were an AMD board with more than 2 USB4 ports.