@inthehands@GhostOnTheHalfShell@cryptadamist If you're seeing a single price listed on a stock, that's the per-share price of the last sale on a public exchange. For historical values (like yesterday's price, etc) it's the sale price of the last sale in that period (aka the closing price). If there's not enough volume to give real prices, then your brokerage might just show the open bid (offer to buy) and ask (offer to sell) prices.
This knowledge comes courtesy of building trade ticket UIs for 5+ years at Schwab and Fidelity
@inthehands If they can just revoke degrees, where does it end? What's to stop them from retroactively revoking scholarships? Or from modifying the authorship of papers? Why not revoke the enrollment itself? If a president, or a donor, or a regent just doesn't like you or your politics, it seems that Columbia thinks they can just obliterate any portion of your life that has touched that university.
@mattly No it does not. But I want to live in the timeline where Mozilla does good things a little more often. Or at least doesn't consider the good things they've done in spite of themselves to be mistakes that must be expunged from history
@mattly ok, but in this same vein, do you plan to cover security questions? Because among my many complaints with those is that I think it's wildly unreasonable to expect me to remember how I capitalized my answer about my childhood pets or whatever.
@inthehands Um, yes, but also no. Commit messages are memory aids, and the more they're asked to do beyond that scope, the less useful they are. So, the level where you add in team members is to recognize that team members might sometimes ask you questions like, "do you remember that bug you fixed? How did you do that? Because I think this situation is similar"
If the author isn't around to ask, the commit messages aren't going to fill that gap.
@inthehands The hill I will die on is that version control systems, and thus the messages attached to commits, are for versioning sources, not finished artifacts. Many many attempts to enforce a commit message standard are made in service of turning commit messages into release notes, and this is bad for everyone.
The essential purpose of VCS commit messages is to make commits findable. Do whatever makes them findable for you, the committer.
@mattly I'm not even sure how much git being distributed is contributing. I think you run into the same problems if you try to pretend that SVN is a package manager/registry. The capabilities and affordances you want when you're building software are almost entirely unlike what you want when you're distributing it. More than not, they become liabilities