This is a known bug in projects generated with `create-shitbowl-app`. You may need to clear the cache and upgrade to the latest version of the S6L framework
Add a wildcard forwarding all emails to your primary email address. When you sign up for a new account at Example Co, use [email protected] as your email. This way, you can’t be easily identified via email, your accounts can’t be matched via email address if your data is sold, and if your data is sold/breached, you’ll know the culprit because all the spam will be sent to a forwarding address with their name.
My actual recommendation is to use GraphQL instead. But I assume that’s not an option.
OpenAPI is the way to go. The official client generator libraries are fairly consistent in my experience, albeit the design patterns sometimes stray outside ecosystem standards.
Alternatively, you could add JSON-Schema validation & schema endpoints to the API’s, then use a library like QuickType to generate types. Or even setup sample requests for each endpoint then use QuickType to generate types based on the response JSON.
True. But after spending a long time looking for the “JavaScript Rails”, I realized that I didn’t actually need an ORM. Learning SQL is just as difficult as learning a new ORM’s API.
Slonik + Postgres + Graphile is now my go-to.
Yes. So long as you do it morally. Your project must extract novel insights from the scraped content, not steal it. Some of my most successful projects have been a result of web scraping.
However, there are caveats.
1. If the scraped website receives frequent updates to its html structure, you will need to update your scraper frequently. This can turn your codeitonceandforgetit side project into a monthly maintenance headache.
2. You are entirely dependent on that site. If they shut their doors, or start blocking bots, you have to find a workaround or shut down your project completely
Ultimately, I would recommend it as a means for quickly attracting users, or as automation for part of a larger project. Ensure that the value is > the maintenance.
No. But one could use a smart contract to strongly disincentivize themselves from uncovering their own treasure.
E.g. Smart contract sends 20% of total treasure (in cryptocurrency) back to the hider each year until the treasure is withdrawn. Treasure can only be withdrawn by the finder address linked to the paper wallet (private key) that was hidden. When it is withdrawn, it sends the finder 15% of the remaining treasure each year, to an address of their choosing.
This way, it’s almost never worth it for the hider to uncover their own treasure