Anthropic is now too expensive to be acquired. Only Amazon could be a potential buyer, given that out of the 3 big cloud providers, it's the only one without their own model offering.
Git is distributed. Distributed system does not guarantee 100% uptime or real time consistency. You can take the whole history with you and push to a different remote.
Status pages are rarely honest. The company will lie to salvage their SLA. "Degraded performance" or "some customers are experiencing an elevated error rate" should be interpreted as "service unavailable / outage"
I'd be curious by how much they downplay downtime. Wouldn't be too hard to put together an honest status page that pulls & pushes something new to main every 5 minutes, creates an issue, comments on it etc. Very basic high level checks.
I'm not convinced it's deliberate dishonesty. Just a communication disconnect. Firstly, it can take time from the first yellow flags to the full realization that there really is an incident underway, secondly it needs someone to decide how to communicate that incident, and thirdly the engineers who are actually working on the incident need to be able to get on with it instead of being pestered for an update every 10 minutes.
They used to be. Github's is a prime example of how "useful info" has turned into "PR mouthpiece" — it used to display graphs of a few choice Github system metrics, and those spiking could often usefully indicate "yeah, they're having a problem" well before a human could update the page.
But yeah, also status pages seem to be under the domain of non-engineers who are too concerned with how things look, vs. conveying useful information in a timely manner, and ultimately, fail at both.
fetch-pack: unexpected disconnect while reading sideband packet
fatal: early EOF
fatal: fetch-pack: invalid index-pack output
...
fatal: clone of 'https://github.com/libsdl-org/harfbuzz.git' into submodule path '~/src/SDL/SDL_ttf/external/harfbuzz' failed
Failed to clone 'external/harfbuzz'. Retry scheduled
...
Failed to clone 'external/freetype' a second time, aborting
For a problem that's supposedly "fixed" that's a whole lot of errors...
I wrote sth similar for myself, without requirement of USB switch or other hardware. it sends DDC command to HDMI/USB-C monitor and HID++ byte code to Logi MX keyboard and mouse.
Code is too messy to share but here's snippet if anyone want to write their own:
Where could I explore this further? Are these sequences specific to the device?
My current setup includes two Dell monitors (U2415 with 2x HDMI "MHL" inputs and built in USB-3 hubs.) I'm using these with a Linux X86_64 desktop. I also use Logi vertical mouse and ATK (A.JAZZ) keyboard, both on Bluetooth and both also have dongles.
I would dearly love to use the keyboard/monitor/mouse on a Raspberry Pi 5 (BT and two micro-HDMI ports) with a pure S/W based solution rather than spending $$$ for a H/W KVM switch.
Thanks!
Edit: WRT messy code - no judgement, no shaming here. BTDT.
ISBN is the default ID when it comes to book related projects, yes it is convenient but not without its caveats. The often overlooked fact is ISBN was introduced in late 1960s, so books published prior to that obviously does not have that number; and not all countries adopted ISBN from day one, some like China was on its own catalog systems until 1980s; and bc ISBN are usually centralized managed by govt or commercial agencies, censorship with political or commercial reasons are not uncommon, some books were not able to get published, or may only see the world without an ISBN.
For obvious reasons, older / non-English / suppressed books may be those need more care when it comes to preserving.
A second issue is that ISBNs identify a specific SKU (different formats will have different ISBNs, different printings may even get different ISBNs, etc), but book-related projects typically want some way to identify "the same book" across all these different formats, printings, sometimes even editions and translations and collections. OCLC IDs are identifying a different space than ISBNs are.
The biggest problem of all is that there are many ISBNs that have been reused for either a later edition of "the same" book or for a totally different book, which should never happen.
Sometimes it is because people are sloppy, sometimes people try to save a little money (because ISBNs cost money).
* Work is defined as the intellectual or artistic content of a distinct creation. It refers to a very abstract idea of a creation e.g. Shakespeare’s Romeo and Juliet and not a specific expression.
* Expression is the intellectual or artistic realization of a work. The realization may take the form of text, sound, image, object, movement, etc., or any combination of such forms.
* Manifestation is the embodiment of an expression of a work. For example a particular edition of a book or a specific music recording.
* Item is a single exemplar of a manifestation. Cataloguing is generally done, based on an item directly available to a cataloguer
Reminds me of lots of fun memory in last but great days of DOS as mainstream and dawn of Win32.
DOS/4GW was not the only game in town, there were a few of those 32bit extenders, I recall using sth called WDosX to run Delphi compiled (win32) exe in DOS. DOS/4GW was probably the most popular one partly thanks to the popularity of Watcom C compiler.
Pharlap was doing Pmode ;
Zortech C (bought later by Symantec), were doing X32 which was compatible with Pharlap but like 5 times smaller ; djgpp (gnu cpp for dos/win then) had a variation
And you could mix and match (if u have written good parametrized makefile/s that is), i had like 6 compilers vs 3-4 diff.extenders (but not all combinations possible)
interesting times these were. internet? what's that?
- Migrating profile and social graph from Instagram is frictionless.
- Federation is not enabled, and my guess is it’s disabled last minute, bc when you type <at>id<at>server, the first <at> is deleted in your post completely.
- The visibility control is different from most ActivityPub implementations like Mastodon and etc, but more like Twitter’s . Kinda makes sense from business perspective, but will be tricky to see how this works across federated ActivityPub servers.