How do you suppose your CP generator will be trained without using authentic CP images? Not only will that require revictimization but you’ll also be downloading CP to train the model.
we already have a lot of fabricated content like that using current photo editing technology (Photoshop) and it's not causing much legal nor moral issues
Just so others are aware, me and this guy have been 'friends' since 2015. He sent me a screenshot of this comment on Signal before he posted it. Its just his way to not address what I said.
The fact that this has never happened before except when literal incitement of violence was being carried out (google for screenshots) and not being stopped, shows there's no reason to worry this will happen to you.
Did Plandemic have literal incitement of violence? That was what OP was talking about. I see a typical Anti-Vac propaganda movie, but the Wikipedia page and news articles didn't seem to mention any calls to violence...
I have a pretty large codebase written in scala 2.12 or so (whatever the version was around late 2018). I'd like to migrate it to scala 3. Any ideas how hard it'll be?
Start with migrating to scala 2.13, scala 3 can run all non-macro 2.13 code that doesn't emit deprecation warnings and can consume most 2.13 libraries. The widely-used ones it can't will get updated.
This is like saying, airplanes are too complex. There are so many knobs and buttons. I'd rather just walk or ride a bike everywhere.
Scala is a very powerful, very expressive language. There are some features which you can just choose to leave out. If you do, you end up with a very clean, concise, and powerful language that makes you really productive.
I've literally had moments where I made my algorithm 5x faster just by adding 4 letters: '.par' in front of an operation. Instantly it got parallelized without my having to do anything, and the processing time got cut 5x.
Its more like saying: I need to cut some paper ( i need to program): Swiss army knifes (scala) are too complex, I just need a pair of pair of scissors (lisp / other languages).
You can also use Smidge without sending us any PII, but obviously segmentation will be limited.
Also in the next couple of weeks, with just a user id, you will be able to place a call directly from Zendesk (for example) without us knowing anything about the user.
Yep absolutely. You bucket users on your end and just pass through the user Id and the segment name. Then mirror the segment as call groups on our end e.g. segment='high value'
We don't show the user anything until you call them (so as to not interfere with drift/intercom etc). When you call them the current UI is like a mobile call UI.
EDIT: we are working on user initiated calling as we speak (it will show availability of support staff/CSRs)
This is really cool. I wish there was a way to have non-english speaking journalists as interviewers, I'd totally set them loose on many of my family members.
Edit: Your homepage doesn't explain what you do well enough, IMO. When I visited it I wasn't sure what you do - but reading your post explained it to me (I think) - you hire journalists to interview your loved ones and turn it into a podcast. I didn't get that from your homepage.
Thank you very much for that feedback and you are correct: We set loved ones up for interviews with professionals and turn those interviews into podcast episodes. We can absolutely make this critical point much more clear than it is presently on the landing page.
We are now supporting Artifacts in Spanish, French, English, and just added Korean. Other languages on the way. In what languages would you like your family members interviewed?
Yes! We are saving the email addresses of people who request specific languages so we can alert them as each new language becomes available on our platform—if you'd like us to let you know when Brazilian Portuguese is an option, please send an email to contact at heyartifact dot com and mention Brazilian Portuguese!
I disagree, you can definitely improve the stuff you built in retool. As a dev it's saved me a lot of time from having to build non user-facing dashboards, etc that would otherwise take up a lot of time. Instead I was able to spend that time on the core features.