pqdbr

From the Pricing JSON page, on the 'Why Each Plan Must Have At Least One Feature' question, it says:

> Without this restriction, it would be significantly more expensive to fetch your pricing model from Stripe's data.

I didn't quite get that. I understood that application code should reference features (and not plans directly) so it becomes easier to change plan structure (via https://priceops.org/4-entitlement), but that's not the reasoning laid out here, is it?

As a Stripe customer, I think that the principles on which Tier were built constitute best practices that could have been taught to me by Stripe docs.

For instance, the idea that plans should be treated as immutable (and versioned when changes are desired) and that we should attach application code to features (and not directly to plans), having a lawyer of abstraction that links features to plans, could have been laid out to us at the very beginning of our integration.

They seem obvious in retrospect, but one is not guaranteed to derive them on first try; the fact that they wrote https://priceops.org/4-entitlement is telling.

So building an actual business, by providing a service that other people see value in, and decide to pay money for, is "everything that's wrong with our society"?

@dang Maybe you could add a [Loud sound] tag on the title. I clicked on it without knowing and blasted a huge noise from external speakers at midnight.

Wife and neighbors are not happy.

Care to elaborate? I’m a fullstack Rails dev for 12 years and I had no idea either, just like OP. Why alienate potential users from the get go?

Those are crazy ideas. I love them. Anywhere they have been experimented with before?

I think you answered your own question about what this is supposed to tell us.

I’d love my child to long being an astronaut, and all the studying and life choices it will impose on them. Can’t say the same about becoming a TikToker.

Just found this on the Apify documentation: https://docs.apify.com/tutorials/log-into-a-website-using-pu...

Is there a similar guide for Crawlee?

This looks really great. However, I can't find examples of how to handle scraping behind a login or a paywall, without having to 'type' credentials every time.

I actually got really excited after reading the article, and the entire piece is about how "down to earth" (pun intended) the technology being developed here really is.

They are going to great lengths to make it compatible with the existing power grid (just replacing the heat source for current generators), re-utilizing abandoned mines and all.

So, would you care to elaborate why you think it would never materialize?

What was your prompt?

Does that also include the very tiny little dots? I have the same question as OP, and I thought the tiny dots were single stars, and the little bigger ones (brighter) were galaxies.

On the agreement he signed, maybe?

If, like me, you read "Axios" as that js library, and PR as Pull Request, you too, my friend, need to take a break.

Now with Turbo, Rails is very opinionated about the frontend side. Which is a great thing.

My productivity with Rails 7 and Turbo has never been higher.

I'm having '500 Internal Server Error' (nginx) on a regular tab, and everything working fine on an icognito tab. Go figure.

With Ruby, `ruby -run -e httpd . -p 8000`

I also went with keychron a year ago and I’m very pleased. My only complaint is that battery is shitty if you use the wireless mode with the led backlight on all the time (it will last about 4-5 days max).

Not op, and I’m on the phone so can’t post an example. But I just wanted to add that Rails + Vue (only for those views that require heavy reactivity) is the most productive stack I’ve ever worked.

It's a shame the article ends with "So as usual, consider not writing Ruby, but if you do, ...". That's worthless advice and many people, myself included, have Ruby as their most beloved programming language.

Would love to know more about how you set this up.

Lol, good analogy. “But can it run Rails?”

I started a new company at the end of 2021 and I chose Ruby/Rails ... once again.

He was being ironic

I only did 13, and got 100% right.

The backend should use an exponential backoff to block repeated failed MFA requests within a short period of time like the one demonstrated in the video.

Longtime customer here (10+ years). I can only hope that now they finally set up a datacenter in Brazil!

Does anyone know any open source library that provides this feature as a widget for a web app?

I’d love to use Rails active storage + S3 to allow users to have a “mini Dropbox” inside my web App; the only one I could find that was nice enough was CKFinder, but it’s not open source and it’s tied to a Java or PHP backend as well.

I'm giving you some pointers below but the best thing is to get proper training from an instructor. Helping you choose the right equipment for you is a big part of it.

Your equipment has 3 main components: your engine (check out Vitorazzi, their "Moster 185" is definitely the most popular engine in the world), your cage (check out Parajet https://parajet.com/ - they have some cages already assembled with the Moster 185) and your wing (I fly Ozone - https://www.flyozone.com/paramotor/).

Just google for paramotor training, there are many schools in the US. I suggest get training near the place you plan to do most of your flying, because flying at the beach with constant, laminar, mid-strong winds is very different than flying at the countryside with bumpy and low-mid winds.

If in doubt, learn to fly near the beach. The views are amazing :)