It’s probably not too important to choose a service that you think you can trust fully, because that trust might be broken at some point. But having an identifier that can be swapped to different backends, so people can find you again when the host inevitability changes, is a stronger strategy.
I think the importance of owning domain names will increase, and using those as the canonical identifier of a project will give it more permanence. The procedures for seizure and censorship with domain names are better established and understood.
But consider how, in just a short few years, tools will have changed so much that even achieving this specific look will not even be possible (everything is in the cloud and normal users can’t even run them locally)
We’ll inevitably end up feeling nostalgic for these mid-2020s AI slop menus, much like how graphic design of the 90s and 2000s is revered (see other comments on this post) even while during its making was regarded as garish
I find myself holding onto and preserving general ephemera and just happened to scan a moist towelette package over the weekend.
My collection mostly consists of business cards and dry cleaning type carbon copy receipts. I need to better catalogue these and share online.
A few business cards: https://ivan.sh/biz-cards/
Going to "modernized" restaurants is just a drag. I don't want to touch your tablet or scan your code. I much prefer the restaurants which only accept cash
There's also the global gitignore configuration (core.excludesfile=~/.gitignore_global), which for me contains things like: *.swp, .DS_Store, scratch, etc.
This seems very low. I have not worked in professional screenprinting environments, but all resources I have seen indicate potential for hundreds or thousands of high quality prints from a well prepared screen.
Yeah I’ve had this same idea for the same reasons, and came to the same conclusions that without legislation, no incentive exists to send statements as attachments in emails or to store them with a 3rd party where they can’t be tampered with when a mistake is discovered
I think going from code to OpenAPI makes a lot more sense, at least for strong typed languages. And even if not directly translated from code, at least closer to the actual code, in annotations or something. Generating the spec from code removes a step, where you simply need to update code, rather than update the spec then update the code
vim-rest-console[0] has been my Postman alternative for years. It basically wraps curl and makes it super easy to make different requests from a single text file. Can even write YAML and have it converted to JSON before being sent in the body. Really great tool