HNHacker News
TopNewBestAskShowJobs

yebyen

2,755 karma · joined October 9, 2012

[ my public key: https://keybase.io/yebyen; my proof: https://keybase.io/yebyen/sigs/Q4xYtntxlQX51bnJaCqx5ERBtsA-G0clfn1VJVEY2F8 ]
submissionscomments
yebyen··on Winter & Cold Weather EV Range Loss in 7,000 Cars
Or in – a battery while charging tends to emit quite a lot of heat on its own, doesn't it?
yebyen··on Read this post ‘unless’ you’re not a Ruby developer
I think we're going to have problems if we try to make all languages consistent for users of all languages.

If and unless are English language keywords besides being Ruby keywords; and in Spanish, the word for "if" and the word for "yes" only differ by an accent mark.

yebyen··on Binance temporarily suspends USDC withdrawals
If your exchange is taking your deposits and market selling them before you have them on the market then they are front-runners and they cheated you.

I don't know how else to say it, your buying power is not their buying power just because they have it on deposit and you trusted them.

That's the thing we trusted them not to do, and that's how exchanges like FTX lose the trust of their customers. If you think this is just the cost of doing business, you're a fool.

Crypto currencies do not take days to move from point a to point b. That is old world baggage.

yebyen··on Just Say No
> Yes it's unfortunate that the alternative is a binary: don't accept issues, or accept having a bunch of open ignored issues,

My whole argument here is the fact that "is there an active maintainer or not" is a continuum, not a binary decision. Any friction we can remove to having an active maintainer remain active, or a new maintainer joining up and becoming active, is a potential boon, drawbacks aside. Stalebot simply removes this friction in the form of "an endless queue of unanswered open issues which you must commit to tackle first." It isn't boundless anymore, only persistent issues will remain open.

If you've ever tackled re-opening a project that has slipped into an unmaintained state for a while you know what I'm talking about. The likelihood that there is anything actionable in an open issue from the distant past actually does decrease as it ages in calendar days and staleness since the last reply. Somebody hanging around waiting for a solution can and likely does take action to ensure their important issue remains open, if it was really important.

Even responding to a stale issue from over a year ago can be a job hazard, as people whose issue was never solved grow more frustrated and irritated about having their problem "bumped" without actually getting solved. It's like poking a bear, maintainers don't want to do it unless they have developed a thick skin of their own, and even then it's not usually a pleasant experience unless you happen to have come with the solution they were asking for in your back pocket.

I would argue that use of stalebot does not increase the volume of issues, even indirectly – the blame goes squarely on users who do not search for their issue before filing a new one. Those users are not irredeemable, but it requires an affirmative commitment to deal with them, and you simply can't decide whether anyone makes that commitment (to spend time dealing with those users) or not. They (the hypothetical maintainer) don't even owe an answer about whether they do.

People begging you to clearly mark your hobby project as unmaintained is another form of social pressure which sometimes pushes people to not publish their work in the future, and that's a shame. You could instead ask if there's a chance that support contracts are going to be sold in the future, but instead you basically "negged" on someone that did something cool for free.

We also wrote a variation on this idea into our governance, because people were asking a lot of questions in Slack that were already addressed by open issues or discussions:

> Bearing in mind that Issues and Discussions are more permanent and searchable than Slack conversations, we can avoid unduly expending finite community resources by searching before asking. If you are not exactly sure how to ask your question or otherwise daunted by the idea of permanence, visitors are always welcome in #project on the (BigCo) Slack.

So...

> Stale bot does not have the ability to ascertain the importance of issues - that's what triaging is for & most maintainers don't have the bandwidth to triage faster than stalebot closes. You are invariably closing important issues to make room for users to re-open already closed issues while completely losing context for everyone. That's dysfunctional and net lossy for your project. If you are, as a maintainer, genuinely trying to triage & respond to issues in this system, you're forcing users to generate a higher volume of issues for you & meanwhile losing out on context of previously opened copies of the same thing. It's a net loss of time & efficiency for a maintainer.

"How many users have filed the same issue" is also a signal you can record and observe, or redirect to the circular file.

It's only a net loss of time and efficiency for that maintainer if they do tangibly exist as a person, and they actually spend that time. This is very much like arguing that technical debt is all wasted time. First, it isn't a waste of time if you haven't spent the time and never do. It's a net gain, "time saved" – until that debt comes back to bite you in the ass. "And that's never a foregone conclusion until it happens, then it was always inevitable that it would."

> most maintainers don't have the bandwidth to triage faster than stalebot closes

This is absolutely true. A problem we can only solve well by having more active maintainers, or less interested users.

https://www.youtube.com/watch?v=LVe0g91yZ84

I think the root of our disagreement centers around whether a large mass of users who believe some issue is important shall dictate whether the issue is actually important or not within any given context.

If users keep opening the same issue after it's been closed before many times, by a bot or not, then there is obviously some disconnect. Users do not get to decide which way the train drives, the person who does the work is the only one who gets to decide (and the person that merges their PR, I guess)

yebyen··on Just Say No
"actively harmful for the vast majority of use cases" but you've discounted the effect of burnout on maintainers, who are the vast minority of individuals.

This effect must not be understated, sustainability is a primary concern, as you'll see at the top of this thread, I started with "not every project has an active maintainer" - this is not always a state that arises in a perfect vacuum or even over a well-defined span of time, when an author loses interest in their creation and stops contributing to it. It is a terminal state in a state diagram with many open loops, and perhaps one to be avoided if you're keen on maintainers triaging issues! But also sometimes unavoidable.

If the active maintainers are all chased away by hungry users, clamoring for architectural changes without a full understanding of the project and how it's designed to work, then there is value in a bot chasing away the people who are just window shopping for something completely else than what you sold them, or even what else you had planned in your as-yet unexpressed vision for the future.

Spending the spoons required for an interaction is not without a compounding cost in all cases either. If your response is not simply accepted, or it's actually reiterating just what you already knew the user didn't want to hear, well... you've now entered the "bargaining" or "negotiating" phase of issue triage, and the next step is... well, another step

I negotiate with those users because they usually have valuable insights hidden inside of their pain! Our lead maintainers would spend time doing the same, but the more time they spend on that, the less time they have to spend on writing code and actually developing the software.

See how this model basically hinges on adding more people to the maintainers team as the user base scales up? And to the point, sacrificing some of their labor in service of triage role activities? If you are a single maintainer for many repos, you desperately need to avoid becoming a customer service bot for your non-paying customer-users. Spending time servicing those users can result in negative feedback loops where people expect more attention just because you gave it once. This has not been my experience most of the time, but...

...And that's not to say the issue queue won't be used for something else... but... maybe just your issue didn't make the cut. And that's not an affirmative value judgement – it just means maybe it did not make the cut for that maintainer's roadmap, who owns the queue, even if such person currently exists. Like I said, nobody signs up as "repo owner" when they publish their work, but it is their queue.

Suggesting that someone turn their issue queue off is a bit presumptive about the possible reasons why your issue was ignored, or why a bot is needed to help keep the issue queue clear enough to be able to easily find out "what's new."

It really might not actually be that they ignored your PR/report just because they want to kill the project? Maybe they really genuinely want the issue queue cleared so that important issues can be given faster attention when they are re-raised because they are important to someone subscribed.

If you've gone to all the trouble to track down 16 issues that provided details about the same report when they were all closed then you know it's possible, they aren't inaccessible just because they've been closed; it's just a bit frustrating – maybe also notice an important indicator of the volume over quality of the average issue submissions that 15 people didn't search well enough to find a closed issue that was a dupe of their issue! Did they even search before posting at all?

Anyway, if you're doing all that, then bottom line you should absolutely be a maintainer. Add yourself to the MAINTAINERS file and then go ahead and turn that stalebot off! ;)

yebyen··on How We Built Fly Postgres
That is assuming you're successful (or at least have a busy storage tier.)

I think the people who are doing this calculation wrong are mostly confusing and conflating those two outcomes. Just because your database servers are very busy, does not mean your product achieved some commercial success. You can't just pay extra for the full-service treatment and expect to receive a commensurate output in value,

(and the people who won't pay for a real person to own their databases full-time are likely in a circular Venn diagram with people who won't pay attention to optimizing their database queries, so your point can probably stand unmodified... except there is an important case where the PaaS provides value, and it's nearest to the starting point of practically everyone.)

If you look at every dollar spent on IT/databases as a sunk cost which cannot be recovered from future recurring expenses, it's very bleak indeed to put pennies on top of pennies and pile them higher every day... or you could pay attention to the signal that SaaS is providing every month (the bill for usage), and ramp up the attention paid to optimizing queries before it gets too late in terms of dollars and cents? The dollar impact of slow queries cannot be understated.

But some business ideas will also not ever make it that far. You could spend the money on DBA salary or DIY and never know how much it was really being wasted, comparatively, if you didn't ever get a handle on your own usage metrics.

yebyen··on Just Say No
I avoid stalebot for the reason you describe, because I want a maintainer to be reading and triaging issues, and I am in a job description where I can reasonably anticipate to be that person at least 40% of the time, even if I may not be coming through often enough (with a high batting average.) I'm really lucky to work for a company that can prioritize this type of interaction!

But when maintainers are overextended or nobody is able to commit that way, I see the value of stalebot. I spent a year closing 400 issues by hand for a popular legacy tool that we were actively telling folks not to use, nearly already on the day I started working on it. They were all so grateful to have someone reading over their issue and for the community goodwill it created, it was definitely worth it – for me. Different value systems and judgements may not make it so valuable. To be as direct as possible, I have 0 information on whether any of those grateful people were ever converted into paying customers of our company (and I like it that way.)

Was it worth it in engineering dollars, or if you measured the output of the time spent reading each issue in terms of how it influenced directly on LOC output from my brain to my keyboard? Definitely not (at least not yet, short-term.) We kept the lights on, and the exit door illuminated, to demonstrate a commitment to support. In service of governance and long-term stability guarantees!

Would we have gotten people off the boat faster if we had gone ahead and decided to pre-emptively close every issue that was not likely to get attended to, based on engineering effort/$$ calculations with low information about each issue? Very much possible. Some people may have also gotten alarmed and decided to swim from there, rather than trust our lifeboats to take them somewhere safer. See how stalebot provides value in this case, if "abandon ship" is the message you want to send ;)

I may have made your (their) point even better for you, my point is simply different value judgements based on different calculus.

yebyen··on Just Say No
Maintainers are great, and working open source projects are good, but not every project has an active maintainer, and it's my opinion that practically no one in Open Source signed up to be a "repo owner", unless they've gone to the trouble of developing some kind of governance structure to signal that they should be counted upon for support. That signal is an affirmative signal though, it's not implied.

If you don't get a reply, and a robot closed your inquiry without comment then my guy, it seems that the signal has been sent clearly and received! If you disagree the fork button is in the upper right hand corner, you are the maintainer now!

I don't mean this to be disrespectful, but there are a lot of open source projects supporting companies and the companies often don't contribute back in any way. So while I appreciate the PR, and I'm going to be as polite as possible before I close it, not everyone has time for that, and nobody owes it.

yebyen··on Twitter’s mass layoffs have begun
If you want to work there, fine, I hope it pays well! But I'm telling you, I saw a tweet when this all began about how someone once set about $2B on fire to buy Yahoo! and what fun they were looking forward to having (as a Twitter user) helping Elon set the new record for cash bonfire volume and speed-run, and from my perspective we are now watching that play out in real-time. I don't want to work there, I don't even want to be mentioned in the same sentence as there. You can find me on Mastodon from now on.
yebyen··on Twitter’s mass layoffs have begun
I can't quit working at Twitter because I already don't, but I am downloading an archive of all my tweets as we speak and I'll be having my finger on the trigger to delete my whole account, which I'm totally sure coming from me, a nobody you never heard of, is, like, an equally serious threat – I mean seriously though, have some solidarity with the workers. Do you want to work under those conditions?
yebyen··on Twitter’s mass layoffs have begun
So Twitter employees can work at home "forever", but they should work 80 hours a week while under explicit threat of layoffs, and return to the office for 12 hours a day, meanwhile the office is closed, go home if you are in the office now!

This is really what has happened inside of just the last 8 weeks. I can't blame anyone who just can't keep up, especially while that 12 hour a day death march was going on. This is really not how you should treat people, even for a day.

yebyen··on Show HN: I made a CMS that uses Git to store your data
Misleading users for GitHub stars... that's a paddling!

Maybe it's like the YouTube Like and Subscribe, except for the part where they contact you for new releases. It's a lot less pushy to tell people to star your repo than asking them to subscribe to issues and become a contributor on equal footing.

You need something like "stars" or "project member" as part of your contributor ladder.

Did you know that YouTube channels cannot get a non-randomized URL or be searchable by the channel title unless you have 1000 subs? (How do you get 1000 subs when nobody can search for or find your channel unless you hand them a link? I guess by pounding pavement...)

As an OSS maintainer, I don't think that stars do anything except for number go up, but you'd be surprised the things that "number go up" can help with.

yebyen··on Facebook reportedly laying off thousands of employees
No need for egregious hyperbole, there are well more than 10k iPhones in the USA
yebyen··on The PS5 Has Been Jailbroken
Just google USAF PS3, it was called the Condor Cluster and it was big news in 2010 when the PS3 was still new. It has also been covered more recently.

The USAF also has Kubernetes in F-22s from what I understand now

yebyen··on Pregnancy-Related Deaths: Data from Maternal Mortality Review Committees
I had a search because I didn't believe that any states required employers to offer paid family leave. Some research revealed that the situation is somehow both better than I thought, and also seemingly much worse than I imagined:

https://www.ncsl.org/research/labor-and-employment/state-fam...

https://www.zippia.com/advice/average-paid-maternity-leave/

There are a few North Korea comparisons in here that I think are tongue-in-cheek but two statistics jumped out at me:

(1) 1/3 of new mothers take little to no time off after [...] new child and instead opt to return to work as soon as they’re able

(2) The highest rates of paid family leave across any segment or industry appear to be in the 30% range. So only 30% of the jobs most likely to offer this benefit actually do.

yebyen··on Bitcoin Is Digital Scarcity
It doesn't even have to die out in order to ruin you. As you mentioned, you can go bankrupt from insolvency. You don't even have to directly use leveraged trading to purchase the Bitcoin to get bit by this. It just has to become a too-large proportion of your assets on your balance sheet, and the space it occupies feeling comfortable enough that you can take out as many loans as you want for other things you need.

"Because no way am I killing my golden goose, but I might as well enjoy life"

(PSA: Pay off your loans when you can, it may occasionally look like this bull run can never end. It will always end!)

yebyen··on The PS5 Has Been Jailbroken
IMO that is Sony's problem, selling special purpose hardware that could be general purpose but locking it down so that your business model is secure... after the point of sale... seems a bit sneaky.

I enjoyed many hours of gaming on the PS2 and I bought it (in part) because I would be able to install Linux on it. I still managed to become a Linux guy today, in spite of the rug by Sony, and I suppose there's nothing overtly wrong with clarifying with an update that the primary intended use of your product is in fact its primary intended use, but as a hobbyist (dang it, now I've gone and done that again)...

yebyen··on The PS5 Has Been Jailbroken
Seriously a bit miffed at the characterization of people who have bought a piece of hardware to install Free and Open Source Software on it (and then been absolutely rugged by the manufacturer) as "pirates out to save/make money, and hobbyists too"

Every business I have ever worked at has either been built almost exclusively on Open Source software, or a bank that ran almost exclusively on Microsoft.

We're not just pirates and hobbyists!

yebyen··on The PS5 Has Been Jailbroken
Yeah, hobbyists like the US Air Force Research Lab

(I imagine, I don't have any info to suggest they actually had to literally jailbreak their PS3s in order to build their supercomputer, but just making a jab)

If it's good enough for the USAF, it should be good enough for hobbyists to have a go around with it!

yebyen··on Baker's Math (2009)
I think people who are downvoting must have misunderstood the joke. The joke is, add more butter. It's like estimating for an engineer, or adding the appropriate amount of salt and spice for a midwestern home cook. You can never ever go high enough. Whatever you were about to do with the butter, just multiply it by 3x and add 50% more on top again after.

(The one weird hack you wish you didn't know about your favorite restaurants' most flavorful dishes!)

yebyen··on Non-Code Contributions to Open Source (2021)
> don't necessarily need to be done by a developer

Yes and no. They need to be done by someone with developer empathy, for example a hyper-enthusiastic user champion, and hands-on problem solving experience definitely helps a lot.

Reproducing bugs and triaging issue reports does not require the skill of reading and writing code, it does require the skill of systems thinking which is IMHO a developer trait.

yebyen··on GitHub Actions Pitfalls
Maybe the premise of my question is about an entirely different misunderstanding then. There is a locus of control issue, and a story about how the original permissions model of GitHub Actions was chronically broken.

It's "pull_request_target" that I'm thinking of:

https://github.blog/2020-08-03-github-actions-improvements-f...

> In order to protect public repositories for malicious users we run all pull request workflows raised from repository forks with a read-only token and no access to secrets. This makes common workflows like labeling or commenting on pull requests very difficult.

> In order to solve this, we’ve added a new pull_request_target event, which behaves in an almost identical way to the pull_request event with the same set of filters and payload. However, instead of running against the workflow and code from the merge commit, the event runs against the workflow and code from the base of the pull request. This means the workflow is running from a trusted source and is given access to a read/write token as well as secrets enabling the maintainer to safely comment on or label a pull request.

That's the user story I was thinking of. Completely unrelated to the default branch issue that GP was describing, I guess.

yebyen··on GitHub Actions Pitfalls
There's something in here I don't understand, and I thought I knew the reason why it does this (for at least some workflow types, maybe not workflow_dispatch)

If you're only free to run those workflows when they land in the default branch, does that also mean that the workflow that runs is the one from the default branch and if you change the workflow in a PR, it will only run the new workflow on merge?

I know there's something in here to permit non-owned commits (from an external contributor) to be tested against a trusted workflow from the main branch, but I don't think it has anything to do with workflow_dispatch. I would expect that if you're able to run workflows and target any branch, then if the workflow you run is the one contained in that branch, you'd be able to select any workflow that is named and defined in the branch's configuration.

I'm not saying that's how it works, I'm saying that's how I'd imagine it to work. If someone knows "the rule" that we can use to disambiguate this and understand it from the precepts that went into the design, maybe speak up here? I don't get it.

yebyen··on In 2019 RX470 were $70, RX580 $100
Yeah if you're in for a penny you're in for a pound as they say. Sometimes I think that most of the algorithms should just go away and we should just trade 10 times a year, from a spreadsheet. Then I remember that those algorithms all came from the primordial spreadsheet soup, and just laugh.
yebyen··on In 2019 RX470 were $70, RX580 $100
This exactly. Unless you're using a suite that's specifically built for crypto traders, there's no way the software can know that income on day X (which you pay income tax on) is from the same bucket that an asset as was sold later on day Y.

You have to tell the software about your cost basis, which is only a problem if you're mining. It's smart enough to figure out buying and selling on the same platform, but it is not smart enough to figure out that some income was related to later sales and track your cost basis unless you make those connections yourself.

yebyen··on In 2019 RX470 were $70, RX580 $100
When you count your income from mining, you need to create an equal cost basis at that time. The value of the coins when you received them is your cost basis. If you didn't do that, you paid way too much in taxes.

(If you hold them for longer than a year before you sell them, you can be paying long-term capital gains which is cheaper than short-term. Unless you're in losses in which case it doesn't matter.)

yebyen··on The Ethereum merge is done
> "normies"

The context was "us normies"

I literally just came here today to tell everyone that I learned something, and you ruined it. You raised the bar, it's no longer enough that I learned something, I have to make it accessible for everyone else too, or I am a bad person. Thanks.

yebyen··on The Ethereum merge is done
You're not responding, you're just condescending, and you've only quoted from the parts you cherry-picked as you could easily be responsive to them.

What is a qualified investor? And why do you have to be one if you want legal access to unregistered securities?

yebyen··on The Ethereum merge is done
> I did try to engage in the discussion.

Go back and read it. I'll give you the benefit of the doubt now, but you did not. You threw barbs and used the word "scam" as often as you could, and told me I'd be likely disappearing in a few minutes. Then someone showed up to comment on how disappointed they are I didn't really disappear like I promised. Can't win for losing. This is exactly like every crypto discussion on the internet today, it's very frustrating. I hope you know how difficult it is for me to be this patient. (It actually reminds me a whole lot of doing Ruby evangelism in almost the same circles...)

> how easily accessible those traditional financial instruments are

> I have some money invested in risky assets that in the past two months sank 10% due to the way the world is right now

I'm talking about deliverable perpetual futures. If you had seen this coming, you could have done some short-selling to hedge your risks. Price goes up, you deliver and sell for a profit. Price goes down, you still have your asset and can cash out for a profit. Is that a service offered by your bank? Not mine...

But maybe your bank offers it ...maybe only to qualified/accredited investors? How do I get that?

Now perhaps you see what I am getting at? It's not accessible, no matter how many books you read. Go out and get a million dollars today, through some act of God, and you still won't be a qualified investor next week or next year. Or you can wait for SEC approval, and then you can go get them through your broker I guess.

Some people read books, others are not well-served by book learning. I looked for a book that could explain it to me, but ultimately I only learned by getting hosed using these instruments flatly incorrectly until I figured out what I was doing wrong, by using them, and observing the outcomes, then also asking for help. Lovely people answering questions to help others learn. (It was the friends we made along the way!)

Is there some reason the system is the way it is? Yes, I'm sure there is. Does it protect people how it was really intended, or does it actually mean it just remains inaccessible to most people? This is how crypto levels the playing field.

Does that mean you cannot cut yourself when working with the sharp object? No, it definitely is not safe to go alone here. There are a million and one ways to lose all your money, plus a million new ones that weren't possible before. And soon a new technology will come, and everyone who understands the current landscape will know immediately what to do with it, (and everyone who has had their head in the sand will wait for the SEC for guidance, and eventually begrudgingly accept the improvement, maybe, once all the life has been sucked out of it by bureaucrats.)

yebyen··on The Ethereum merge is done
I haven't made any claims. I said I learned something, and your buddy disappeared without explaining how to do the same thing I said I learned how to do as he said was "something you could always do," while shouting insults at me on his way like I'm somehow the one responsible for the Crypto-calypse. I'm not, and you people need to get over yourselves.
← PreviousPage 5 of 34Next →