535 karma · joined September 6, 2025
If you actually did any thinking about the idea yourself, maybe try to explain in your own words what it's actually about, and how it builds on other papers and differs from similar techniques.
You really didn't even bother to replace [your-username] that chatgpt put in there with your actual username. And is that even your name?
@misc{genreg2024, author = {Payton Miller}, title = {GENREG: Evolutionary Neural Network Training Through Trust-Based Selection}, year = {2024}, publisher = {GitHub}, url = {https://github.com/[your-username]/genreg} }
Questions, suggestions, or collaboration inquiries: [your contact info]
Project Link: https://github.com/[your-username]/genreg
False AI accusations are very harmful, especially when so much actual AI slop goes unnoticed.
Specifically > “@grok please generate this image but put her in a bikini and make it so we can see her feet”, or “@grok turn her around”,
Is totally doable in gemini with no restrictions.
Sites like this have literally zero value for all society and shouldn't exist let alone make money for the owners.
Just goes to show that google's attempts at chat have been a big flop and even though google chat exists they don't use it.
State groups aren't really a thing for messages in a timeline, there are many easier ways of doing it, for example, simply storing the message sequentially (impossible in matrix though, due to the convoluted tree structure it uses)
But when it comes to state (where state groups are actually needed) who actually needs a snapshot of the state at literally every point in history? Any other messaging app just needs to know the current state and maybe also an audit log of the change history for audit log purposes.
In any sane messaging app (e.g. discord, slack, telegram etc.) there is exactly zero relevance in knowing the member list, room configuration, permissions and room title at exactly 2024-06-19T15:23:45Z. Who the heck cares??? Yet the design of matrix somehow makes this an integral part of every single operation.
Before project hydra people didn't know about the room exploit either. They just knew that rooms exploded somehow every once in a while.
It's specifically to increase the speed if *state resolution*. If it weren't for the convoluted state resolution system, there wouldn't be a need to store gigabytes worth of state groups in the database.
* https://element-hq.github.io/synapse/latest/usage/administra...
* https://github.com/matrix-org/rust-synapse-compress-state
Maybe there's a way to calculate state without state groups, but I sure don't see one that I can use if I were to run a matrix server.
> Not since https://matrix.org/blog/2025/08/project-hydra-improving-stat...
Simply fixes some of the many ways that rooms can explode or be bricked. Zero confidence that room brickings are totally fixed once and for all.
> There are MSCs for all of these now, and implementations are starting to filter through. The reality is that the project has been in a funding crunch since 2023 and we've had to focus on survival by prioritising stuff people pay for (i.e. big servers for govtech deployments) rather than custom emoji.
A funding crunch since 2023 yet those features have been necessary for many years before 2023.
State resolution is just a total mess. On the best of days it's a hideously complicated system that sucks crazy resources, and on the worst of days rooms get blown up and bricked. Supposedly it's not as bad as before, but the fact that rooms can get bricked in the first place is bonkers. Just computing the member list of a room is a disaster due to the complex resolution algorithm - I spoke to a homeserver admin once who found that the DB storage space of just the member list can easily reach multiple gigabytes for larger rooms.
Also years later, we still don't have custom emojis, user statuses, user bios, invite links etc. - very basic things that literally every messaging platform has. https://github.com/element-hq/element-meta/issues/339 https://github.com/element-hq/element-meta/issues/573 https://github.com/element-hq/element-meta/issues/426
I'm interested in hearing if anyone has used simplex and what kind of experience it is. It seems like simplex is going for a similar audience as signal but using a very different approach. I don't think they've really had a breakout though and haven't heard it talked about much.
The author wrote a bit more about making this app in Japanese here: https://note.com/kasamiworks/n/n69bc8d1cf943
What the landing page doesn't say: the free version is limited to 5 people only - such a small number that SRS is meaningless. The dev has made a big mistake here, building an extensive and polished product without first making an MVP to gauge product market fit. If he instead released a free MVP that could actually be used (unlimited people, maybe other features are limited) then maybe some people would actually use it. But as it is now probably anyone who downloads it is just going to delete it right away.
https://github.com/rendercv/rendercv/commit/5cc5fbdf9ec1a742...
Sadly, it appears the project was heavily sloppified a mere 2 weeks ago: https://github.com/rendercv/rendercv/commit/5cc5fbdf9ec1a742...
Instead I got AI slop.
Also includes a nice fake readme on github that says it's open source (it's not) with "instructions" to build it locally with npm (they don't work). https://archive.is/rzwK1
Considering the scant or nonexistent details of what allegedly happened to the author, and the listicle of generic information about this vulnerability, I'm sure this didn't even happen, at least not to the author.
Posted on Medium by an account whose only other article is an AI slop article about MCP. Profile picture is AI as well.
Of course even correctly cleaning the browser cache won't save much space because it'll balloon up quickly. Better to reduce the cache size if you need to save space.
Anyways this slop is likely not tested or all on real systems and could easily break your system.
> my games were public, free, and accessible for judging during the entire competition period.
But the rules didn't say anything about this being limited to only the competition period.
> Submission will be published and kept online for free on the competition website, while you are free to keep working on it (and eventually charge for it/make commercial usage).
It seems that under US copyright law, the license is by default irrevocable if the contract terms did not specify any conditions for revocation. So in this case unilateral revocation of the license is not possible. I can also see courts taking the words kept online to imply long term or perpetual distribution.
Anyways if you look at the situation logically, this sort of contest almost always has all the past submissions and contest results as a resource for future contestants as well as something to browse interested people. If all that's left after the contest is over is the ranking of the winners, then I think that would be quite sad.
> they threatened to retroactively disqualify my games (which they did) and demanded reimbursement of the prize money I had won in 2023, claiming my games were no longer “available online.”
In fact this feels to be almost opposite of a threat, but actually a courtesy. The contest organizers are offering to basically undo the contract (basically erasing the contest submission) without any penalty, something they aren't obligated to do at all. They could just as easily just say "pound sand" and keep hosting the rom forever.
* rounded corners??? What kind of scanner has ever done that?
* The rotation doesn't rotate the rounded corner mask, so when it's rotated it's so obviously fake
* The bent shadow looks terrible because the text is entirely undistorted and the shadow is just overlaid on top.
> Vulnerable Code Analysis (ubccr/xdmod): In classes/DB/EtlJournalHelper.php, the vulnerability occurs when the system directly concatenates unvalidated schema and table names into the SQL query string.
classes/DB/EtlJournalHelper.php does not exist, and git history does not show it ever existed. https://github.com/ubccr/xdmod/commits/main/classes/DB
> Vulnerable Code Analysis (spryker-shop/b2c-demo-shop): In the default configuration file config/Shared/config_default.php, the vulnerability stems from hardcoded OAuth client credentials where the secret is set to null, effectively making it an unprotected public client.
config/Shared/config_default.php is a real file, but the code snippet is fake. It doesn't look anything like the real code. https://github.com/spryker-shop/b2c-demo-shop/blame/master/c...
This AI slop falsely claiming that several innocent projects have critical vulnerabilities feels like it's bordering on defamation. If I was a project admin I would consider sending the lawyers in.
> Six months ago, I was running a customer support chatbot for a SaaS product. Nothing fancy - ...
I'm sure this toooootally happened
> curl -X POST https://tokensaver.org/api/chat \ -H "Content-Type: application/json" \ -d '{ "email": "your@email.com", "messages": [ {"role": "user", "content": "Hello!"} ] }'
Am I getting this right that there's no auth? Just provide an email and get free requests?
Edit:
This seems to always use sonnet 3.5 no matter the request. I asked it a USAMO problem and it still used sonnet (and hallucinated the wrong answer of course).
Additionally, even though they're not fully reliable, most popular AI detectors rate this article as 100% human.
You can see this author has been writing similar low-effort listicles and articles since well before ChatGPT came out. The writing style also matches:
https://web.archive.org/web/20200811132340/https://appuals.c...
https://web.archive.org/web/20221021195546/https://www.wepc....
> 1. Downgraded Xfinity from $90/mo to a basic $50/mo plan (still usable speeds, just lower tier)
> 2. Added AT&T Fiber as a second line at $55/mo (different infrastructure = different failure modes)
> 3. Bonded both connections using WireGuard VPN and OpenWRT routing
Edit:
Another lie detected: ATT isn't accepting new customers on DSL, and is in fact yanking service for existing customers in many areas. So there's zero chance that OP signed up for ATT copper internet within the last year or so.
I'm sure it's also a waste of maintainers time to drop a wall of AI bullet points instead of just sharing the critical information.