• 8 Posts
  • 906 Comments
Joined 2 years ago
cake
Cake day: July 7th, 2023

help-circle



  • Am engineer. Know zero professional people in the engineering community who use AI browsers, and very few who even touch AI for anything aside from docs or stats.

    In my personal life I know zero people who use these browsers. I think this is just panic from the higher ups at Mozilla who have no idea what in the fuck the company should be doing or is about, even.

    Start making tools to give to people to combat this bullshit from the EU. Build a USABLE and decentralized chat app that people can actually use FFS. Build something like Proton and ACTUALLY BECOME SELF-SUFFICIENT.

    Others have eaten your lunch because of this exact thing. Do better.







  • It’s not about their actual effectiveness, it’s about the justification people use to force more “AI” reasons to fire people, reduce pay, eliminate jobs, and so on, and so on…

    Literally the first point in this speech, though broad, is making that case. A very small number of people are forcing this shit down people’s throats, and using it to justify the loss of monumental numbers of jobs.

    Feel free to look up Amazon’s upcoming waves of layoffs, Salesforce, Google, HP…etc. Amazon alone claims they will be replacing 150k jobs in the US alone in the next year with robots. Again, first point brought up by Bernie.




  • (typing quickly, excuse errors)

    Title: The title is both confusing and misleading to the actual topic being discussed, which is CVEs being used to identify vulnerabilities to be exploited. The tool is irrelevant, and the tool in the headline is actually mentioned very little in the content.

    Staying on topic: the title sets out a few things as the topics: 1) NPMScan 2) Vulnerabilities 3) Frameworks being exploited.

    It then shifts in the first details to middleware exploits, and how routes are mishandled. So a reader might be asking "Wait, is this a post about middleware attacks, or something specific to NPMScan/CVE exploits?

    A title or headline should be a simple summarization of the topics discussed, and the content should stick to what those topics are. A more accurate title to this piece would be “How Hackers use CVE information to craft exploits in X, Y and Z”

    Diversion from topics: While keeping the meat of an article as close to the main topic thread, it’s important explain the when/where/why you are diverting from that thread for context. When doing so, you’re explaining the relationship between your main topic, and this new information being pertinent and important to the discussion overall.

    Just adding a bunch of unrelated information leaves the reader confused about what those ties to the main thread are, and usually will be forgotten or skipped if they came to your content based on the headline and looking for specific information.

    An example of this being used horribly all over the place is recipe sites. You go looking for a Holiday Cookie recipe, and are presented with with pages of journal entries about the authors childhood cookie memories. It’s not pertinent to the actual content being requested, and people will skip it.




  • NEVER EVER EVER pay anything to anyone if they are making claims like this.

    Simply respond with “Our legal team’s process requires a filed Cease and Desist to be sent directly to them with specific references to infringements based on your claims. Once they have received this, the offending content will be immediately rectified.”

    Even if it’s your personal website. Don’t even fucking bother with these people and waste your time and money worrying about it, be sure this is the very first step in any legal action over public content. They can’t just jump to suing you or demanding money.

    Scammers will fuck right off.