About memories - throwing away the associated item often feels like admitting that you can't go back to the moment represented by the item. It's hard to face that small grief so it's easier to keep it there.
292 karma · joined May 15, 2016
About memories - throwing away the associated item often feels like admitting that you can't go back to the moment represented by the item. It's hard to face that small grief so it's easier to keep it there.
It would be really great to have some GUI frameworks for the common platforms (including web!) designed to do this and have some opinions on common shortcuts for common actions so we can standardize on something.
> We had to change them all
It's still valuable to raise the cost of scraping of course. I don't think anything can really stop a determined scraper from impersonating a human. I wonder though if a system similar to Anubis but mining some crypto would make bots _welcome_ - since they're paying for their traffic.
The solution my team eventually settled on to the dedup, buffering, and race problems was:
* When a webhook came in, store a single copy of the payload (usually json) in some temporary storage and enqueue the id.
* Any subsequent updates (while the id was enqueued) overwrote that payload and skipped the queue.
So, we were able to ensure we only updated the object once and with the latest state (since the webhook payload always held the entire object state).We didn't have a great solution for the bootstrap problem though.
I do like the SCROLL proposal, but I wonder about the cost of keeping around log-structured data forever - every log structured DB I know about does compactions for this reason.
Still good news for those wanting to see broader Linux adoption, but the news really is the usage was correctly recognized as Linux for the first time.
Form tags usually contain other elements - textboxes, checkboxes, etc. The url and method are specified on the form tag and not the button, so if you want a second submit button that goes to a different URL or use a different method, you need to duplicate all the other inputs in a separate form tag with your button.
All of this can be done with scripting, but the point of this proposal is to make that unnecessary.
Amazing line.
Yes this does threaten Blizzard's business model so I understand why they'll go after Turtle, but that doesn't mean we have to care or let them prosecute Turtle for Contempt of Business Model.
Now, if Turtle used Blizzard's WoW trademarks to advertise and make money, I fully agree that violates their _trademarks_ and can be litigated as such. But if Turtle somehow didn't do that (and still sold access to their compatible WoW backend), I'd be interested to hear if that is somehow still a copyright violation.
I think this is referring to the Japanese rail payment cards? I know you can use them on things like vending machines, but from the article it seems like the Triforce cabinets let you save game progress on them too, which would be a great feature I've never seen in US arcades.
That's the theory, but I don't know how far LiteBox is along to supporting that workflow.
Then there's things like the folate blocking antibody (https://pmc.ncbi.nlm.nih.gov/articles/PMC4783401/) which you can do a blood test for, but again not all people with autism have the antibody.
If anybody has any ideas I'd love to hear them.
- Money (the concept) is useful to society as a store of value, so you don't have to waste effort bartering for things.
- Adding on to that, credit is useful to society since it lets humanity even more efficiently allocate its good and labor (stored as money).
- Finally, stocks, insurance, and other financial instruments are additional advanced developments on top of credit, where groups of humans (companies) can take on even more risky endeavors supported by investors or insurers.
So my view is companies like Jane Street facilitate these complicated value transfers, to let (e.g.) a spaceship company draw on resources generated by growing crops, selling shoes, giving haircuts, etc via a convoluted path through stocks, ETFs, whatever.
In 2010 or so we tried to adopt Mercurial at the small company I worked at, but the support for Git was just so much better - even back then. Git's popularity meant that tooling, documentation, and general ease of finding people to ask questions was 100x easier with Git, so we switched. I'd imagine the same thing played out many times over.
A few FAANGs did and still use Mercurial, but they're on their own islands and don't really affect the wider tech ecosystem.
For my Kobo, I wrote a mod that lets me redirect Pocket API requests, and a small proxy server that translates Pocket API calls into Readeck calls.
So far it's working flawlessly and my Kobo is using its built in Pocket viewer for Readeck instead. I'm hoping to open source it soon so others can use it.
It took so long to move tapes around and read the sequentially (no random access!), and as the data corpus grew it got harder to have a practical backup, even though the data was still theoretically extant.