<?xml version="1.0"?>
<!--<!DOCTYPE nitf SYSTEM "nitf-3-4.dtd">-->
<nitf>
  <head>
    <title id="Title">#Title</title>
    <docdata management-doc-idref="">
      <date.issue id="CreationDate" norm="" />
      <du-key id="rev-ver" generation="1" version="Default" />
      <du-key id="Parent-Version" version="" />
      <identified-content>
        <classifier id="newspro-nitf" value="r2" />
        <classifier id="Newspro-App" value="Epaper" />
        <classifier id="Content-Type" value="Story" />
        <classifier id="storyID" value="" />
        <classifier id="CmsConID" value="" />
        <classifier id="Desk" value="" />
        <classifier id="Source" value="" />
        <classifier id="Edition" value="" />
        <classifier id="Category" value="-1" />
        <classifier id="UserName" value="" />
        <classifier id="PublicationDate" value="04/08/2026" />
        <classifier id="PublicationName" value="DailyStar" />
        <classifier id="IsPublished" value="Y" />
        <classifier id="IsPlaced" value="Y" />
        <classifier id="IsCompleated" value="N" />
        <classifier id="IsProofed" value="N" />
        <classifier id="User" value="" />
        <classifier id="Headline-Count" value="" />
        <classifier id="Slug-Count" value="0" />
        <classifier id="Photo-Count" value="0" />
        <classifier id="Caption-Count" value="0" />
        <classifier id="Word-Count" value="0" />
        <classifier id="Character-Count" value="0" />
        <classifier id="Location" value="" />
        <classifier id="TemplateType" value="1" />
        <classifier id="StoryType" value="Story" />
        <classifier id="Author" value="" />
        <classifier id="UOM" value="mm" />
        <classifier id="kicker" value="" />
        <classifier id="ByLine" value="" />
        <classifier id="DateLine" value="" />
        <classifier id="box-geometry" value="402,757,617,1227" />
         <classifier id="Layer" value="Layer 1"/>
          <classifier id="numcol" value="1"/>
         <classifier id="ArticleStyle" value=""/>
       <classifier id="Epaper-Build" value="7.1.5.2"/>
  <classifier id="ProcessingDateTime" value="Mon Aug 03 2026 21:08:00 GMT+0600"/>
      </identified-content>

      <urgency id="home-page" ed-urg="0" />
      <urgency id="priority" ed-urg="0" />
      <doc-scope id="scope" value="0" />
    </docdata>
    <pubdata type="print" name="DailyStar" date.publication="20260804T000000+5.30" edition.name="Dhaka Edition" edition.area="MAI" position.section="DST04082610MAI-NEXTSTEP" position.sequence="10" ex-ref="DST04082610MAI-NEXTSTEP.indd" />
  </head>
  <body boxBorderWeightColor="" boxBorderWeight="">
<body.head>
      <hedline>
    	<hl1 id="Headline1" ul="0" ol="0" ulColor=""  ulWeight=""  olColor=""  olWeight="" textFrameColor="" orgstyle="HEAD new" class="1" MainHead="true" style="Headline1">
		<lang class="3" colour="#000000" orgstyle="HEAD new" style="Headline1"  font="Blacker Pro Display" fontStyle="Bold" size="25">LinkedIn adds ‘seems like AI slop’ reporting button </lang>
	</hl1>

       </hedline>
</body.head>
    <body.content id="Bodytext" CaptionAsBody="0">
     <block>
	<media id="1" media-type="image">
		<media-reference id="tn" source-credit="" data-location="1" source="shutterspeedU_10_MAI_tn.jpg"  Units="pixels" width="50" height="50"></media-reference>
	</media>
</block>

     <p style=".Bodylaser" ul="1" ol="0"  orgstyle="BY NAME LINE new">
	<lang class="3" style=".Bodylaser" colour="#000000" orgstyle="BY NAME LINE new" font="Blacker Pro Display" fontStyle="Bold" size="8">NEXT STEP DESK
</lang>
</p>
<p style=".Bodylaser" ul="0" ol="0"  orgstyle="INDENTLESS BODY new">
	<lang class="3" style=".Bodylaser" colour="#000000" orgstyle="INDENTLESS BODY new" font="Blacker Pro Display" fontStyle="Regular" size="9">LinkedIn has introduced a new reporting option allowing users to flag low-quality AI-generated content in their feed, and has simultaneously removed its own AI post-writing tool, replacing it with a proofreading feature that corrects without replacing the user’s voice. The company’s chief product officer Hari Srinivasan said in a post on the platform that “AI slop is a top priority for all of us” and that people come to LinkedIn to connect with real people and share genuine perspectives. 
</lang>
</p>
<p style=".Bodylaser" ul="0" ol="0"  orgstyle="BODY new">
	<lang class="3" style=".Bodylaser" colour="#000000" orgstyle="BODY new" font="Blacker Pro Display" fontStyle="Regular" size="9">LinkedIn says it is also investing in automation defences that now block hundreds of thousands of automated comment attempts daily, along with millions of other automated interactions in recent months. New classifiers will identify AI-generated or low-quality content and reduce its visibility in recommended posts from outside a user’s network. LinkedIn will also begin privately flagging users’ dashboards when their posts are perceived as inauthentic due to heavy AI use, aiming to help posters improve rather than simply penalise them.</lang>
</p>
<p style=".Bodylaser" ul="0" ol="0"  orgstyle="PHOTO new">
	<lang class="3" style=".Bodylaser" colour="#000000" orgstyle="PHOTO new" font="Verdana" fontStyle="Regular" size="6">IMAGE: </lang>
<lang  class="3" style=".Bodylaser" colour="#000000" orgstyle="PHOTO new" font="Verdana" fontStyle="Bold" size="6">UNSPLASH</lang>
</p>

    </body.content>
  </body>
</nitf>