[1] - https://gitgud.io/AUTOMATIC1111/stable-diffusion-webui/-/blo...
Looking through that file, I can't think of a single charitable interpretation for that categorization.
[1] https://www.reddit.com/r/StableDiffusion/comments/xl8bj2/aut...
Do you think I'm doing that because I hate a group of people that are called a derogatory word that begins with r?
Sometimes we infer things from a combination of evidence.
People in the Jim Crow era were convicted without evidence, or had exonerating evidence hidden by racist law enforcement and prosecutors. It’s hardly the same.
Circumstantial evidence becomes compelling only when there's a lot of it, all in one direction, without exonerating or at least contradictory evidence of some kind.
If you have white robes with pointy hats, a noose, and a Confederate flag in your closet, I'm very comfortable assuming certain facts about you. If you can come up with a good explanation - perhaps you're an actor in a play about the civil rights era - I'm prepared to shift that conclusion, but "nuh uh, this doesn't prove anything!" isn't a compelling response to it.
But if I found out that a black person had a picture of a white person on his computer under the "C" drive, I wouldn't assume that he named the drive "C" for cracker, and wouldn't expect him to prove the "real reason" his drive was named "C"
Agreed!
If, however, all the other drives were named "Photos" and "Recipes" and other descriptive terms, leaving only the C drive as a letter, that'd be interesting. Even more interesting if it's a bunch of photos of white people, and nothing much else on said C drive. If that same person had previously criticized civil rights issues, and was cagey about why they have the one oddly-named drive (https://www.reddit.com/r/StableDiffusion/comments/xl8bj2/com...), and had a history of putting out racially-focused mods for a game, we might begin to get outright suspicious.
This is what circumstantial evidence is all about; more than one data point leading to a reasonable conclusion. You seem to want to redefine it to a single data point, which giving it's been explained several times now, I have to assume (circumstantial again!) is playing dumb intentionally.
Civil vs. Criminal cases have different levels of guilt. Further, this isn't either, but a private company and its TOS. It's perfectly reasonable to hold different standards for different situations. I would hope that we hold a higher standard for criminal activity. What GitHub did was very much use the powers conservatives have fought long and hard to maintain.
People seem unable to do this. They want to see all of these examples as unrelated things that coincidentally can all be considered racist by wokies. To me, it's a case of walking and swimming and talking like a duck.
Mati Klarwein
Quite frankly I'm having trouble believing you picked one randomly and it happened to be the only one miscategorized.
You could argue maybe that using the letter "n" could be seen as racist. It's a US centric view however, in other places n would be fine (n for negro in Spanish for example)
For all I know automatic might be super racist, I'm just playing devils advocate, and I like to assume the best of in people.
Regarding the content: That would still be a questionable classification, but even more so for someone like "RETNA (Marquis Lewis)" who rarely ever seems to depict people.
All in all it’s very sketchy, though one could probably construct ways it’s not racist, and it might not even be racist, though I doubt it.
I think the most likely scenario is that automatic's trying to group that style, which is fair and the purpose of those categories after all, and him coming from 4chan is no stranger to the n word, so that's what came to his mind.
Even if I think that's the most likely situation, I give him the benefit of the doubt, that's what I meant.
My first assumption on encountering a table field with a standalone "n" would be that it's an abbreviation of "no". So I'm surprised people are assuming so strongly here that this is instead code for a racist word. This is quite a harsh accusation, given the lack of evidence.
It will be quite embarrassing all round if this just turns out to be a run-of-the-mill copyright strike, or similar.
If, say, the guy had made mods smirking at the George Floyd protests, had made skin-color mods, and had also said "no comment" when asked what the 'n' and 'c' tags represented, would you still go with your first assumption?
That he's clearly more than a little racist isn't enough for me to defend nuking the guy's account without warning or explanation. But it is enough to make me think twice about blindly downloading and running the guy's code (which also downloads a lot of stuff/self-updates).
Who knows what other norms of basic decency this anonymous person from 4chan would violate.
So I loaded up A111, selected the 'n' category, and ran a few pictures using random artists from said category.
The results were all black. The category itself is actually useful to me, now that I know it exists — I use the AI to generate illustrations for my fanfiction, and getting non-white, non-asian outputs is difficult at best — but labelling it "n" is, uh, suspicious.
In combination with everything else, I don't think there's really any doubts about his thought process here. :(
* Bill Jacklin
* Hiroshi Sugomoto
* Josef Albers
* David Teniers the Younger
None of them are black.
Edit: As eyko pointed out below, these are not in the 'n' category. So I searched for people in that category, and all the ones I checked turned out to have been black (other than Mati Klarwein).
Howardena Pindell,0.7686921,n Mati Klarwein,0.7066092,n Barkley L. Hendricks,0.69986427,n Carrie Mae Weems,0.6645416,n Barkley Hendricks,0.6883637,n Yinka Shonibare,0.68256056,n Zanele Muholi,0.58554715,n Kehinde Wiley,0.66218376,n RETNA (Marquis Lewis),0.47963,n Wangechi Mutu,0.6394607,n Kadir Nelson,0.5669006,n Amadou Opa Bathily,0.5536976,n Juliana Huxtable,0.5364195,n Chinwe Chukwuogo-Roy,0.49445248,n Teophilus Tetteh,0.46064255,n Bruce Onobrakpeya,0.42588046,n
If that that's the ban reason, it's pretty Orwellian. There was a lot of severe property destruction (e.g. arson) during those protests, some of which was indisputably committed by people aligned with the protests. They were complicated events, with peaceful and violent parts. They were only one or the other when seen through a blinkered political orthodoxy.
> * Free - Yes, totally free for any user or group*
Such claims are invariably false. Or, stated most generously, heavily misleading, because of limitations. And that’s even ignoring the common “it became popular and we realised what we were offering wasn’t sustainable so we’re charging or limiting sharply or shutting down” result.
> * Fast - One of the fastest git hosting services*
Holistically, I’d say this isn’t even possible if you’re using GitLab. Significant parts of GitLab are very slow. And as for GitGud.io at present, well, that repository’s URL is consistently taking about ten seconds to send the first byte of the response, and even HEAD / takes more than five seconds to issue a 302 redirect to /users/sign_in.
> * Highly available - average uptime of 99.83% ¹*
Look, “highly available” is a vague term, but for this kind of service I’d expect it to mean three nines at the very least, probably four, and to mean an architecture and upgrade deployment mechanism significantly different from GitLab’s, where upgrades are disruptive.
Also, their actual status page is currently saying 91.16% for the last 24 hours (2h7m of downtime), which is already more than two months’ downtime budget even at 99.83%.
> * Reliable - We have never lost any data, unlike other services*
You also probably haven’t dealt with any of the scale-related issues that have caused data loss in said Other Services.
>>Free - Yes, totally free for any user or group
>Such claims are invariably false. Or, stated most generously, heavily misleading, because of limitations.
Can you explain your issue with this? GitGud.io has been operating for over 8 years with only free accounts and without any paid setup. Historically we've been supported by user donations, but I now also pay out of pocket, a relatively trivial amount since my main job is being a DevOps engineer for a CDN & cloud company, for server resources and upgrades for GitGud.io and we have plans to launch SaaS products that will completely offset any GitGud.io costs.
>>Fast - One of the fastest git hosting services
>Holistically, I’d say this isn’t even possible if you’re using GitLab. Significant parts of GitLab are very slow. And as for GitGud.io at present, well, that repository’s URL is consistently taking about ten seconds to send the first byte of the response, and even HEAD / takes more than five seconds to issue a 302 redirect to /users/sign_in.
GitGud.io has historically been fast. Currently we just finished an upgrade of the main node last week from an 8-core Epyc to a 64-core Epyc, plus 2-3x more available memory and we have not had enough traffic to adjust this. This event helped us tune GitLab better to our new resources. And yes, as someone who has been working with GitLab for over 8 years, I know exactly how slow and bloated it is, but you must also understand that GitLab.com itself spent years being constantly down or hardly loading in comparison. Different scales of "users", but GitGud.io still has 41,000 users and close to 15,000 repositories. You'd be hard pressed to find many other GitLab instances publicly usable that big. We could utilize Gitea or something lighter, but GitLab offers a lot of features and Gitea didn't exist when we started.
>> Highly available - average uptime of 99.83% ¹
>Look, “highly available” is a vague term, but for this kind of service I’d expect it to mean three nines at the very least, probably four, and to mean an architecture and upgrade deployment mechanism significantly different from GitLab’s, where upgrades are disruptive. >Also, their actual status page is currently saying 91.16% for the last 24 hours (2h7m of downtime), which is already more than two months’ downtime budget even at 99.83%.
Yes, cause currently we currently took the host node down 12 hours ago for a couple of hours in a planned hardware upgrade maintenance to install new 40g NICs, SSDs, etc. Overall the average is decent, and this line harkens back to the days when GitLab.com was down daily. We run on our own bare metal colo servers, not magically appearing cloud instances.
>> Reliable - We have never lost any data, unlike other services
>You also probably haven’t dealt with any of the scale-related issues that have caused data loss in said Other Services.
Their scale outs should have made it harder to lose data, not the other way around. We've also have ran a fairly large file/media sharing site in the form of Imgur with dozens of TBs of user uploaded media scaled across several servers, and we didn't lose data there. Fact is, we haven't lost any data and that's our track record so far over the past 8 years. I think that's worth of some note.
Either way, while the homepage claims are eyebrow raising for you, I don't see how this matters much for a service that is charging $0 for Git repo hosting. We make $0 for any user who decides to utilize us. If we wanted to charge for GitGud.io access and it's GitLab CI runner access, we could. There's nothing stopping us from doing that. But even if we disappeared tomorrow, the fact is that Git is naturally decentralized. The original creators and the clones exist somewhere.
We exist as an alternative to other services that suspend accounts on a whim and an easy solution for those that don't want to setup or pay for their own Git instance.
update: Gitgud repo created here : https://gitgud.io/AUTOMATIC1111/stable-diffusion-webui
(Gitgud seems to be really slow)
Further update : Account was suspended due to "TOS violations" : https://www.reddit.com/r/StableDiffusion/comments/103uwx1/au...