home.social

#slop — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #slop, aggregated by home.social.

fetched live
  1. [P] It's shameful to waste a brain on something as crass as racism. I'm having more and more trouble seeing hiverarchians as aught but slop people. It is a sloppy brain that contends with bigotries, that gets obsessed with pointless lines on a map. All lines of hiverarchian invention, an artifact of slopthink, where rumination is heresy, questions are dangerous, and consideration is a sin. Very 1984 of them.

    #psychology #actuallyautistic #slop #hiverarchiansaredumb #dumb #dumb

  2. [P] It's shameful to waste a brain on something as crass as racism. I'm having more and more trouble seeing hiverarchians as aught but slop people. It is a sloppy brain that contends with bigotries, that gets obsessed with pointless lines on a map. All lines of hiverarchian invention, an artifact of slopthink, where rumination is heresy, questions are dangerous, and consideration is a sin. Very 1984 of them.

    #psychology #actuallyautistic #slop #hiverarchiansaredumb #dumb #dumb

  3. [P] It's shameful to waste a brain on something as crass as racism. I'm having more and more trouble seeing hiverarchians as aught but slop people. It is a sloppy brain that contends with bigotries, that gets obsessed with pointless lines on a map. All lines of hiverarchian invention, an artifact of slopthink, where rumination is heresy, questions are dangerous, and consideration is a sin. Very 1984 of them.

    #psychology #actuallyautistic #slop #hiverarchiansaredumb #dumb #dumb

  4. [P] It's shameful to waste a brain on something as crass as racism. I'm having more and more trouble seeing hiverarchians as aught but slop people. It is a sloppy brain that contends with bigotries, that gets obsessed with pointless lines on a map. All lines of hiverarchian invention, an artifact of slopthink, where rumination is heresy, questions are dangerous, and consideration is a sin. Very 1984 of them.

    #psychology #actuallyautistic #slop #hiverarchiansaredumb #dumb #dumb

  5. [P] It's shameful to waste a brain on something as crass as racism. I'm having more and more trouble seeing hiverarchians as aught but slop people. It is a sloppy brain that contends with bigotries, that gets obsessed with pointless lines on a map. All lines of hiverarchian invention, an artifact of slopthink, where rumination is heresy, questions are dangerous, and consideration is a sin. Very 1984 of them.

    #psychology #actuallyautistic #slop #hiverarchiansaredumb #dumb #dumb

  6. @LuisCrespo

    Guessing here, but looks like #AI #slop to me.

    10 seconds long (a limit on a lot of the free generators) the cats don't seen to be visually tracking the ball (this is the big tell, anyone who has cats knows the laser focused tracking look) and the ball does something weird at the end.

    Can't say for sure though, but would love to know where the later got it from.

  7. @LuisCrespo

    Guessing here, but looks like #AI #slop to me.

    10 seconds long (a limit on a lot of the free generators) the cats don't seen to be visually tracking the ball (this is the big tell, anyone who has cats knows the laser focused tracking look) and the ball does something weird at the end.

    Can't say for sure though, but would love to know where the later got it from.

  8. @LuisCrespo

    Guessing here, but looks like #AI #slop to me.

    10 seconds long (a limit on a lot of the free generators) the cats don't seen to be visually tracking the ball (this is the big tell, anyone who has cats knows the laser focused tracking look) and the ball does something weird at the end.

    Can't say for sure though, but would love to know where the later got it from.

  9. @LuisCrespo

    Guessing here, but looks like #AI #slop to me.

    10 seconds long (a limit on a lot of the free generators) the cats don't seen to be visually tracking the ball (this is the big tell, anyone who has cats knows the laser focused tracking look) and the ball does something weird at the end.

    Can't say for sure though, but would love to know where the later got it from.

  10. @LuisCrespo

    Guessing here, but looks like #AI #slop to me.

    10 seconds long (a limit on a lot of the free generators) the cats don't seen to be visually tracking the ball (this is the big tell, anyone who has cats knows the laser focused tracking look) and the ball does something weird at the end.

    Can't say for sure though, but would love to know where the later got it from.

  11. tl;dr: If people spend their personal time to contribute to your open source project, the very least you should do is take the ~30 seconds to reply yourselves instead of having your chat bot spam them with slop.

    If you wanna vibe code, that's completely up to you. I'm not fond of it and usually rather underwhelmed by the result, but it's your choice.

    But please, if you're maintaining an open source project and someone contributes something, even if just reporting a bug, have the decency and reply yourselves instead of making your contributor read a massive chunk of LLM generated slop text, especially when they've put some effort into it!

    I found a bug in a library the other day that caused a crash when parsing certain files, looked into the code, looked into the specs of the file format, compared what the code was doing with what it should be doing and then wrote a top notch bug report containing everything needed to fix the bug (short of a patch to fix the bug myself), a developer's dream I'd say.

    A week later I got a clearly LLM generated piece of junk text as response, basically just repeating my report but slightly rephrased so it sounds like it figured it all out by itself, you probably know what I mean if you've ever talked to a chat bot.

    Call me hippie but for me open source software/projects are also about community and exchange and working on something together with like-minded people. By letting some LLM do not only the coding but also communication with contributors for you, from my perspective you're telling contributors that you don't give a shit about them and the time and effort they put into contributing to your project. I'm not even asking for much, a simple "thx, fixed" would be way more appreciated that that wall of slop.

    PS: The "fix" the LLM came up with was to remove a certain sanity check for that file format altogether, thus introducing a new bug. Not sure if I'm gonna point that out, I don't feel like using my human time for working towards your chat bot.

    #vibecoding #opensource #slop #ai #rant

  12. tl;dr: If people spend their personal time to contribute to your open source project, the very least you should do is take the ~30 seconds to reply yourselves instead of having your chat bot spam them with slop.

    If you wanna vibe code, that's completely up to you. I'm not fond of it and usually rather underwhelmed by the result, but it's your choice.

    But please, if you're maintaining an open source project and someone contributes something, even if just reporting a bug, have the decency and reply yourselves instead of making your contributor read a massive chunk of LLM generated slop text, especially when they've put some effort into it!

    I found a bug in a library the other day that caused a crash when parsing certain files, looked into the code, looked into the specs of the file format, compared what the code was doing with what it should be doing and then wrote a top notch bug report containing everything needed to fix the bug (short of a patch to fix the bug myself), a developer's dream I'd say.

    A week later I got a clearly LLM generated piece of junk text as response, basically just repeating my report but slightly rephrased so it sounds like it figured it all out by itself, you probably know what I mean if you've ever talked to a chat bot.

    Call me hippie but for me open source software/projects are also about community and exchange and working on something together with like-minded people. By letting some LLM do not only the coding but also communication with contributors for you, from my perspective you're telling contributors that you don't give a shit about them and the time and effort they put into contributing to your project. I'm not even asking for much, a simple "thx, fixed" would be way more appreciated that that wall of slop.

    PS: The "fix" the LLM came up with was to remove a certain sanity check for that file format altogether, thus introducing a new bug. Not sure if I'm gonna point that out, I don't feel like using my human time for working towards your chat bot.

    #vibecoding #opensource #slop #ai #rant

  13. tl;dr: If people spend their personal time to contribute to your open source project, the very least you should do is take the ~30 seconds to reply yourselves instead of having your chat bot spam them with slop.

    If you wanna vibe code, that's completely up to you. I'm not fond of it and usually rather underwhelmed by the result, but it's your choice.

    But please, if you're maintaining an open source project and someone contributes something, even if just reporting a bug, have the decency and reply yourselves instead of making your contributor read a massive chunk of LLM generated slop text, especially when they've put some effort into it!

    I found a bug in a library the other day that caused a crash when parsing certain files, looked into the code, looked into the specs of the file format, compared what the code was doing with what it should be doing and then wrote a top notch bug report containing everything needed to fix the bug (short of a patch to fix the bug myself), a developer's dream I'd say.

    A week later I got a clearly LLM generated piece of junk text as response, basically just repeating my report but slightly rephrased so it sounds like it figured it all out by itself, you probably know what I mean if you've ever talked to a chat bot.

    Call me hippie but for me open source software/projects are also about community and exchange and working on something together with like-minded people. By letting some LLM do not only the coding but also communication with contributors for you, from my perspective you're telling contributors that you don't give a shit about them and the time and effort they put into contributing to your project. I'm not even asking for much, a simple "thx, fixed" would be way more appreciated that that wall of slop.

    PS: The "fix" the LLM came up with was to remove a certain sanity check for that file format altogether, thus introducing a new bug. Not sure if I'm gonna point that out, I don't feel like using my human time for working towards your chat bot.

  14. tl;dr: If people spend their personal time to contribute to your open source project, the very least you should do is take the ~30 seconds to reply yourselves instead of having your chat bot spam them with slop.

    If you wanna vibe code, that's completely up to you. I'm not fond of it and usually rather underwhelmed by the result, but it's your choice.

    But please, if you're maintaining an open source project and someone contributes something, even if just reporting a bug, have the decency and reply yourselves instead of making your contributor read a massive chunk of LLM generated slop text, especially when they've put some effort into it!

    I found a bug in a library the other day that caused a crash when parsing certain files, looked into the code, looked into the specs of the file format, compared what the code was doing with what it should be doing and then wrote a top notch bug report containing everything needed to fix the bug (short of a patch to fix the bug myself), a developer's dream I'd say.

    A week later I got a clearly LLM generated piece of junk text as response, basically just repeating my report but slightly rephrased so it sounds like it figured it all out by itself, you probably know what I mean if you've ever talked to a chat bot.

    Call me hippie but for me open source software/projects are also about community and exchange and working on something together with like-minded people. By letting some LLM do not only the coding but also communication with contributors for you, from my perspective you're telling contributors that you don't give a shit about them and the time and effort they put into contributing to your project. I'm not even asking for much, a simple "thx, fixed" would be way more appreciated that that wall of slop.

    PS: The "fix" the LLM came up with was to remove a certain sanity check for that file format altogether, thus introducing a new bug. Not sure if I'm gonna point that out, I don't feel like using my human time for working towards your chat bot.

    #vibecoding #opensource #slop #ai #rant

  15. tl;dr: If people spend their personal time to contribute to your open source project, the very least you should do is take the ~30 seconds to reply yourselves instead of having your chat bot spam them with slop.

    If you wanna vibe code, that's completely up to you. I'm not fond of it and usually rather underwhelmed by the result, but it's your choice.

    But please, if you're maintaining an open source project and someone contributes something, even if just reporting a bug, have the decency and reply yourselves instead of making your contributor read a massive chunk of LLM generated slop text, especially when they've put some effort into it!

    I found a bug in a library the other day that caused a crash when parsing certain files, looked into the code, looked into the specs of the file format, compared what the code was doing with what it should be doing and then wrote a top notch bug report containing everything needed to fix the bug (short of a patch to fix the bug myself), a developer's dream I'd say.

    A week later I got a clearly LLM generated piece of junk text as response, basically just repeating my report but slightly rephrased so it sounds like it figured it all out by itself, you probably know what I mean if you've ever talked to a chat bot.

    Call me hippie but for me open source software/projects are also about community and exchange and working on something together with like-minded people. By letting some LLM do not only the coding but also communication with contributors for you, from my perspective you're telling contributors that you don't give a shit about them and the time and effort they put into contributing to your project. I'm not even asking for much, a simple "thx, fixed" would be way more appreciated that that wall of slop.

    PS: The "fix" the LLM came up with was to remove a certain sanity check for that file format altogether, thus introducing a new bug. Not sure if I'm gonna point that out, I don't feel like using my human time for working towards your chat bot.

    #vibecoding #opensource #slop #ai #rant

  16. *I just generated a morale patch for a militant Ukrainian scuba unit that detonates undersea pipelines #slop

    *Looks great, eh? So authentic, hardly sloppy at all! Could you wear that design-fiction in modern Russia without getting instantly arrested? Probably not!

  17. *I just generated a morale patch for a militant Ukrainian scuba unit that detonates undersea pipelines #slop

    *Looks great, eh? So authentic, hardly sloppy at all! Could you wear that design-fiction in modern Russia without getting instantly arrested? Probably not!

  18. *I just generated a morale patch for a militant Ukrainian scuba unit that detonates undersea pipelines #slop

    *Looks great, eh? So authentic, hardly sloppy at all! Could you wear that design-fiction in modern Russia without getting instantly arrested? Probably not!

  19. *I just generated a morale patch for a militant Ukrainian scuba unit that detonates undersea pipelines #slop

    *Looks great, eh? So authentic, hardly sloppy at all! Could you wear that design-fiction in modern Russia without getting instantly arrested? Probably not!

  20. me as i'm writing in english, but since i'm in Germany and will use German book distributors I'm along for the ride into (apparently) involuntary AI slop hell:

    mastoart.social/@thatwriterell

    #selfpublishing in Germany seems to be a bit on fire... 🔥 send help 💀

    #selfpublishing #bookstodon #buchstodon #ki #wegmitki #kifrei #slop #aislop #writing #reading #schreiben

  21. me as i'm writing in english, but since i'm in Germany and will use German book distributors I'm along for the ride into (apparently) involuntary AI slop hell:

    mastoart.social/@thatwriterell

    #selfpublishing in Germany seems to be a bit on fire... 🔥 send help 💀

    #selfpublishing #bookstodon #buchstodon #ki #wegmitki #kifrei #slop #aislop #writing #reading #schreiben

  22. me as i'm writing in english, but since i'm in Germany and will use German book distributors I'm along for the ride into (apparently) involuntary AI slop hell:

    mastoart.social/@thatwriterell

    #selfpublishing in Germany seems to be a bit on fire... 🔥 send help 💀

    #selfpublishing #bookstodon #buchstodon #ki #wegmitki #kifrei #slop #aislop #writing #reading #schreiben

  23. me as i'm writing in english, but since i'm in Germany and will use German book distributors I'm along for the ride into (apparently) involuntary AI slop hell:

    mastoart.social/@thatwriterell

    #selfpublishing in Germany seems to be a bit on fire... 🔥 send help 💀

    #selfpublishing #bookstodon #buchstodon #ki #wegmitki #kifrei #slop #aislop #writing #reading #schreiben

  24. me as i'm writing in english, but since i'm in Germany and will use German book distributors I'm along for the ride into (apparently) involuntary AI slop hell:

    mastoart.social/@thatwriterell

    #selfpublishing in Germany seems to be a bit on fire... 🔥 send help 💀

    #selfpublishing #bookstodon #buchstodon #ki #wegmitki #kifrei #slop #aislop #writing #reading #schreiben

  25. @BeeDoubleYou @v_d_richards Und #Epubli schrieb mir per Email sie überlegen das auch zu machen, mit scheinbar Manuskripte alle in US-KIs werfen, und sie empfehlen Leuten die das nicht mögen wegzuwechseln. So verstand ich das zumindest.

    Fragt alle gerne nach: epubli.com/kontakt Mehr Fragen und ggf. Bedenken dazu kann wohl nicht schaden.

    Und korrigiert mich gerne falls ich falsch liege, ich würd gerne irren...

    #wegmitki
    #kifrei
    #ki
    #slop
    #selfpublishing
    #buch
    #buchstodon
    #lesen
    #schreiben

  26. @BeeDoubleYou @v_d_richards Und #Epubli schrieb mir per Email sie überlegen das auch zu machen, mit scheinbar Manuskripte alle in US-KIs werfen, und sie empfehlen Leuten die das nicht mögen wegzuwechseln. So verstand ich das zumindest.

    Fragt alle gerne nach: epubli.com/kontakt Mehr Fragen und ggf. Bedenken dazu kann wohl nicht schaden.

    Und korrigiert mich gerne falls ich falsch liege, ich würd gerne irren...

    #wegmitki
    #kifrei
    #ki
    #slop
    #selfpublishing
    #buch
    #buchstodon
    #lesen
    #schreiben

  27. @BeeDoubleYou @v_d_richards Und #Epubli schrieb mir per Email sie überlegen das auch zu machen, mit scheinbar Manuskripte alle in US-KIs werfen, und sie empfehlen Leuten die das nicht mögen wegzuwechseln. So verstand ich das zumindest.

    Fragt alle gerne nach: epubli.com/kontakt Mehr Fragen und ggf. Bedenken dazu kann wohl nicht schaden.

    Und korrigiert mich gerne falls ich falsch liege, ich würd gerne irren...

    #wegmitki
    #kifrei
    #ki
    #slop
    #selfpublishing
    #buch
    #buchstodon
    #lesen
    #schreiben

  28. @BeeDoubleYou @v_d_richards Und #Epubli schrieb mir per Email sie überlegen das auch zu machen, mit scheinbar Manuskripte alle in US-KIs werfen, und sie empfehlen Leuten die das nicht mögen wegzuwechseln. So verstand ich das zumindest.

    Fragt alle gerne nach: epubli.com/kontakt Mehr Fragen und ggf. Bedenken dazu kann wohl nicht schaden.

    Und korrigiert mich gerne falls ich falsch liege, ich würd gerne irren...

    #wegmitki
    #kifrei
    #ki
    #slop
    #selfpublishing
    #buch
    #buchstodon
    #lesen
    #schreiben

  29. @khzimmer2 @BeeDoubleYou @v_d_richards #tredition könnte ja notfalls auch lokale #LLM Instanzen benutzen.

    Aber anscheinend musste es maximal schädlich für die Schreibenden sein, oder ich weiss auch nicht wie ichs mir sonst erklären soll...

    #wegmitki #kifrei #ki #slop #selfpublishing #buch #buchstodon #lesen #schreiben

  30. @khzimmer2 @BeeDoubleYou @v_d_richards #tredition könnte ja notfalls auch lokale #LLM Instanzen benutzen.

    Aber anscheinend musste es maximal schädlich für die Schreibenden sein, oder ich weiss auch nicht wie ichs mir sonst erklären soll...

    #wegmitki #kifrei #ki #slop #selfpublishing #buch #buchstodon #lesen #schreiben

  31. @khzimmer2 @BeeDoubleYou @v_d_richards #tredition könnte ja notfalls auch lokale #LLM Instanzen benutzen.

    Aber anscheinend musste es maximal schädlich für die Schreibenden sein, oder ich weiss auch nicht wie ichs mir sonst erklären soll...

    #wegmitki #kifrei #ki #slop #selfpublishing #buch #buchstodon #lesen #schreiben

  32. @khzimmer2 @BeeDoubleYou @v_d_richards #tredition könnte ja notfalls auch lokale #LLM Instanzen benutzen.

    Aber anscheinend musste es maximal schädlich für die Schreibenden sein, oder ich weiss auch nicht wie ichs mir sonst erklären soll...

    #wegmitki #kifrei #ki #slop #selfpublishing #buch #buchstodon #lesen #schreiben