Search
232 results for “hrefna”
-
Let's not mince words.
It is the creator saying outright that they were trying to solve their problem of being unable to get people to work #ForExposure at a mass scale.
This is why I'm describing what they are doing with language as a "shell game."
#Haidra _cannot_ be ethically neutral middleware when the author's stated purpose in building and running the system is to make it so that people can avoid needing to pay artists for their work.
There are other problems, but start there.
6/
-
So here we have an Actual Problem™.
Let's break it down.
The creator could not find someone who would do a significant amount of work for free so their solution was to reach for a tool that was trained on those same artists information without their knowledge or consent. Now wants to enable that theft for everyone. #haidra
That's the goal. That's what this is aiming for. Remember that when later the author talks about how the ethical questions are answered.
Just… let that sit.
5/
-
So here we have an Actual Problem™.
Let's break it down.
The creator could not find someone who would do a significant amount of work for free so their solution was to reach for a tool that was trained on those same artists information without their knowledge or consent. Now wants to enable that theft for everyone. #haidra
That's the goal. That's what this is aiming for. Remember that when later the author talks about how the ethical questions are answered.
Just… let that sit.
5/
-
So here we have an Actual Problem™.
Let's break it down.
The creator could not find someone who would do a significant amount of work for free so their solution was to reach for a tool that was trained on those same artists information without their knowledge or consent. Now wants to enable that theft for everyone. #haidra
That's the goal. That's what this is aiming for. Remember that when later the author talks about how the ethical questions are answered.
Just… let that sit.
5/
-
So here we have an Actual Problem™.
Let's break it down.
The creator could not find someone who would do a significant amount of work for free so their solution was to reach for a tool that was trained on those same artists information without their knowledge or consent. Now wants to enable that theft for everyone. #haidra
That's the goal. That's what this is aiming for. Remember that when later the author talks about how the ethical questions are answered.
Just… let that sit.
5/
-
So here we have an Actual Problem™.
Let's break it down.
The creator could not find someone who would do a significant amount of work for free so their solution was to reach for a tool that was trained on those same artists information without their knowledge or consent. Now wants to enable that theft for everyone. #haidra
That's the goal. That's what this is aiming for. Remember that when later the author talks about how the ethical questions are answered.
Just… let that sit.
5/
-
Specifically, I am of the view that if they are accepted then #nivenly will become complicit in the behavior of #AiHordeDotNet.
I _don't_ think that the Nivenly board sees it that way, but as an engineer _I_ would. I could draw a line between "us" and "them" if .net was run by someone who was not a lead maintainer on #Haidra
This would not be as big of deal, except that I feel like there's a bit of a shell game going on when it comes to responsibility, and that's part of my core objection
4/
-
Specifically, I am of the view that if they are accepted then #nivenly will become complicit in the behavior of #AiHordeDotNet.
I _don't_ think that the Nivenly board sees it that way, but as an engineer _I_ would. I could draw a line between "us" and "them" if .net was run by someone who was not a lead maintainer on #Haidra
This would not be as big of deal, except that I feel like there's a bit of a shell game going on when it comes to responsibility, and that's part of my core objection
4/
-
Specifically, I am of the view that if they are accepted then #nivenly will become complicit in the behavior of #AiHordeDotNet.
I _don't_ think that the Nivenly board sees it that way, but as an engineer _I_ would. I could draw a line between "us" and "them" if .net was run by someone who was not a lead maintainer on #Haidra
This would not be as big of deal, except that I feel like there's a bit of a shell game going on when it comes to responsibility, and that's part of my core objection
4/
-
Specifically, I am of the view that if they are accepted then #nivenly will become complicit in the behavior of #AiHordeDotNet.
I _don't_ think that the Nivenly board sees it that way, but as an engineer _I_ would. I could draw a line between "us" and "them" if .net was run by someone who was not a lead maintainer on #Haidra
This would not be as big of deal, except that I feel like there's a bit of a shell game going on when it comes to responsibility, and that's part of my core objection
4/
-
Specifically, I am of the view that if they are accepted then #nivenly will become complicit in the behavior of #AiHordeDotNet.
I _don't_ think that the Nivenly board sees it that way, but as an engineer _I_ would. I could draw a line between "us" and "them" if .net was run by someone who was not a lead maintainer on #Haidra
This would not be as big of deal, except that I feel like there's a bit of a shell game going on when it comes to responsibility, and that's part of my core objection
4/
-
In our introduction here we establish the terms.
Basically what I see is that there are three separate concepts that need to be discussed:
Haidra is the parent organization looking to join nivenly.
#AiHorde is the actual software
#AiHordeDotNet is the maintainer's implementation service and the main cluster that the #AiHorde software ties into
For reasons I'll get into later I do not believe that this delineation is bad, but I also think we should weigh the behavior and activity of .net /3
-
Being neurodivergent has _nothing_ to do with it. At all.
The maintainer responded poorly to multiple people who they have not apologized to, but rather made a blanket post in a different medium. This evades responsibility.
This makes the apology feel less than genuine
From a learning perspective I could treat this as a calling in moment and a matter of coaching, but in whether to select a project for #Nivenly—and their maintainers for the senate—I would like to see that learned _first_
2/
-
I'm going to do some reflecting here on #haidra
https://hachyderm.io/@nivenly/110890692128244044
Because I have tried to write a perspective more appropriate for the private discussion and I keep failing because I get angry, so I am going to start here.
First, as a pet peeve, let me say:
I am autistic. I have ADHD. I have NVLD.
I strongly dislike when people say things like "As a neurodivergent, I will readily admit that I do not react well to such comments and for that I’d like to apologize and try again."
1/
-
I'm going to do some reflecting here on #haidra
https://hachyderm.io/@nivenly/110890692128244044
Because I have tried to write a perspective more appropriate for the private discussion and I keep failing because I get angry, so I am going to start here.
First, as a pet peeve, let me say:
I am autistic. I have ADHD. I have NVLD.
I strongly dislike when people say things like "As a neurodivergent, I will readily admit that I do not react well to such comments and for that I’d like to apologize and try again."
1/
-
I'm going to do some reflecting here on #haidra
https://hachyderm.io/@nivenly/110890692128244044
Because I have tried to write a perspective more appropriate for the private discussion and I keep failing because I get angry, so I am going to start here.
First, as a pet peeve, let me say:
I am autistic. I have ADHD. I have NVLD.
I strongly dislike when people say things like "As a neurodivergent, I will readily admit that I do not react well to such comments and for that I’d like to apologize and try again."
1/
-
If your fundamental claim is: "We just built an API, it is up to others how they use it!"
Then you have:
* Deliberate and direct integrations with a set of highly problematic systems.
* A lot of your advertised use cases are with those problematic systems.
* The main deployment of your API is for said systems.
* Your main use of your system on social media accounts is of said systems.
It is hard to simply wave away your support of the problematic system.
-
#RegretRate for various surgeries:
* Knee surgery: 22% total regret, 2.9% even without complications http://doi.org/10.1186/s12891-020-3041-y
* Back surgery: 21% in older adults http://doi.org/10.1097/BRS.0000000000004287
* Regret of having children: varies by study, but usually in the 10-20% range http://doi.org/10.1371/journal.pone.0254163
* Breast reconstruction after a mastectomy: 19.5% moderate to strong regret http://doi.org/10.1080/14768320601124899
* #GenderAffirmationSurgery: < 1% http://doi.org/10.1097/GOX.0000000000003477
-
Gahhhhhh, once again, for those in the back:
#AtWill does not mean "they can fire you for any or no reason." It means that they can fire you for a lot of things, but firing you for engaging in a protected activity, being in a protected class, etc is still illegal.
#RightToWork has to do with #union security clauses. Nothing else. It doesn't affect your rights beyond that item. At all.
Please stop conceding defeat and encouraging others to concede before even starting.
-
What if instead of opting _out_ of content and #federation (fediblock), instances had to opt _in_ to content and federation?
What I mean by that:
* Instead of "things appear in the federated timeline by default" it is "only servers that have been reviewed show up in the fedderated timeline."
* Instead of "follow requests require review if coming from a silenced server" it would be "non-mutual follow requests require review unless coming from a reviewed server."
-
IMO some things that would help tremendously and that would be good to prioritize, ways:
* Of having a persistent identifier that is decoupled from your server. Whether this looks like the current #VC and #DID proposals is less important than that the decoupling takes place.
* Of sharing and pooling moderation, load, storage, privacy, and security resources (see my previous discussion of #APAF/#ActivityPubApplicationFirewall or #APRL).
-
One thing I definitely do not get about #TechLayoffs in general and #GoogleLayoffs in specific is that presumably you have those people because you think you can deliver some reasonable value proposition with them.
With fewer people you will deliver less. Yes?
So when you cut people in a broad spectrum like this, a month into Q1, what exactly do you expect to happen?
Between the hit to moral, the severance and legal costs, and the slowed productivity just how expensive is this?
-
Are #unions a perfect tool? Frak no. Any given union or collection of unions is going to have a long history of shitty decisions and problematic behaviors if they have existed for more than a few years. Unions are comprised of people are not immune to any of the things that make people people.
But I would rather stand with my fellow workers in an imperfect alliance than get fraked over by unchecked corporate greed again and again without recourse and without any resistance.
-
After watching execs talk about the #GoogleLayoffs, all I can really say is this:
If you are in tech you need a strong union.
If you are in tech you need a strong union.
If you are in tech you need a strong #union.
After seeing what happened at #twitter, after seeing yet another round of nonsense layoffs across so many good people at so many companies, we need unions and we need them yesterday.
If you are in a union already, build strength. We are going to need it.
-
hreflang ist der am häufigsten falsch implementierte Tag im technischen SEO. 🌍Die drei Klassiker: fehlende Rückverweise (x verweist auf y, aber y nicht auf x), falsche Sprachcodes (de-DE statt de) und Canonicals, die auf eine andere Sprachversion zeigen.
Google ignoriert hreflang komplett, sobald die Signale inkonsistent sind. Stillschweigend. Kein Hinweis in der Search Console, kein Warnsignal.
Check: Crawler drauf, paarweise Validierung, fertig.
-
Hreflang теги для SEO
Теги hreflang — это атрибуты в HTML, которые помечают язык и региональную принадлежность веб-страниц. Они важны для того, чтобы поисковики, например Google, могли определять, какую именно версию страницы показывать пользователям в зависимости от их местоположения и языковых настроек. Это особенно критично для сайтов, которые доступны на нескольких языках и предназначены для разных регионов.
-
@MonicaAzzolini that Hoefnagel image is divine. 😍 #enthist
-
Google confirme (à nouveau) que les balises Hreflang sont des signaux (comme les canonical tag) et non une directive (comme par exemple la meta robots).
Avoir le même contenu sur un site international ne va clairement pas vous aider à mieux vous indexer sur la bonne version régionale du moteur.
