home.social

#comments — Public Fediverse posts

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

fetched live
  1. NiemanLab: We analyzed 6,400 New York Times stories to find out how comments change when you give readers more information. “Data journalists have sometimes wondered whether loading a story with data can be overwhelming rather than clarifying. We found that giving readers more information changes who comments, and how.”

    https://rbfirehose.com/2026/08/12/niemanlab-we-analyzed-6400-new-york-times-stories-to-find-out-how-comments-change-when-you-give-readers-more-information/
  2. NiemanLab: We analyzed 6,400 New York Times stories to find out how comments change when you give readers more information. “Data journalists have sometimes wondered whether loading a story with data can be overwhelming rather than clarifying. We found that giving readers more information changes who comments, and how.”

    https://rbfirehose.com/2026/08/12/niemanlab-we-analyzed-6400-new-york-times-stories-to-find-out-how-comments-change-when-you-give-readers-more-information/
  3. NiemanLab: We analyzed 6,400 New York Times stories to find out how comments change when you give readers more information. “Data journalists have sometimes wondered whether loading a story with data can be overwhelming rather than clarifying. We found that giving readers more information changes who comments, and how.”

    https://rbfirehose.com/2026/08/12/niemanlab-we-analyzed-6400-new-york-times-stories-to-find-out-how-comments-change-when-you-give-readers-more-information/
  4. NiemanLab: We analyzed 6,400 New York Times stories to find out how comments change when you give readers more information. “Data journalists have sometimes wondered whether loading a story with data can be overwhelming rather than clarifying. We found that giving readers more information changes who comments, and how.”

    https://rbfirehose.com/2026/08/12/niemanlab-we-analyzed-6400-new-york-times-stories-to-find-out-how-comments-change-when-you-give-readers-more-information/
  5. NiemanLab: We analyzed 6,400 New York Times stories to find out how comments change when you give readers more information. “Data journalists have sometimes wondered whether loading a story with data can be overwhelming rather than clarifying. We found that giving readers more information changes who comments, and how.”

    https://rbfirehose.com/2026/08/12/niemanlab-we-analyzed-6400-new-york-times-stories-to-find-out-how-comments-change-when-you-give-readers-more-information/
  6. Tubefilter: So, theoretically, how much does it cost to buy fake views, followers, comments, likes, and shares right now?. “Overall, it found that paying for fakes ‘remains very affordable’ for the average Joe. The most affordable fake? Views, which average $1.40 per 1,000 on TikTok up to $6.70 per 1,000 on YouTube. At the other end of the expense spectrum are comments, which are by far the […]

    https://rbfirehose.com/2026/08/07/tubefilter-so-theoretically-how-much-does-it-cost-to-buy-fake-views-followers-comments-likes-and-shares-right-now/
  7. Tubefilter: So, theoretically, how much does it cost to buy fake views, followers, comments, likes, and shares right now?. “Overall, it found that paying for fakes ‘remains very affordable’ for the average Joe. The most affordable fake? Views, which average $1.40 per 1,000 on TikTok up to $6.70 per 1,000 on YouTube. At the other end of the expense spectrum are comments, which are by far the […]

    https://rbfirehose.com/2026/08/07/tubefilter-so-theoretically-how-much-does-it-cost-to-buy-fake-views-followers-comments-likes-and-shares-right-now/
  8. Tubefilter: So, theoretically, how much does it cost to buy fake views, followers, comments, likes, and shares right now?. “Overall, it found that paying for fakes ‘remains very affordable’ for the average Joe. The most affordable fake? Views, which average $1.40 per 1,000 on TikTok up to $6.70 per 1,000 on YouTube. At the other end of the expense spectrum are comments, which are by far the […]

    https://rbfirehose.com/2026/08/07/tubefilter-so-theoretically-how-much-does-it-cost-to-buy-fake-views-followers-comments-likes-and-shares-right-now/
  9. Tubefilter: So, theoretically, how much does it cost to buy fake views, followers, comments, likes, and shares right now?. “Overall, it found that paying for fakes ‘remains very affordable’ for the average Joe. The most affordable fake? Views, which average $1.40 per 1,000 on TikTok up to $6.70 per 1,000 on YouTube. At the other end of the expense spectrum are comments, which are by far the […]

    https://rbfirehose.com/2026/08/07/tubefilter-so-theoretically-how-much-does-it-cost-to-buy-fake-views-followers-comments-likes-and-shares-right-now/
  10. Tubefilter: So, theoretically, how much does it cost to buy fake views, followers, comments, likes, and shares right now?. “Overall, it found that paying for fakes ‘remains very affordable’ for the average Joe. The most affordable fake? Views, which average $1.40 per 1,000 on TikTok up to $6.70 per 1,000 on YouTube. At the other end of the expense spectrum are comments, which are by far the […]

    https://rbfirehose.com/2026/08/07/tubefilter-so-theoretically-how-much-does-it-cost-to-buy-fake-views-followers-comments-likes-and-shares-right-now/
  11. Not just Mastodon either — it works exactly the same on Bluesky.

    #blogsh #comments

  12. A nice example of how to have comments on a blog with no comment system built in — they’re nothing more than Mastodon replies.

    blogsh.app/posts/2026/blog-sh/

    #blogsh #comments

  13. Why not X, and why Threads waits

    Post read: $0.005 per resource. Post creation: $0.015 per request — $0.200 when it carries a URL. Free public read access: none. Two networks are in. Two are not — and here's the whole reasoning, because "we decided against it" is not a reason.…

    blogsh.app/posts/2026/why-not-

    #philosophy #comments

  14. Why not X, and why Threads waits

    Post read: $0.005 per resource. Post creation: $0.015 per request — $0.200 when it carries a URL. Free public read access: none. Two networks are in. Two are not — and here's the whole reasoning, because "we decided against it" is not a reason.…

    blogsh.app/posts/2026/why-not-

    #philosophy #comments

  15. Why not X, and why Threads waits

    Post read: $0.005 per resource. Post creation: $0.015 per request — $0.200 when it carries a URL. Free public read access: none. Two networks are in. Two are not — and here's the whole reasoning, because "we decided against it" is not a reason.…

    blogsh.app/posts/2026/why-not-

    #philosophy #comments

  16. Why not X, and why Threads waits

    Post read: $0.005 per resource. Post creation: $0.015 per request — $0.200 when it carries a URL. Free public read access: none. Two networks are in. Two are not — and here's the whole reasoning, because "we decided against it" is not a reason.…

    blogsh.app/posts/2026/why-not-

    #philosophy #comments

  17. Why not X, and why Threads waits

    Post read: $0.005 per resource. Post creation: $0.015 per request — $0.200 when it carries a URL. Free public read access: none. Two networks are in. Two are not — and here's the whole reasoning, because "we decided against it" is not a reason.…

    blogsh.app/posts/2026/why-not-

    #philosophy #comments

  18. Our next #JCON2026 session is live: 'Ten Angry #Comments Later: #Stories About #Code Reviews, Teams, and Yesterday’s Code' with Johannes Rabauer

    You open a #pullrequest. Ten comments later, you’re wondering whether the code …

    Grab your coffee and hit play: youtu.be/N5hGP4qQ30I

  19. Our next #JCON2026 session is live: 'Ten Angry #Comments Later: #Stories About #Code Reviews, Teams, and Yesterday’s Code' with Johannes Rabauer

    You open a #pullrequest. Ten comments later, you’re wondering whether the code …

    Grab your coffee and hit play: youtu.be/N5hGP4qQ30I

  20. Our next #JCON2026 session is live: 'Ten Angry #Comments Later: #Stories About #Code Reviews, Teams, and Yesterday’s Code' with Johannes Rabauer

    You open a #pullrequest. Ten comments later, you’re wondering whether the code …

    Grab your coffee and hit play: youtu.be/N5hGP4qQ30I

  21. Our next #JCON2026 session is live: 'Ten Angry #Comments Later: #Stories About #Code Reviews, Teams, and Yesterday’s Code' with Johannes Rabauer

    You open a #pullrequest. Ten comments later, you’re wondering whether the code …

    Grab your coffee and hit play: youtu.be/N5hGP4qQ30I

  22. Our next #JCON2026 session is live: 'Ten Angry #Comments Later: #Stories About #Code Reviews, Teams, and Yesterday’s Code' with Johannes Rabauer

    You open a #pullrequest. Ten comments later, you’re wondering whether the code …

    Grab your coffee and hit play: youtu.be/N5hGP4qQ30I

  23. So, here the fuck I am , back at it again in an #AWS environment and my #devops challenge today is: Instance Scheduler because our dev teams stand up resource shit and then forget about it, and the cost variable goes up to more than 200k a year in total fucking waste.

    Has anyone seen this? if you have how did you deal with it? Because right now, Instance scheduler, #Karpenter, and #ASG are the only real way I see to deal with this bullshit.

    #cloudops #comments

  24. So, here the fuck I am , back at it again in an #AWS environment and my #devops challenge today is: Instance Scheduler because our dev teams stand up resource shit and then forget about it, and the cost variable goes up to more than 200k a year in total fucking waste.

    Has anyone seen this? if you have how did you deal with it? Because right now, Instance scheduler, #Karpenter, and #ASG are the only real way I see to deal with this bullshit.

    #cloudops #comments

  25. So, here the fuck I am , back at it again in an #AWS environment and my #devops challenge today is: Instance Scheduler because our dev teams stand up resource shit and then forget about it, and the cost variable goes up to more than 200k a year in total fucking waste.

    Has anyone seen this? if you have how did you deal with it? Because right now, Instance scheduler, #Karpenter, and #ASG are the only real way I see to deal with this bullshit.

    #cloudops #comments

  26. So, here the fuck I am , back at it again in an #AWS environment and my #devops challenge today is: Instance Scheduler because our dev teams stand up resource shit and then forget about it, and the cost variable goes up to more than 200k a year in total fucking waste.

    Has anyone seen this? if you have how did you deal with it? Because right now, Instance scheduler, #Karpenter, and #ASG are the only real way I see to deal with this bullshit.

    #cloudops #comments

  27. So, here the fuck I am , back at it again in an #AWS environment and my #devops challenge today is: Instance Scheduler because our dev teams stand up resource shit and then forget about it, and the cost variable goes up to more than 200k a year in total fucking waste.

    Has anyone seen this? if you have how did you deal with it? Because right now, Instance scheduler, #Karpenter, and #ASG are the only real way I see to deal with this bullshit.

    #cloudops #comments

  28. Darnit! Brahvim's coding style STRIKES *AGAIN!:*
    ```css
    #comments #comment {
    width: calc(var(--page-w) - 10dvw);
    transition: all 0.2s ease-in-out;
    align-self: center;

    border-style: solid;
    border-radius: 2mm;
    border-width: 1mm;

    padding-bottom: 5%;
    padding-right: 5%;
    padding-left: 5%;
    padding-top: 1%;
    }
    ```

  29. Darnit! Brahvim's coding style STRIKES *AGAIN!:*
    ```css
    #comments #comment {
    width: calc(var(--page-w) - 10dvw);
    transition: all 0.2s ease-in-out;
    align-self: center;

    border-style: solid;
    border-radius: 2mm;
    border-width: 1mm;

    padding-bottom: 5%;
    padding-right: 5%;
    padding-left: 5%;
    padding-top: 1%;
    }
    ```

  30. Darnit! Brahvim's coding style STRIKES *AGAIN!:*
    ```css
    #comments #comment {
    width: calc(var(--page-w) - 10dvw);
    transition: all 0.2s ease-in-out;
    align-self: center;

    border-style: solid;
    border-radius: 2mm;
    border-width: 1mm;

    padding-bottom: 5%;
    padding-right: 5%;
    padding-left: 5%;
    padding-top: 1%;
    }
    ```

  31. Darnit! Brahvim's coding style STRIKES *AGAIN!:*
    ```css
    #comments #comment {
    width: calc(var(--page-w) - 10dvw);
    transition: all 0.2s ease-in-out;
    align-self: center;

    border-style: solid;
    border-radius: 2mm;
    border-width: 1mm;

    padding-bottom: 5%;
    padding-right: 5%;
    padding-left: 5%;
    padding-top: 1%;
    }
    ```

  32. Finland roundwood prices rise in June

    Logs Standing-sale pulpwood prices increased by at least Euro 1 per m3 from May, while June purchase volumes…
    #Finland #FI #Europe #Europa #EU #comments #finland #logs #markets #NaturalResourcesInstituteFinland(Luke) #Suomi #uutiset
    europesays.com/3152245/

  33. For those who don't know, I'm a #software engineer by trade. I've worked in lots of environments, from being a one-person consulting shop, part of a tiny development team at a small business, through contracted R&D to staff at huge corporations and working for governments.

    One of the most frustrating experiences I ever had was in a job at a fair-sized tech company. I was brought in to bring some experience and subject matter expertise to a very junior team. I don't have a problem with juniors; in general they're very enthusiastic and energetic, and it's contagious.

    But this particular team had a couple of people with a ... very strange ... preference. I have long had the habit of adding helpful comments in code - anywhere I think it may help someone understand what a piece of code is doing and why it does it that way, or how other approaches failed until this one was chosen, or marking sharp edges to watch out for. These types of comments are invaluable to someone trying to debug code they don't know well (which can be yourself in six months).

    And in code #reviews, these two co-workers seemed to be offended by the very presence of comments. They would argue for deleting them outright claiming "but this is obvious" - and I'd explain "This is obvious now, because you just learned it. It won't be obvious next year".

    I eventually gave up arguing; it just wasn't worth it. I'd delete #comments every time they complained.

    I suspect that #codebase got difficult after I left.

  34. For those who don't know, I'm a #software engineer by trade. I've worked in lots of environments, from being a one-person consulting shop, part of a tiny development team at a small business, through contracted R&D to staff at huge corporations and working for governments.

    One of the most frustrating experiences I ever had was in a job at a fair-sized tech company. I was brought in to bring some experience and subject matter expertise to a very junior team. I don't have a problem with juniors; in general they're very enthusiastic and energetic, and it's contagious.

    But this particular team had a couple of people with a ... very strange ... preference. I have long had the habit of adding helpful comments in code - anywhere I think it may help someone understand what a piece of code is doing and why it does it that way, or how other approaches failed until this one was chosen, or marking sharp edges to watch out for. These types of comments are invaluable to someone trying to debug code they don't know well (which can be yourself in six months).

    And in code #reviews, these two co-workers seemed to be offended by the very presence of comments. They would argue for deleting them outright claiming "but this is obvious" - and I'd explain "This is obvious now, because you just learned it. It won't be obvious next year".

    I eventually gave up arguing; it just wasn't worth it. I'd delete #comments every time they complained.

    I suspect that #codebase got difficult after I left.

  35. For those who don't know, I'm a #software engineer by trade. I've worked in lots of environments, from being a one-person consulting shop, part of a tiny development team at a small business, through contracted R&D to staff at huge corporations and working for governments.

    One of the most frustrating experiences I ever had was in a job at a fair-sized tech company. I was brought in to bring some experience and subject matter expertise to a very junior team. I don't have a problem with juniors; in general they're very enthusiastic and energetic, and it's contagious.

    But this particular team had a couple of people with a ... very strange ... preference. I have long had the habit of adding helpful comments in code - anywhere I think it may help someone understand what a piece of code is doing and why it does it that way, or how other approaches failed until this one was chosen, or marking sharp edges to watch out for. These types of comments are invaluable to someone trying to debug code they don't know well (which can be yourself in six months).

    And in code #reviews, these two co-workers seemed to be offended by the very presence of comments. They would argue for deleting them outright claiming "but this is obvious" - and I'd explain "This is obvious now, because you just learned it. It won't be obvious next year".

    I eventually gave up arguing; it just wasn't worth it. I'd delete #comments every time they complained.

    I suspect that #codebase got difficult after I left.

  36. For those who don't know, I'm a #software engineer by trade. I've worked in lots of environments, from being a one-person consulting shop, part of a tiny development team at a small business, through contracted R&D to staff at huge corporations and working for governments.

    One of the most frustrating experiences I ever had was in a job at a fair-sized tech company. I was brought in to bring some experience and subject matter expertise to a very junior team. I don't have a problem with juniors; in general they're very enthusiastic and energetic, and it's contagious.

    But this particular team had a couple of people with a ... very strange ... preference. I have long had the habit of adding helpful comments in code - anywhere I think it may help someone understand what a piece of code is doing and why it does it that way, or how other approaches failed until this one was chosen, or marking sharp edges to watch out for. These types of comments are invaluable to someone trying to debug code they don't know well (which can be yourself in six months).

    And in code #reviews, these two co-workers seemed to be offended by the very presence of comments. They would argue for deleting them outright claiming "but this is obvious" - and I'd explain "This is obvious now, because you just learned it. It won't be obvious next year".

    I eventually gave up arguing; it just wasn't worth it. I'd delete #comments every time they complained.

    I suspect that #codebase got difficult after I left.

  37. For those who don't know, I'm a #software engineer by trade. I've worked in lots of environments, from being a one-person consulting shop, part of a tiny development team at a small business, through contracted R&D to staff at huge corporations and working for governments.

    One of the most frustrating experiences I ever had was in a job at a fair-sized tech company. I was brought in to bring some experience and subject matter expertise to a very junior team. I don't have a problem with juniors; in general they're very enthusiastic and energetic, and it's contagious.

    But this particular team had a couple of people with a ... very strange ... preference. I have long had the habit of adding helpful comments in code - anywhere I think it may help someone understand what a piece of code is doing and why it does it that way, or how other approaches failed until this one was chosen, or marking sharp edges to watch out for. These types of comments are invaluable to someone trying to debug code they don't know well (which can be yourself in six months).

    And in code #reviews, these two co-workers seemed to be offended by the very presence of comments. They would argue for deleting them outright claiming "but this is obvious" - and I'd explain "This is obvious now, because you just learned it. It won't be obvious next year".

    I eventually gave up arguing; it just wasn't worth it. I'd delete #comments every time they complained.

    I suspect that #codebase got difficult after I left.

  38. Article says that the bad things didn't materialize
    and the dollar didn't get hit
    even with the #IranWar

    So think of gold at $4K (not $5.3 anymore) as the result of a "dollar relief rally"
    [FORBES allows 3 free articles then paywall]
    "Gold Is the Constant: What's the Signal in Its Decline?"
    #gold #silver #economy #USDollar #strength #weak #metals #price #correction #Bessent #Treasury #comments #press #inflation #pressure
    forbes.com/sites/johntamny/202

  39. Article says that the bad things didn't materialize
    and the dollar didn't get hit
    even with the #IranWar

    So think of gold at $4K (not $5.3 anymore) as the result of a "dollar relief rally"
    [FORBES allows 3 free articles then paywall]
    "Gold Is the Constant: What's the Signal in Its Decline?"
    #gold #silver #economy #USDollar #strength #weak #metals #price #correction #Bessent #Treasury #comments #press #inflation #pressure
    forbes.com/sites/johntamny/202