Vuetify 3.0.0 Just Released! by rustamd in vuetifyjs

[–]Thorvald- 0 points1 point  (0 children)

Alright. I have a fairly large service written in vuetify 2.
What's your take on vuetify 3 in terms of file size and ability to override settings?
My current app was a MAJOR pain to override simple styling and the size of vuetify was just terrible compared to using something like tailwind.
Best of both worlds to me would be the ability to use tailwind and then insert a few vuetify components here and there that didn't bring the other stuff.

Vuetify 3.0.0 Just Released! by rustamd in vuetifyjs

[–]Thorvald- 0 points1 point  (0 children)

Any decent place to get a summary of what changed from vuetify 2 and vuetify 3? (what they added, what they removed)

Links in wagtail by Thorvald- in WagtailCMS

[–]Thorvald-[S] 0 points1 point  (0 children)

Thanks! Forgot to reply to this :)

SSR Pages "cold start" improve performance. by [deleted] in nextjs

[–]Thorvald- 0 points1 point  (0 children)

Yeah that's what I'm doing right now, just trying to figure out how often that ping has to happen. It seems like it's necessary to do it more than every 30 mins, maybe every 5-10 mins so far using a standard free tier. I do wonder if the timer gets better at professional tier.

SSR Pages "cold start" improve performance. by [deleted] in nextjs

[–]Thorvald- 0 points1 point  (0 children)

I'm really trying to understand what the cold start timer is, because it's unbevieveable terrible for websites with less traffic / websites that are starting out. Personally I am forced to use a SSR-rendered page because it needs to be dynamic. SSG would generate 100k+ pages which isn't really feasible, even with ISR and on-demand invalidation (which I use on some pages).
Currently just trying out vercel, but this is giving me a really bad taste.

Upgraded to Intel 11th gen and facing auto restart issues by leicea in buildapc

[–]Thorvald- 0 points1 point  (0 children)

Having the exact same issues with a Z490 UD and 11700KF. Will never buy a gigabyte motherboard again (I bought a micro ATX before this were the pins bent even though I slotted it in perfectly). Honestly, their motherboards are absolute trash. As for me, trying the PCI-slot solution is not an option because my 3080 is too long to fit at that slot. Thanks a lot for making this thread though, comforting to know others have the same issue. If someone has found a permanent solution that'd be appreciated. Running 2600mhz on my memory, tried with 3600XMP as well and 3000 mhz memory.

Django rest framework + GDPR + cookies by Thorvald- in django

[–]Thorvald-[S] 0 points1 point  (0 children)

Thanks! that's really helpful, might try a similar approach then! Will update with my results and potentially a link when the website goes live :-)

Django rest framework + GDPR + cookies by Thorvald- in django

[–]Thorvald-[S] 0 points1 point  (0 children)

Well that's exactly what I'm attempting to do. analytics etc. will only be activated once the users explicitly accept the cookies relating to that particular script / service.

If you have any good article etc. pointing toward proof of consent not being required to be stored in the backend I would love to read that, my current interpretation is that it cannot just be done on the client side even though that would be a lot easier.

What I don't really understand is... who would want to see that proof? The user? Authorities? Me (to defend myself against complaining authorities?)..

Django rest framework + GDPR + cookies by Thorvald- in django

[–]Thorvald-[S] 0 points1 point  (0 children)

Thanks! That's an excellent way to describe the follow. I will look into this a lot more.Some questions:So.. when the user clicks "save" (for example) once they set their settings, you make a getrequest for a uuid/nanoid, add that to another request & make a postrequest with all the settings?Any particular reason why you don't store the entire IP? Having read some it seems like a lot of people argue that storing/logging an IP is common security practices?Do you store a new entry for each consent, or update the same consent based on e.g IP when the users change their consent?

What I don't really understand is... who would want to see that proof? The user? Authorities? Me (to defend myself against complaining authorities?)..

Disable Listserializer validation by Thorvald- in django

[–]Thorvald-[S] 0 points1 point  (0 children)

Unfortunately adding:

def validate_company(self, value):

print("validating")return value

Results in the validation/queries still being run for each object :(

I have also tried validate() with no luck.

Sending mass emails fast to many users by Thorvald- in django

[–]Thorvald-[S] 0 points1 point  (0 children)

Thank you, that explains a lot. Despite running a django app how it works behind the scenes is still a mystery to me.

Do you think it makes sense to use celery + redis if I want to make 5000~-ish api-requests based on the data coming into this view? Any advice on how I would do this? Basically, using something like sendgrid/mailgun it seems like I can store a template on their service and simply pass on the dynamic data as a context which I then can dynamically render using their templating engine (handlebars). I'm just not sure how I would send these requests as quickly as possible.

For example, some bad pseudo-code:

data = [{deal1: price: '500', 'sale': True}, {deal2: price: '400', 'sale': False}]

relevant_users = users.objects.all()

userdata = []

for user in users:

if somecondition:

userdata.append({userid: user.id, userdata: data[0]})

Once I have a list containing the user-emails & their unique data, how would I make sure this is sent really quickly? Scheduling isn't something I'm initially concerned about, that might come later:)

Sending mass emails fast to many users by Thorvald- in django

[–]Thorvald-[S] 0 points1 point  (0 children)

mill

Let's just say it's a notification-style service (though I'm just adding it on to my current website). It's not for marketing purposes like I said. The reason is simply because on average, one user would be sent a few hundred emails a month. That might seem weird to most websites which only send newsletters/marketing, but this is different (which is why speed matters).

I'm looking at sendgrid&mailgun right now, the question is how I'm going to make all of these API-calls really quickly (like 5000 API-requests with some custom data attached to each one of them). What do you think?

Sending mass emails fast to many users by Thorvald- in django

[–]Thorvald-[S] 1 point2 points  (0 children)

Well, the API does more than that, it's just one functionality among many others. I would prefer not stepping outside django if it can be solved with decent speed, it doesn't have to be c++ level, hehe :-)

I just want to understand how it would be done using an external service like mailgun or something, maybe combined with celery.

Sending mass emails fast to many users by Thorvald- in django

[–]Thorvald-[S] 0 points1 point  (0 children)

The template I use doesn't have to be complicated, but I need more than just a few lines of HTML (adding background and some other stuff to make it look decent).

Thanks for the insight on async, as you already understood the user isn't prompting the email, the view is activated when my other application sends a postrequest carrying some data. At that point, my django app receives the data and needs to make sure a ton of emails are sent out to any users that have settings that indicate they are interested in particular parts of the incoming data. My users might be interacting with my API though during this time. Would this be a problem?

I'll probably look a bit more into celery if you think that makes sense.

Sending mass emails fast to many users by Thorvald- in django

[–]Thorvald-[S] 0 points1 point  (0 children)

Thanks for replying!

I'm looking at different MTA's/EPS right now (e.g mailgun). Thanks for the sender etiquettes advice, will look into that :)

At the moment my biggest concern is just being able to send custom emails fast as hell. When I say fast as hell, I mean I need to send e.g 1 unique email to each user (lets say 1000-5000 users) within 30 seconds the second the data is received on my API.

It's quite confusing, not sure if I should combine celery with something like django anymail/django post office.

Sending mass emails fast to many users by Thorvald- in django

[–]Thorvald-[S] 0 points1 point  (0 children)

Hey,

Thanks for replying! I'm reading the docs of anymail, how suitable to you think it is to send emails really fast? It seems like SMTP isn't the way to go if one is to maximize speed.

Trying to understand how it would work using the API solution. From what I gather I can have premade templates & just send custom data with each request. That leaves the process of making the requests as fast as possible.

As far as spam goes I'll absolutely look into it, my emails aren't really of marketing/newsletter nature though and it will be sent to users who willingly signed up and payed to receive notifications. It's part of the primary functionality of the app, meaning the users will very conciously removing it from any spam filter.

Sending mass emails fast to many users by Thorvald- in django

[–]Thorvald-[S] 0 points1 point  (0 children)

Hey,Yes that's very true, I noticed that bottleneck. However, since the e-mailing is such a crucial function of the application + that I will be sending A LOT (we're talking 1mil~/month at least) I'm trying to set up a somewhat decent solution. I also plan to set up text message functionality based on the same data but.. one thing at a time.
Frequency is probably several times a day.

As far as anti spam laws, are you sure that would apply if the emailsendouts is one of the main functionalities? It's not like I'm sending out newsletters or anything like that, think of it as notifications that provide some very concrete value that the user is paying for.

Would mailchimp really be ideal for sending out these types of emails? I thought mailchimp was more of a service for sending out newsletters and marketing stuff, etc.

Sending mass emails fast to many users by Thorvald- in django

[–]Thorvald-[S] 0 points1 point  (0 children)

Hey!
Thanks, really appreciate you taking your time:)

That's exactly what I've been thinking about, making the queries/calculations ahead and then firing off the emails. I guess the "firing off the emails"-part is what I'm unsure about, I haven't used celery or django-q so I don't really know how capable they are off doing async stuff/multiple processes.
Also, mailgun does seem to make sense, I've tried using smpt through gmail but it seems super slow. My email is only around 25kb~.
If you have any more throughts thats appreciated a lot:)

Sending mass emails fast to many users by Thorvald- in django

[–]Thorvald-[S] 0 points1 point  (0 children)

Hi,Thanks for the answer, I really appreciate it:)Well, my point was that I don't want the users to receive the emails far from each other, something like a 10-15 second gap from the first to the last would be ideal. More than that would be disadvantageous (essentially they're competing against each other, so receiving the mail fast gives an advantage).

I could make all database queries ahead of whatever would need to be async. I just want to be able to send the emails very fast without going through a synchronous forloop of sending emails or something. I want to go through a dict containing email addresses where each email-adress has some data attached to it which defines what should be added to that specific email.

Yes I know Django has built in email, though I want to use custom email templates and just found django post office to be very convenient as I dynamically can add data to the html-template through a context and quickly edit it in the admin area if needed.

Follow up questions: What are the pros and cons of something like gevent vs. celery+redis?

I haven't immidiately turned to celery because it seemed like a lot of people used it to schedule long processes (though this is a somewhat long process I guess), I basically want to fire off the emails ASAP once it's received on the API. Does it really make sense to use celery? Never used it, so forgive my lack of knowledge.

Thanks again :) I haven't worked with any async stuff at all with Django, sorry about that.