Post #2919730

2026-05-14 03:48 UTC

@gfaster@tilde.zone @lina@vt.social i think the issue from the programmer's perspective is that: a very large portion of users *will not care* that the implementation was slop-coded and *stolen*, only that it exists. the credit is erroneously going to go to the person who *stole* Lina's work and nearly none of the credit is going to go to Lina herself who actually did all the hard work here. programming and reverse engineering is very much a field where work being attributed and credited correctly is extremely important, especially when it comes to things like career advancement and just plain *satisfaction in one's work* so her being credited for being the one who did this work is really really important in general. (you may notice I keep emphasizing the word *stolen* here. *stolen* is the only correct word to use here, Lina published her reverse engineering work and progress out of a sense of goodwill and a desire to be transparent to her community, and the slopcoder here stomped all over that and decided to steal *her* work that this person had no right to steal, and take all the credit for it by putting it through a slop generator.)

Replies (1)

@lina@vt.social 2026-05-14 04:16

@amarioguy@social.treehouse.systems @gfaster@tilde.zone It's not even really "stolen", like if someone had done this a month later I couldn't care less, whatever. People will slop. It's also completely valid to take your time and do it by hand and while credit would be nice it's not required, I don't have a copyright on Apple's API. It's this thing where AI can spit out MVPs with zero effort and time and so it allows these people to jump ahead of the person who had the idea in the first place, while investing zero time and learning nothing in the process. Another example: https://bsky.app/profile/freya.bsky.social/post/3mhdsjgf7cc2h @acegikmo@mastodon.social

Open ##2919731