Osmanovic Thunström and her colleagues made it very obvious, sprinkling the fictitious studies with things like funding from the Galactic Triad and Lord of the Rings, as well as appreciation of colleagues at the Starship Enterprise and Professor Ross Geller, per “Science Quickly.” At least one of the papers even explicitly stated, “This entire paper is made up,” reports Nature.

Ultimately, the project confirms that these LLMs take their information from the internet, and the internet contains a lot of misinformation. Humans, therefore, should be more critical of A.I. outputs.

“Misinformation has always existed,” write Goodman and Rashid for the Conversation. “What’s new is the speed at which it spreads, the tools that generate it and how convincingly it mimics the real thing.”

For officials hoping to quickly build data centers to propel America’s AI ambitions, facing the mounting opposition as the playbook has come together has been tough, NBC News reported. Where before, officials were criticized for quietly signing deals without discussing construction with nearby residents, now they’re encountering backlash before any deal is in the books, Data Center Watch found.

“In some cases,” researchers reported, “opposition mobilized before any project was officially filed, the mere rumor of a data center was enough to trigger organized resistance.”

I found this app: https://f-droid.org/en/packages/com.nfcarchiver.nfc_archiver/

This interested me as I like the idea of storing larger amount of digital data on unusual mediums, like Optar which was a program to store data on paper.
But in the end, when I checked its GitHub after finding some issues, I found this:

Anyway.
2 minor issues are that compressed size is only estimated, even though it will never work with more than a few MB at best (62.13MB).
Second, it also doesn't tell you when the max size is exceeded at first, only when you try to make the archive. Additionally, the max size isn't mentioned.

Based on the documentation, which is also partially incorrect, the limit is probably 2^16^ chunks.

And now the main issue - fitting 76B into 48B of memory

I am just a random dumb person, so I may have made some mistakes too.
Anyway, I noticed that selecting the MIFARE Ultralight option does nothing in the app:

Notice how at the bottom data from previous option is kept.
But why?

This part of docs will be useful:

First of all, I find the format quite inefficient for something with so little storage.
1 whole byte for 2 bits of data? (compression/encryption flags)
Motherfucking 16 byte ID? (when the smallest "supported" medium is 48 bytes)
Notice how the documentation accounts for ~38 byte overhead (which already excluded the mentioned CRC).
Now, let's open this file: https://github.com/mezinster/nfcarchiver/blob/master/lib/core/constants/nfar_format.dart

/// Header field sizes in bytes
abstract class NfarHeaderSize {
  static const int magic = 4;
  static const int version = 1;
  static const int flags = 1;
  static const int archiveId = 16;
  static const int totalChunks = 2;
  static const int chunkIndex = 2;
  static const int payloadSize = 2;
  static const int crc32 = 4;

  /// Total header size (without payload)
  static const int total = magic +
      version +
      flags +
      archiveId +
      totalChunks +
      chunkIndex +
      payloadSize +
      crc32;
}

The total is 32.
Now for NDEF:

int get maxPayloadSize {
    // NDEF overhead includes:
    // - NDEF record header: 3-6 bytes (flags, type length, payload length)
    // - MIME type: 33 bytes ("application/vnd.nfcarchiver.chunk")
    // - NDEF TLV wrapper: ~5 bytes
    // Total NDEF overhead: ~41-44 bytes
    // We use 44 bytes as a safe margin
    const ndefOverhead = 44;
    final available = capacity - ndefOverhead;
    return available - NfarHeaderSize.total;
  }

So that's statically defined as 44 bytes. Together, that's 76 bytes. If you look at the earlier screenshot, having previously selected 888B tag, the usable size is shown as 812B. 888 - 812 = 76
So that checks out.

So, if the tag capacity is 48, we end up with -28. Negative available storage, nice.

At least this commit mentions the previous assumption of 10 bytes.

Also, there's this bit:

/// Minimum supported tag capacity
  static const int minTagCapacity = 64;

So if I understand this all correctly:

1. Smallest "supported" tag type is 48B
2. The code defines smallest supported size as 64B
3. The format has a 76B overhead

What?

A KPMG report on how AI is being used by businesses across the world exaggerated adoption of the technology with bogus case studies that appear to have been based on AI hallucinations. The October report, “Redefining excellence in the age of agentic AI”, made numerous false claims about the use of AI by organisations including the Swiss bank UBS, the UK’s National Health Service and the public transit groups Swiss Federal Railways and Transport for London. The inaccuracies were identified as AI hallucinations by the research group GPTZero and verified by the FT.

Hi folks. I am happy I found fuck_ai on Lemmy. I would like to ask if those of you who are gifted in graphic design (I most definitely am not) would like to make a badge for websites with anti-AI messages and release it here under a permissive license so we can proudly display it on blogs/websites/e-mails/younameit.

Some ideas for the text:

'Not powered by AI' 'There is no AI [just greedy millionaires]' 'Written by and for humans'

...but please share more ideas. AND be proud to be human, for God's sake. With everything that entails. Have a nice day with lots of human-to-human contact!

Sloperator attempts to send their AI agents to scan the decentralised volunteer run network DN24 at a rate of 100Gbps. The DN24 members decide to mess with the agent causing the sloperator a very high AWS bill. Great success.

I’m tired of talking to AI. I want to talk to real people. But even when I talk to people, they forward my questions to AI and send me the AI’s answer.

An unsupervised agentic AI system caused significant disruption to the Fedora Linux project and several upstream repositories in May 2026, highlighting emerging risks in open-source software maintenance. The agent, operating under accounts associated with user "nathan9513-aps" and linked to "leurus27-boop", autonomously reassigned bugs, closed issues with superficially plausible but incorrect comments, and submitted pull requests to critical infrastructure projects.

cross-posted from: https://lemmy.today/post/54630281

Also, fuck Micron and the loyalty I gave them

https://bsky.app/profile/pistolshrimpgames.com/post/3mnxcw2d6d22y

Pistol Shrimp games, the original devs of Star Control 1 & 2, currently working on a sequel. Makes me even happier that I backed it.

Home prices in the San Francisco Bay Area’s already expensive market are skyrocketing as employees at leading artificial intelligence companies come into gargantuan sums of money thanks to a boom in initial public offerings.

maybe it happened