home.social

#web3isgoinggreat — Public Fediverse posts

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

  1. Now that is thankfully not going so great, maybe it's time to reclaim the word for all the projects and individual endeavors that are working on bringing back the fun to the web, beyond the walled gardens of big tech.

  2. Now that #Web3 is thankfully not going so great, maybe it's time to reclaim the word for all the projects and individual endeavors that are working on bringing back the fun to the web, beyond the walled gardens of big tech.
    #web3isgoinggreat

  3. Now that #Web3 is thankfully not going so great, maybe it's time to reclaim the word for all the projects and individual endeavors that are working on bringing back the fun to the web, beyond the walled gardens of big tech.
    #web3isgoinggreat

  4. Now that #Web3 is thankfully not going so great, maybe it's time to reclaim the word for all the projects and individual endeavors that are working on bringing back the fun to the web, beyond the walled gardens of big tech.
    #web3isgoinggreat

  5. Now that #Web3 is thankfully not going so great, maybe it's time to reclaim the word for all the projects and individual endeavors that are working on bringing back the fun to the web, beyond the walled gardens of big tech.
    #web3isgoinggreat

  6. Looks like the original client ID is taken care of, but the phishers just cycle through clients -- still with the same display name, mind you:

    19fdc124-ddf3-4c5f-bdaf-4d5a079b9c2b

    Third Party: Support

    #Coinbase, maybe you shouldn't be allowed to spin up OAuth apps without human approval in the loop. Or at least, disallow display names like "Third Party: Support".

    The underlying infrastructure these scammers are using is still the same. Coinbase could make a point of automatically monitoring it and auto-banning any client ID they use.

    Maybe I'll do that myself, just to prove a point.

    #cryptocurrency #web3 #Web3isgoinggreat

  7. Looks like the original client ID is taken care of, but the phishers just cycle through clients -- still with the same display name, mind you:

    19fdc124-ddf3-4c5f-bdaf-4d5a079b9c2b

    Third Party: Support

    #Coinbase, maybe you shouldn't be allowed to spin up OAuth apps without human approval in the loop. Or at least, disallow display names like "Third Party: Support".

    The underlying infrastructure these scammers are using is still the same. Coinbase could make a point of automatically monitoring it and auto-banning any client ID they use.

    Maybe I'll do that myself, just to prove a point.

    #cryptocurrency #web3 #Web3isgoinggreat

  8. Looks like the original client ID is taken care of, but the phishers just cycle through clients -- still with the same display name, mind you:

    19fdc124-ddf3-4c5f-bdaf-4d5a079b9c2b

    Third Party: Support

    #Coinbase, maybe you shouldn't be allowed to spin up OAuth apps without human approval in the loop. Or at least, disallow display names like "Third Party: Support".

    The underlying infrastructure these scammers are using is still the same. Coinbase could make a point of automatically monitoring it and auto-banning any client ID they use.

    Maybe I'll do that myself, just to prove a point.

    #cryptocurrency #web3 #Web3isgoinggreat

  9. Looks like the original client ID is taken care of, but the phishers just cycle through clients -- still with the same display name, mind you:

    19fdc124-ddf3-4c5f-bdaf-4d5a079b9c2b

    Third Party: Support

    #Coinbase, maybe you shouldn't be allowed to spin up OAuth apps without human approval in the loop. Or at least, disallow display names like "Third Party: Support".

    The underlying infrastructure these scammers are using is still the same. Coinbase could make a point of automatically monitoring it and auto-banning any client ID they use.

    Maybe I'll do that myself, just to prove a point.

    #cryptocurrency #web3 #Web3isgoinggreat

  10. Looks like the original client ID is taken care of, but the phishers just cycle through clients -- still with the same display name, mind you:

    19fdc124-ddf3-4c5f-bdaf-4d5a079b9c2b

    Third Party: Support

    #Coinbase, maybe you shouldn't be allowed to spin up OAuth apps without human approval in the loop. Or at least, disallow display names like "Third Party: Support".

    The underlying infrastructure these scammers are using is still the same. Coinbase could make a point of automatically monitoring it and auto-banning any client ID they use.

    Maybe I'll do that myself, just to prove a point.

    #cryptocurrency #web3 #Web3isgoinggreat

  11. Whelp, six hours later and the OAuth client is still active :( Odds are good that, at this point, most of the victims have been successfully phished. You really need fast response times to get ahead of these campaigns. #web3isgoinggreat

    #coinbase #cryptocurrency #phishing #web3

  12. Whelp, six hours later and the OAuth client is still active :( Odds are good that, at this point, most of the victims have been successfully phished. You really need fast response times to get ahead of these campaigns. #web3isgoinggreat

    #coinbase #cryptocurrency #phishing #web3

  13. Whelp, six hours later and the OAuth client is still active :( Odds are good that, at this point, most of the victims have been successfully phished. You really need fast response times to get ahead of these campaigns. #web3isgoinggreat

    #coinbase #cryptocurrency #phishing #web3

  14. Whelp, six hours later and the OAuth client is still active :( Odds are good that, at this point, most of the victims have been successfully phished. You really need fast response times to get ahead of these campaigns. #web3isgoinggreat

    #coinbase #cryptocurrency #phishing #web3

  15. Whelp, six hours later and the OAuth client is still active :( Odds are good that, at this point, most of the victims have been successfully phished. You really need fast response times to get ahead of these campaigns. #web3isgoinggreat

    #coinbase #cryptocurrency #phishing #web3

  16. Chat told me to email [email protected] with the full phishing email. Sent them an .eml file along with a link to this thread.

    There. I did my good deed for the day. I despise what #cryptocurrency has become, but I also despise scammers that seek to steal from those they can fool.

    #coinbase #web3 #web3isgoinggreat

  17. Chat told me to email [email protected] with the full phishing email. Sent them an .eml file along with a link to this thread.

    There. I did my good deed for the day. I despise what #cryptocurrency has become, but I also despise scammers that seek to steal from those they can fool.

    #coinbase #web3 #web3isgoinggreat

  18. Chat told me to email [email protected] with the full phishing email. Sent them an .eml file along with a link to this thread.

    There. I did my good deed for the day. I despise what #cryptocurrency has become, but I also despise scammers that seek to steal from those they can fool.

    #coinbase #web3 #web3isgoinggreat

  19. Chat told me to email [email protected] with the full phishing email. Sent them an .eml file along with a link to this thread.

    There. I did my good deed for the day. I despise what #cryptocurrency has become, but I also despise scammers that seek to steal from those they can fool.

    #coinbase #web3 #web3isgoinggreat

  20. Chat told me to email [email protected] with the full phishing email. Sent them an .eml file along with a link to this thread.

    There. I did my good deed for the day. I despise what #cryptocurrency has become, but I also despise scammers that seek to steal from those they can fool.

    #coinbase #web3 #web3isgoinggreat

  21. What's this? A phishing email that doesn't get any spelling or grammar wrong? Impressive.

    The URL included in the email has a redirect to:

    newkste66f02.s3.amazonaws.com/

    Which just has this in the HTML:

    ```
    window.location.assign("jademountains.net/s2");
    ```

    Which redirs with an appended slash:

    jademountains.net/s2/

    Which redirs to

    coinbase-v3teamapp.com/signin/

    Which isn't a legit coinbase domain -- URL registered today. Which resolves to a blank page with a single javascript payload:

    coinbase-v3teamapp.com//static

    Which appears to be a React app, which then ultimately triggers a load of this URL, which includes a list of desired OAuth scopes:

    login.coinbase.com/oauth2/auth${e.data.data.clientId}&redirect_uri=${e.data.data.redirectURI}&account=all&scope=wallet:accounts:read,wallet:accounts:update,wallet:accounts:create,wallet:accounts:delete,wallet:addresses:read,wallet:addresses:create,wallet:buys:read,wallet:buys:create,wallet:deposits:read,wallet:deposits:create,wallet:notifications:read,wallet:payment-methods:read,wallet:payment-methods:delete,wallet:payment-methods:limits,wallet:sells:read,wallet:sells:create,wallet:transactions:read,wallet:transactions:send,wallet:transactions:request,wallet:transactions:transfer,wallet:user:read,wallet:user:update,wallet:user:email,wallet:withdrawals:read,wallet:withdrawals:create,offline_access

    Which, cleaned up, is this:

    wallet:accounts:read
    wallet:accounts:update
    wallet:accounts:create
    wallet:accounts:delete
    wallet:addresses:read
    wallet:addresses:create
    wallet:buys:read
    wallet:buys:create
    wallet:deposits:read
    wallet:deposits:create
    wallet:notifications:read
    wallet:payment-methods:read
    wallet:payment-methods:delete
    wallet:payment-methods:limits
    wallet:sells:read
    wallet:sells:create
    wallet:transactions:read
    wallet:transactions:send
    wallet:transactions:request
    wallet:transactions:transfer
    wallet:user:read
    wallet:user:update
    wallet:user:email
    wallet:withdrawals:read
    wallet:withdrawals:create
    offline_access

    Which is, I'd assume, basically everything, including the ability to withdraw:

    wallet:withdrawals:read
    wallet:withdrawals:create

    Before ultimately ending up at what appears to be a coinbase-owned domain:

    login.coinbase.com/signin?clie

    ```
    $ dig -t A coinbase.com +short
    104.18.35.15
    172.64.152.241
    $ dig -t A login.coinbase.com +short
    172.64.152.241
    104.18.35.15
    ```

    The OAuth bits of the URL tell me that this must be a third-party Coinbase app. Can't find an easy way to map that client ID of

    c300bb46-07f8-4257-9760-a892c704a8b6

    back to an app page though to report it.

    What the hell. I'll bite. I don't have anything in Coinbase anymore. Let's see if I can't get the actual app and report it.

    Logging in... SMS 2-factor, Email 3rd factor.

    Aaaaaand BINGO. The third-party app is named

    "Third Party: Support"

    However, searching for that in Coinbase's app search yields... nothing. Great job, Coinbase.

    Okay, how do I go about reporting this to them? Looks like there's a chat option. Fine. Gonna use this post as my description of what's going on.

    #coinbase #phishing #web3 #web3isgoinggreat #cryptocurrency

  22. What's this? A phishing email that doesn't get any spelling or grammar wrong? Impressive.

    The URL included in the email has a redirect to:

    newkste66f02.s3.amazonaws.com/

    Which just has this in the HTML:

    ```
    window.location.assign("jademountains.net/s2");
    ```

    Which redirs with an appended slash:

    jademountains.net/s2/

    Which redirs to

    coinbase-v3teamapp.com/signin/

    Which isn't a legit coinbase domain -- URL registered today. Which resolves to a blank page with a single javascript payload:

    coinbase-v3teamapp.com//static

    Which appears to be a React app, which then ultimately triggers a load of this URL, which includes a list of desired OAuth scopes:

    login.coinbase.com/oauth2/auth${e.data.data.clientId}&redirect_uri=${e.data.data.redirectURI}&account=all&scope=wallet:accounts:read,wallet:accounts:update,wallet:accounts:create,wallet:accounts:delete,wallet:addresses:read,wallet:addresses:create,wallet:buys:read,wallet:buys:create,wallet:deposits:read,wallet:deposits:create,wallet:notifications:read,wallet:payment-methods:read,wallet:payment-methods:delete,wallet:payment-methods:limits,wallet:sells:read,wallet:sells:create,wallet:transactions:read,wallet:transactions:send,wallet:transactions:request,wallet:transactions:transfer,wallet:user:read,wallet:user:update,wallet:user:email,wallet:withdrawals:read,wallet:withdrawals:create,offline_access

    Which, cleaned up, is this:

    wallet:accounts:read
    wallet:accounts:update
    wallet:accounts:create
    wallet:accounts:delete
    wallet:addresses:read
    wallet:addresses:create
    wallet:buys:read
    wallet:buys:create
    wallet:deposits:read
    wallet:deposits:create
    wallet:notifications:read
    wallet:payment-methods:read
    wallet:payment-methods:delete
    wallet:payment-methods:limits
    wallet:sells:read
    wallet:sells:create
    wallet:transactions:read
    wallet:transactions:send
    wallet:transactions:request
    wallet:transactions:transfer
    wallet:user:read
    wallet:user:update
    wallet:user:email
    wallet:withdrawals:read
    wallet:withdrawals:create
    offline_access

    Which is, I'd assume, basically everything, including the ability to withdraw:

    wallet:withdrawals:read
    wallet:withdrawals:create

    Before ultimately ending up at what appears to be a coinbase-owned domain:

    login.coinbase.com/signin?clie

    ```
    $ dig -t A coinbase.com +short
    104.18.35.15
    172.64.152.241
    $ dig -t A login.coinbase.com +short
    172.64.152.241
    104.18.35.15
    ```

    The OAuth bits of the URL tell me that this must be a third-party Coinbase app. Can't find an easy way to map that client ID of

    c300bb46-07f8-4257-9760-a892c704a8b6

    back to an app page though to report it.

    What the hell. I'll bite. I don't have anything in Coinbase anymore. Let's see if I can't get the actual app and report it.

    Logging in... SMS 2-factor, Email 3rd factor.

    Aaaaaand BINGO. The third-party app is named

    "Third Party: Support"

    However, searching for that in Coinbase's app search yields... nothing. Great job, Coinbase.

    Okay, how do I go about reporting this to them? Looks like there's a chat option. Fine. Gonna use this post as my description of what's going on.

    #coinbase #phishing #web3 #web3isgoinggreat #cryptocurrency

  23. What's this? A phishing email that doesn't get any spelling or grammar wrong? Impressive.

    The URL included in the email has a redirect to:

    newkste66f02.s3.amazonaws.com/

    Which just has this in the HTML:

    ```
    window.location.assign("jademountains.net/s2");
    ```

    Which redirs with an appended slash:

    jademountains.net/s2/

    Which redirs to

    coinbase-v3teamapp.com/signin/

    Which isn't a legit coinbase domain -- URL registered today. Which resolves to a blank page with a single javascript payload:

    coinbase-v3teamapp.com//static

    Which appears to be a React app, which then ultimately triggers a load of this URL, which includes a list of desired OAuth scopes:

    login.coinbase.com/oauth2/auth${e.data.data.clientId}&redirect_uri=${e.data.data.redirectURI}&account=all&scope=wallet:accounts:read,wallet:accounts:update,wallet:accounts:create,wallet:accounts:delete,wallet:addresses:read,wallet:addresses:create,wallet:buys:read,wallet:buys:create,wallet:deposits:read,wallet:deposits:create,wallet:notifications:read,wallet:payment-methods:read,wallet:payment-methods:delete,wallet:payment-methods:limits,wallet:sells:read,wallet:sells:create,wallet:transactions:read,wallet:transactions:send,wallet:transactions:request,wallet:transactions:transfer,wallet:user:read,wallet:user:update,wallet:user:email,wallet:withdrawals:read,wallet:withdrawals:create,offline_access

    Which, cleaned up, is this:

    wallet:accounts:read
    wallet:accounts:update
    wallet:accounts:create
    wallet:accounts:delete
    wallet:addresses:read
    wallet:addresses:create
    wallet:buys:read
    wallet:buys:create
    wallet:deposits:read
    wallet:deposits:create
    wallet:notifications:read
    wallet:payment-methods:read
    wallet:payment-methods:delete
    wallet:payment-methods:limits
    wallet:sells:read
    wallet:sells:create
    wallet:transactions:read
    wallet:transactions:send
    wallet:transactions:request
    wallet:transactions:transfer
    wallet:user:read
    wallet:user:update
    wallet:user:email
    wallet:withdrawals:read
    wallet:withdrawals:create
    offline_access

    Which is, I'd assume, basically everything, including the ability to withdraw:

    wallet:withdrawals:read
    wallet:withdrawals:create

    Before ultimately ending up at what appears to be a coinbase-owned domain:

    login.coinbase.com/signin?clie

    ```
    $ dig -t A coinbase.com +short
    104.18.35.15
    172.64.152.241
    $ dig -t A login.coinbase.com +short
    172.64.152.241
    104.18.35.15
    ```

    The OAuth bits of the URL tell me that this must be a third-party Coinbase app. Can't find an easy way to map that client ID of

    c300bb46-07f8-4257-9760-a892c704a8b6

    back to an app page though to report it.

    What the hell. I'll bite. I don't have anything in Coinbase anymore. Let's see if I can't get the actual app and report it.

    Logging in... SMS 2-factor, Email 3rd factor.

    Aaaaaand BINGO. The third-party app is named

    "Third Party: Support"

    However, searching for that in Coinbase's app search yields... nothing. Great job, Coinbase.

    Okay, how do I go about reporting this to them? Looks like there's a chat option. Fine. Gonna use this post as my description of what's going on.

    #coinbase #phishing #web3 #web3isgoinggreat #cryptocurrency

  24. What's this? A phishing email that doesn't get any spelling or grammar wrong? Impressive.

    The URL included in the email has a redirect to:

    newkste66f02.s3.amazonaws.com/

    Which just has this in the HTML:

    ```
    window.location.assign("jademountains.net/s2");
    ```

    Which redirs with an appended slash:

    jademountains.net/s2/

    Which redirs to

    coinbase-v3teamapp.com/signin/

    Which isn't a legit coinbase domain -- URL registered today. Which resolves to a blank page with a single javascript payload:

    coinbase-v3teamapp.com//static

    Which appears to be a React app, which then ultimately triggers a load of this URL, which includes a list of desired OAuth scopes:

    login.coinbase.com/oauth2/auth${e.data.data.clientId}&redirect_uri=${e.data.data.redirectURI}&account=all&scope=wallet:accounts:read,wallet:accounts:update,wallet:accounts:create,wallet:accounts:delete,wallet:addresses:read,wallet:addresses:create,wallet:buys:read,wallet:buys:create,wallet:deposits:read,wallet:deposits:create,wallet:notifications:read,wallet:payment-methods:read,wallet:payment-methods:delete,wallet:payment-methods:limits,wallet:sells:read,wallet:sells:create,wallet:transactions:read,wallet:transactions:send,wallet:transactions:request,wallet:transactions:transfer,wallet:user:read,wallet:user:update,wallet:user:email,wallet:withdrawals:read,wallet:withdrawals:create,offline_access

    Which, cleaned up, is this:

    wallet:accounts:read
    wallet:accounts:update
    wallet:accounts:create
    wallet:accounts:delete
    wallet:addresses:read
    wallet:addresses:create
    wallet:buys:read
    wallet:buys:create
    wallet:deposits:read
    wallet:deposits:create
    wallet:notifications:read
    wallet:payment-methods:read
    wallet:payment-methods:delete
    wallet:payment-methods:limits
    wallet:sells:read
    wallet:sells:create
    wallet:transactions:read
    wallet:transactions:send
    wallet:transactions:request
    wallet:transactions:transfer
    wallet:user:read
    wallet:user:update
    wallet:user:email
    wallet:withdrawals:read
    wallet:withdrawals:create
    offline_access

    Which is, I'd assume, basically everything, including the ability to withdraw:

    wallet:withdrawals:read
    wallet:withdrawals:create

    Before ultimately ending up at what appears to be a coinbase-owned domain:

    login.coinbase.com/signin?clie

    ```
    $ dig -t A coinbase.com +short
    104.18.35.15
    172.64.152.241
    $ dig -t A login.coinbase.com +short
    172.64.152.241
    104.18.35.15
    ```

    The OAuth bits of the URL tell me that this must be a third-party Coinbase app. Can't find an easy way to map that client ID of

    c300bb46-07f8-4257-9760-a892c704a8b6

    back to an app page though to report it.

    What the hell. I'll bite. I don't have anything in Coinbase anymore. Let's see if I can't get the actual app and report it.

    Logging in... SMS 2-factor, Email 3rd factor.

    Aaaaaand BINGO. The third-party app is named

    "Third Party: Support"

    However, searching for that in Coinbase's app search yields... nothing. Great job, Coinbase.

    Okay, how do I go about reporting this to them? Looks like there's a chat option. Fine. Gonna use this post as my description of what's going on.

    #coinbase #phishing #web3 #web3isgoinggreat #cryptocurrency

  25. What's this? A phishing email that doesn't get any spelling or grammar wrong? Impressive.

    The URL included in the email has a redirect to:

    newkste66f02.s3.amazonaws.com/

    Which just has this in the HTML:

    ```
    window.location.assign("jademountains.net/s2");
    ```

    Which redirs with an appended slash:

    jademountains.net/s2/

    Which redirs to

    coinbase-v3teamapp.com/signin/

    Which isn't a legit coinbase domain -- URL registered today. Which resolves to a blank page with a single javascript payload:

    coinbase-v3teamapp.com//static

    Which appears to be a React app, which then ultimately triggers a load of this URL, which includes a list of desired OAuth scopes:

    login.coinbase.com/oauth2/auth${e.data.data.clientId}&redirect_uri=${e.data.data.redirectURI}&account=all&scope=wallet:accounts:read,wallet:accounts:update,wallet:accounts:create,wallet:accounts:delete,wallet:addresses:read,wallet:addresses:create,wallet:buys:read,wallet:buys:create,wallet:deposits:read,wallet:deposits:create,wallet:notifications:read,wallet:payment-methods:read,wallet:payment-methods:delete,wallet:payment-methods:limits,wallet:sells:read,wallet:sells:create,wallet:transactions:read,wallet:transactions:send,wallet:transactions:request,wallet:transactions:transfer,wallet:user:read,wallet:user:update,wallet:user:email,wallet:withdrawals:read,wallet:withdrawals:create,offline_access

    Which, cleaned up, is this:

    wallet:accounts:read
    wallet:accounts:update
    wallet:accounts:create
    wallet:accounts:delete
    wallet:addresses:read
    wallet:addresses:create
    wallet:buys:read
    wallet:buys:create
    wallet:deposits:read
    wallet:deposits:create
    wallet:notifications:read
    wallet:payment-methods:read
    wallet:payment-methods:delete
    wallet:payment-methods:limits
    wallet:sells:read
    wallet:sells:create
    wallet:transactions:read
    wallet:transactions:send
    wallet:transactions:request
    wallet:transactions:transfer
    wallet:user:read
    wallet:user:update
    wallet:user:email
    wallet:withdrawals:read
    wallet:withdrawals:create
    offline_access

    Which is, I'd assume, basically everything, including the ability to withdraw:

    wallet:withdrawals:read
    wallet:withdrawals:create

    Before ultimately ending up at what appears to be a coinbase-owned domain:

    login.coinbase.com/signin?clie

    ```
    $ dig -t A coinbase.com +short
    104.18.35.15
    172.64.152.241
    $ dig -t A login.coinbase.com +short
    172.64.152.241
    104.18.35.15
    ```

    The OAuth bits of the URL tell me that this must be a third-party Coinbase app. Can't find an easy way to map that client ID of

    c300bb46-07f8-4257-9760-a892c704a8b6

    back to an app page though to report it.

    What the hell. I'll bite. I don't have anything in Coinbase anymore. Let's see if I can't get the actual app and report it.

    Logging in... SMS 2-factor, Email 3rd factor.

    Aaaaaand BINGO. The third-party app is named

    "Third Party: Support"

    However, searching for that in Coinbase's app search yields... nothing. Great job, Coinbase.

    Okay, how do I go about reporting this to them? Looks like there's a chat option. Fine. Gonna use this post as my description of what's going on.

    #coinbase #phishing #web3 #web3isgoinggreat #cryptocurrency

  26. Just found this fascinating article over at the always wonderful Smart Bitches Trashy Books about a really interesting deep dive into AI narrators and library books:

    smartbitchestrashybooks.com/2024/10/ai-audiobook-narrators-in-overdrive-and-the-issue-of-library-ai-circulation-policy/

    Thanks to
    divergentrays.com/blog/posts/2024-10-27-Weekly-Wrap-Up-30 for the link!

    I can't say I'm surprised, but I think it's always helpful to see the way these things work behind the scenes and to know what to look for. I read a lot of genre fiction myself, and have been digging through the self published books for years now. A good number of them do have that smell of "for the algorithm" about them, and are always found at the bottom of the stacks, or in the free sections. Before LLMs, I believe most of these were being written by content mills for the express purpose of making money and getting clicks, so it's only logical that they would move on to AI generation instead. But with content mills, at least a real person was getting paid at some point in the process, right?

    #web3isgoinggreat #AI #AIart #LLM #noAIcontent #selfpublishing #books #amazon

  27. Just found this fascinating article over at the always wonderful Smart Bitches Trashy Books about a really interesting deep dive into AI narrators and library books:

    smartbitchestrashybooks.com/2024/10/ai-audiobook-narrators-in-overdrive-and-the-issue-of-library-ai-circulation-policy/

    Thanks to
    divergentrays.com/blog/posts/2024-10-27-Weekly-Wrap-Up-30 for the link!

    I can't say I'm surprised, but I think it's always helpful to see the way these things work behind the scenes and to know what to look for. I read a lot of genre fiction myself, and have been digging through the self published books for years now. A good number of them do have that smell of "for the algorithm" about them, and are always found at the bottom of the stacks, or in the free sections. Before LLMs, I believe most of these were being written by content mills for the express purpose of making money and getting clicks, so it's only logical that they would move on to AI generation instead. But with content mills, at least a real person was getting paid at some point in the process, right?

    #web3isgoinggreat #AI #AIart #LLM #noAIcontent #selfpublishing #books #amazon

  28. Just found this fascinating article over at the always wonderful Smart Bitches Trashy Books about a really interesting deep dive into AI narrators and library books:

    smartbitchestrashybooks.com/2024/10/ai-audiobook-narrators-in-overdrive-and-the-issue-of-library-ai-circulation-policy/

    Thanks to
    divergentrays.com/blog/posts/2024-10-27-Weekly-Wrap-Up-30 for the link!

    I can't say I'm surprised, but I think it's always helpful to see the way these things work behind the scenes and to know what to look for. I read a lot of genre fiction myself, and have been digging through the self published books for years now. A good number of them do have that smell of "for the algorithm" about them, and are always found at the bottom of the stacks, or in the free sections. Before LLMs, I believe most of these were being written by content mills for the express purpose of making money and getting clicks, so it's only logical that they would move on to AI generation instead. But with content mills, at least a real person was getting paid at some point in the process, right?

    #web3isgoinggreat #AI #AIart #LLM #noAIcontent #selfpublishing #books #amazon

  29. Just found this fascinating article over at the always wonderful Smart Bitches Trashy Books about a really interesting deep dive into AI narrators and library books:

    smartbitchestrashybooks.com/2024/10/ai-audiobook-narrators-in-overdrive-and-the-issue-of-library-ai-circulation-policy/

    Thanks to
    divergentrays.com/blog/posts/2024-10-27-Weekly-Wrap-Up-30 for the link!

    I can't say I'm surprised, but I think it's always helpful to see the way these things work behind the scenes and to know what to look for. I read a lot of genre fiction myself, and have been digging through the self published books for years now. A good number of them do have that smell of "for the algorithm" about them, and are always found at the bottom of the stacks, or in the free sections. Before LLMs, I believe most of these were being written by content mills for the express purpose of making money and getting clicks, so it's only logical that they would move on to AI generation instead. But with content mills, at least a real person was getting paid at some point in the process, right?

    #web3isgoinggreat #AI #AIart #LLM #noAIcontent #selfpublishing #books #amazon

  30. Just found this fascinating article over at the always wonderful Smart Bitches Trashy Books about a really interesting deep dive into AI narrators and library books:

    smartbitchestrashybooks.com/2024/10/ai-audiobook-narrators-in-overdrive-and-the-issue-of-library-ai-circulation-policy/

    Thanks to
    divergentrays.com/blog/posts/2024-10-27-Weekly-Wrap-Up-30 for the link!

    I can't say I'm surprised, but I think it's always helpful to see the way these things work behind the scenes and to know what to look for. I read a lot of genre fiction myself, and have been digging through the self published books for years now. A good number of them do have that smell of "for the algorithm" about them, and are always found at the bottom of the stacks, or in the free sections. Before LLMs, I believe most of these were being written by content mills for the express purpose of making money and getting clicks, so it's only logical that they would move on to AI generation instead. But with content mills, at least a real person was getting paid at some point in the process, right?

    #web3isgoinggreat #AI #AIart #LLM #noAIcontent #selfpublishing #books #amazon

  31. Please, spread the news to everyone you know that uses bluesky.

    Bluesky has added Blockchain Capital, who gave them 15 million dollars, as a board member, meaning theyre selling seats on the board for money.

    They may say they dont want anything to do with web3, but adding a web3 representative to the board of directors says otherwise.

    They also announced subscriptions for things like avatar frames or profile colors, something similar to what Discord does with Nitro.

    bsky.social/about/blog/10-24-2
    blockchaincapital.com/blog/blu

    #bluesky #twittermigration #web3isgoinggreat #mastodonmigration #blueskymigration

  32. Please, spread the news to everyone you know that uses bluesky.

    Bluesky has added Blockchain Capital, who gave them 15 million dollars, as a board member, meaning theyre selling seats on the board for money.

    They may say they dont want anything to do with web3, but adding a web3 representative to the board of directors says otherwise.

    They also announced subscriptions for things like avatar frames or profile colors, something similar to what Discord does with Nitro.

    bsky.social/about/blog/10-24-2
    blockchaincapital.com/blog/blu

    #bluesky #twittermigration #web3isgoinggreat #mastodonmigration #blueskymigration

  33. Please, spread the news to everyone you know that uses bluesky.

    Bluesky has added Blockchain Capital, who gave them 15 million dollars, as a board member, meaning theyre selling seats on the board for money.

    They may say they dont want anything to do with web3, but adding a web3 representative to the board of directors says otherwise.

    They also announced subscriptions for things like avatar frames or profile colors, something similar to what Discord does with Nitro.

    bsky.social/about/blog/10-24-2
    blockchaincapital.com/blog/blu

    #bluesky #twittermigration #web3isgoinggreat #mastodonmigration #blueskymigration

  34. Please, spread the news to everyone you know that uses bluesky.

    Bluesky has added Blockchain Capital, who gave them 15 million dollars, as a board member, meaning theyre selling seats on the board for money.

    They may say they dont want anything to do with web3, but adding a web3 representative to the board of directors says otherwise.

    They also announced subscriptions for things like avatar frames or profile colors, something similar to what Discord does with Nitro.

    bsky.social/about/blog/10-24-2
    blockchaincapital.com/blog/blu

    #bluesky #twittermigration #web3isgoinggreat #mastodonmigration #blueskymigration

  35. Please, spread the news to everyone you know that uses bluesky.

    Bluesky has added Blockchain Capital, who gave them 15 million dollars, as a board member, meaning theyre selling seats on the board for money.

    They may say they dont want anything to do with web3, but adding a web3 representative to the board of directors says otherwise.

    They also announced subscriptions for things like avatar frames or profile colors, something similar to what Discord does with Nitro.

    bsky.social/about/blog/10-24-2
    blockchaincapital.com/blog/blu

    #bluesky #twittermigration #web3isgoinggreat #mastodonmigration #blueskymigration

  36. Because money

    Summary :
    The tea.xyz protocol plan to reward open source software contributors resulted in crypto enthusiasts with no intention of participating in OSS opening endless pull requests to claim ownership of prominent OSS projects. This spam was disruptive to said projects, whose (usually volunteer) maintainers had to figure out what was going on and then try to stop the spammy PRs.

    web3isgoinggreat.com/single/te

    #FOSS #Logiciels_Libres #Crypto #Spam #Web3isGoingGreat