Settings and activity
22 results found
-
1,852 votes
An error occurred while saving the comment 
Pieman3K
supported this idea
·
-
127 votesPieman3K
supported this idea
·
-
16,627 votes
An error occurred while saving the comment Pieman3K
commented
...How many times do I have to come back here and remind that taking the creator out of the creative process will only increase the hollow shell your overlords are so eager to shoehorn?
Like... let's think for a second, who either you or Amazon are selling this to if you're taking the vendor and therefore the buyer out of the equation? Ever thought about that?
Also good luck with brand accounts, I fully expect them to lawyer up if their image/mascot gets (and it will) misused in such a woefully misguided endeavor.
Pieman3K
supported this idea
·
-
62 votesPieman3K
supported this idea
·
-
3,042 votesPieman3K
supported this idea
·
An error occurred while saving the comment Pieman3K
commented
Need I also remind that the previous predictive tools you folks have attempted to implement have also been woefully inefficient as it gauged a moment that could very much be out of context due to mere chat having a spike in activity as a sole metric, often leading to moments that were far from intended to be captured as "mementos" of some sort, while at the same time driving away the community aspect of said features (in cases such as Moments, also fomenting more FOMO).
Now, imagine, if you will, getting autoclipped during a hate raid just because it uses a similar measuring... that would not be fun or let alone legal in terms of your own terms and conditions regarding harrassment, would it? :)
Let alone our collective disgust for the slop machine being used (I'm not even gonna call it misuse) for what it was intended for in the first place, an overbloated system that will inevitably siphon more resources than having human as staff would. Not even in the long run, but short term, at this point. coding is sloppy, insecure, and it was made precisely to siphon more money than you would imagine while causing the damage mentioned on the post above, on top of the multitude of copyright liabilities already in place. The fact that there has been hiring to correct said sloppiness from other companies scream as much.
So I'll call it for what it is. Another unforced error, fueled by another unforced error.
Drop the automation. Seriously.
-
7,980 votesPieman3K
supported this idea
·
An error occurred while saving the comment Pieman3K
commented
Answer me this... What is the point of an art category if you take the artist out of the equation?
The additional irony being, LLM assets are more often (not to say always) obtained through plagiarism, and while it may sound cheap on paper to obtain such assets, the server processing costs behind it can far outweigh the price of a commission from an... you guessed it, an artist! Which there are many at your disposal if instead of this option you chose to do a bit of legwork!
That's the third time in less than 6 months.
Do better.
-
436 votesPieman3K
supported this idea
·
-
5,284 votes
An error occurred while saving the comment Pieman3K
commented
An amateur designer would soon learn that critical function elements require to be a top priority AND the first to load, not a highlight to be broken by bad formatting. The second sample is even worse, separating elements on both sides while keeping a larger, unnecessary void instead of a functional design.
And before you so much as consider moving the chatbox to the left side on a later update, keeping it on the right side ALSO is cognitively functional. Don't push it.
Once again it falls on the hands of third party development to clean up your mess.
Don't fix what isn't broken. Period.
Pieman3K
supported this idea
·
-
895 votesPieman3K
supported this idea
·
-
630 votesPieman3K
supported this idea
·
-
4,863 votes
An error occurred while saving the comment Pieman3K
commented
Are you folks REALLY going to cave in to the ADL's faceless decisions instead of consulting with your guilds or ambassadors without an inkling of inclination to check for motives?
You can't just sweep what happened in October 21st under the rug and remain reactive over point 4 of their public statement.
Otherwise what is even the point of having them in the first place if they're going to be thrown under the bus?
Kindly remove the ENTIRE document, not just the two contested points. This is dumb on SO many levels.
Pieman3K
supported this idea
·
-
6 votesPieman3K
supported this idea
·
-
637 votesPieman3K
supported this idea
·
-
2,142 votesPieman3K
supported this idea
·
-
334 votesPieman3K
supported this idea
·
-
2,648 votes
-
4,500 votesPieman3K
supported this idea
·
-
189 votesPieman3K
supported this idea
·
-
1,949 votesPieman3K
supported this idea
·
-
1,590 votesPieman3K
supported this idea
·
I'm not gonna sugarcoat it, I already detest it by principle as many others for many-a-good reasons, but as far as this month alone is concerned, I can only expect such "developments" to end up in more exploits being shared not with devbranches to be patched out but public often ending up in the wrong hands, except in an exponential manner, leading to more harassment campaigns.
You can thank the individual that has singlehandedly facilitated that back in `21 for setting up the groundwork for that ending up in four continuous months of nothing but strife, then went on to haze other support platforms in a similar fashion just for sport in the following years.
Knock it off.