You'll probably be fine, but you'll definitely need to flag the stream as 18+ only. That might affect your advertising revenue, so consider that if your stream is not 18+ already.
Twitch hasn't been profitable a single day of its existence. Kick can afford to pay 95% to its streamers because the platform is basically just a giant ad for their gambling business, the real revenue driver.
You just needs fields = ['__all__']
. If you want all fields in the nested serializer, you need to set it on that object.
Signals aren’t discouraged, but it’s easy to make things a signal that probably shouldn’t be. In my experience, this comes up a lot when figuring out how to handle logic that shouldn’t be in a view but is intrinsic to how my models relate to each other. There are lots of articles on this.
Because of that, it’s a good practice to think hard about whether there are other ways to do the same thing before resorting to signals.
You have to setup nginx and not use run server to start your app, look into gunicorn instead
This. Django is a framework. Not a production web server. You need to set up a web server, and then configure it to host Django. You can google a lot of tutorials for different web servers to do it.
It isn’t wrong, but you’re missing out on a lot Django has to offer in the long run. If you just need a framework to handle routes and views, Flask may be a better fit.
wtf do they want then?
Let them stay home to put human lives over profit? Not to be forced to return to a dangerous work environment? To not be treated as human machinery under the guise of being "essential"?
Do you realize that if not for Amazon and other delivery services way more people would be going out to buy stuff, in many cases risk groups? That if we sent those workers home the end result would be way more people getting sick?
Did you even read Bezos' word about Amazon actually LOSING money the next quarter because they're investing $4b on safety measures?
Demonising Amazon
Amazon doesn't need any help from journalists to look bad. It's OK to be critical of a multibillion dollar corporation run by a trillionaire. If everything is hunky-dory, they should release the numbers and be totally transparent. If they have nothing to hide, they shouldn't be keeping worker deaths from their colleagues.
It's OK to be critical. It's not OK to blame them for everything just because they are a multibillion company. This article is crap and the data doesn't support these attacks. Envy, on the hand, explains things much better.
Short answer is yes. How you do that depends on how you intend to use it. If you want to embed it in another Django project, run a command line script, use it like a library, etc. Without knowing more it’s hard to advise further.
No Keyra-Seb-Jet makes this list cry.
I would love an invite!
It is but I only accept people who let me know what cool stuff they can bring first
haha sorry about that, I just looked at what people were responding with.
I don't have any of the stuff you're looking for XD and I only have one gold at this point. GL! Thanks for sharing in general!
waitlist if actually still happening :)
also in :)
Also 105 I would love an invite.
Installing zipline across Australia let’s go!
I lived at 399 for a year facing the bay bridge. Really amazing views day and night.
This was the first year it was open though, and the elevators were always broken.
Couldn't deal with a 30 minute in building commute to my apartment
I live there now. It hasn’t gotten better.
Something I really love about Django is that you don’t need to understand everything it’s doing to get started and feel like it’s useful. DRF isn’t like that.
DRF is one of those frameworks that’s hard to use unless you really understand every part of it. While what you’re doing isn’t wrong, you’re leaving a lot on the table, and it’s likely because you don’t know everything it can do.
I went through this with DRF. It wasn’t until I dedicated some time with the documentation to really understand how DRF approached things that I got over it. Don’t know if that’s what’s blocking you or not, but maybe it helps.
Read moreMy guess is this system Jeff is alluding to allows balance updates without a client patch. Overwatch has a huge QA window because of OWL and because Blizzard emphasizes client stability. Unless they’re hotfixing, their turnaround on development seems to be about 3 months. That said, if all you’re doing is adjusting how much damage Sigma does per shot, that shouldn’t require a whole patch with a full QA process.
That said, it isn’t a sexy answer to the problem, so I imagine that’s why he filmed the dev update a while ago but hasn’t released it yet...they are editing to make sure it adequately explains what they want to do.
I could be wrong, but I’ve shipped a lot of software. If I were trying to solve Jeff’s stated goals that’s what I would do.
Read more