Well, for one, because xcancel was forced to suspend its service.
There's legal as in "what the law says", and legal as in "what the judge will order you to do", and the latter sense is not as clear-cut as we'd want it to be.
Xcancel was accused of using the twitter API. You don't have to use it. You can have a machine vision model process screenshots. You can also process the Dom. You don't offer a freely usable service or software to the public, only the final result. That final result is opinionated according to the very public accounts you want and does not offer broad scope access to accounts. You do not let the public control it nor provide a product to browse to random or posts about anything like nitter. Or you can process the content into your own news account with ai which is what most news accounts do anyways and then it becomes yours.
xcancel wasn't actually forced to suspend its service. It got two increasingly threatening C&Ds, but nothing actually happened to it, and the creator took it offline in an abundance of caution.
>So you can use more than one iPhone as your primary phone. For example, if you have the new iPhone Duo but want to use your other 'standard' iPhone for the telephoto zoom camera capability, you could transfer your phone number from the Duo to that phone for the day if you're going to be out taking a lot of pictures. When you are done, transfer it back to the Duo, and the Duo will become your primary phone again.
Ah, so the functionality that switching the physical SIM card gave you instantly and at no cost at all.
> Interestingly, to counter the people who say that the best thing to learn from is an actual globe, a couple of children's globes of the world that I had as a child had large metal caps around the axle that obscured most of Antarctica.
"I had toy globes which, unlike actual globes, covered up significant chunks of Earth, so actual globes are bad"
Acme is just a way of calling your company "Best Brand" or "Peak Product" while being just a tiny bit less pretentious about it (and, conveniently, getting yourself listed before "American Anything" in lexicographically sorted lists).
It was only a matter of time before company names like that would be mocked.
That said, Best Buy is still a thriving business / brand (as are American Apparel and AAA).
A long time ago, I wrote an ORM to serialize/deserialize object data seamlessly into SQLite, with massive arrays of floats being stored as blobs.
In code, I could effectively mark which class members need to be stored/restored, and optionally provide a custom serialization function for them if needed.
The latter was effectively never necessary, because all the bases types and multi-dimensional arrays were handled by templates.
Really wish I open-sourced that thing then, but the corporate bureaucracy around that was tricky.
I remember sufficiently little about implementation details now that I think I can get to writing it again, without producing a copypasta of that code - and maybe I should :)
It almost always does. People put so much effort into building layers of abstractions to avoid using SQL, while just writing it directly would be much faster, easier, more readable, easier to maintain, modify, and debug. I do not get it.
>It almost always does. People put so much effort into building layers of abstractions to avoid using SQL, while just writing it directly would be much faster, easier, more readable, easier to maintain, modify, and debug. I do not get it.
When your data is literally hierarchical and all you need to do is read/write one Big Object, "just using SQL" makes no sense.
I used SQLite because it makes a lot of sense to use as an application file format[1], i.e. as an alternative to writing directly to the filesystem.
The hierarchical data was a mix of parameters and huge blobs, so text-based JSON was a no-go, size-limited BSON was a no-go, at which point I asked myself if there was a reason to not just use SQLite, and found none.
The ORM was the smallest part of it, I could have written/read from JSON too, but SQLite was just a far better choice for a mix of structured data and big blobs.
The thing it replaced was writing to a file at a predetermined offsets. Which became very fun as the file format changed between versions and backwards compatibility needed to be maintained.
That was the part I really missed from my Google days.
That, insane achievement badges, and terrible-ideas-discuss (if anyone at Google is reading this, I have one word for you: dirigibles). It was like /r/NonCredibleDefense but for Google.
It's a pixel-perfect modern clone (with some actually useful extras that won't get in the way unless you look for them), and yes, you can clone the repo and run it locally.
So, I take it some Twitter users took an issue with their tweets being redistributed by another platform and sued XCancel?
Because surely you're not claiming that Twitter has any ownership of what gets posted on that platform, are you?
>if you started doing the same to, say, instagram content both meta and individual creators would sue you as well.
By that logic, Meta could sue me for posting my photos on other platforms.
Meta doesn't have a case here, and neither does Twitter, but something tells me Twitter is involved in this nevertheless.
reply