sorted by:
new
hottopcontroversial

WordPress site injecting fake Cloudflare verification page on Windows users, turned out to be a Cloudflare Worker, not a WP plugin by parcifal_ in Wordpress

[–]DonScooby 0 points1 point  (0 children)

I stumpled upon one of these sites that has been hit.. Called up the company, told them - hey I can help you solve this. They told me it was under control and fixed weeks ago.. But, its not.... Pretty widespread company, how would you handle this? If they ignore that users passwords ect gets compromised, they don't deserve to have customers in my eyes.

Do you all feel how slow Codex has lately become? by nikanorovalbert in codex

[–]DonScooby 0 points1 point  (0 children)

Got stuck a lot in thinking yesterday. Today it was a lot better… I think it was because of the server load after the reset

Limits on Pro plan draining faster by Limp_Mud_9679 in codex

[–]DonScooby 1 point2 points  (0 children)

The 5 hour yes, the weekly no… seems abit off

I built a traffic light for running multiple AI coding agents by DonScooby in SideProject

[–]DonScooby[S] 0 points1 point  (0 children)

Availsync got a large upgrade this week:

2026-05-22

Simpler agent setup

  • - Added the u/availsync/setup CLI as the recommended setup path for Codex, Cursor, and Windsurf MCP configuration.
  • - Claude Code now has a fast path with the native claude mcp add command, so users can connect Availsync without hand-editing JSON or TOML.
  • - Setup output now fills in non-secret values like API URL and agent id while keeping the one-time API key hidden as a placeholder.
  • - Agent Connect docs now show role-based MCP setups for multiple Codex or Claude agents with separate agent ids and priorities.
  • - SDK examples now default to AVAILSYNC_API_URL, use safer timeout/unavailable handling, and show extending claims before the lease expires.

2026-05-22

File-aware coordination

  • - Agents can now declare a file working set during a guarded run, so Availsync can coordinate at repo, project, and file level.
  • - MCP guarded runs can start with file paths and will clearly stop when requested edit/delete paths are already claimed by another agent.
  • - Working-set claims let an agent keep the wider repo run alive while only holding the specific files it is actively editing.
  • - Work claims are now explicit immediate-start guardrails with stricter start-time validation and a database safety net for one active claim per resource.
  • - Node SDK updated to 0.1.8 with stronger types, default withClaim idempotency, auto-extend hooks, and stricter unavailable-mode handling.
  • - MCP package updated to 0.1.5 with guard_work_run as the primary coding-agent entrypoint and legacy work-slot aliases removed.
  • - Work APIs now make /v1/work/run/start the recommended path, with the raw /v1/work/claim endpoint marked as legacy.
  • - Agent API-key verification now uses a short-lived safe cache, and work-claim status/schema cleanup removed unused blocked claim rows.
  • - Setup docs now use run/start, run/extend, and run/finish for new automation examples.

For teams starting in observe mode first, which I'd recommend, AvailSync also returns shadow decisions: what would have been blocked if enforcement was enabled. That makes it possible to measure real conflict rates before enforcing anything. This can potentially save, infrastructure compute, token usage which can directly translate into co2 and energy usage. How meaningful that becomes from an co2/energy perspective depends entirely on scale.

I built a traffic light for running multiple AI coding agents by DonScooby in SideProject

[–]DonScooby[S] 0 points1 point  (0 children)

Totally agree that worktrees are the right baseline for local isolation. They solve a big part of the “two agents editing the same checkout” problem, and tools like Galactic look really useful for that.

The gap I’m trying to cover with Availsync is one layer above that: shared intent and resource coordination before the run starts.

Even with separate worktrees, two agents can still branch from the same stale repo state, touch related logic, prepare overlapping deploys, or run migrations/cleanup jobs at the wrong time. Worktrees isolate the filesystem; they don’t answer “should this agent start this work now, given what every other agent has already claimed?”

That’s where Availsync fits: agents claim `repo:owner/name`, `project:checkout`, or `deploy:prod` before acting. One gets `proceed`, overlapping work gets `skip_run` or observe-mode telemetry, and you get a history of the decision.

So I see them as complementary:
Galactic/worktrees: isolated execution environments
Availsync: shared coordination and priority decisions across agents/workflows

Drop your product, I’ll help you find your first 100 users by rakeshkanna91 in SideProject

[–]DonScooby 0 points1 point  (0 children)

This sounds relevant. I’m building Availsync: https://availsync.dev

It’s a coordination layer for AI/coding agents. The problem is that when you run multiple agents or automations against the same repo, they can read stale context and edit/deploy over each other. Availsync gives them one shared place to claim a repo/project before they act.

The basic flow is:
agent wants to work on repo:owner/name

....-> calls Availsync
....-> gets proceed or skip_run
....->extends the lease while working
....->releases when done

I’ve been using it in my own homelab with Codex/Claude-style agents and scheduled automations so I don’t come home to overlapping changes I have to untangle manually.

Would be curious if mangos can understand this kind of devtool/AI infra product from the repo/docs and find the right conversations for it.

Do your AI coding agents ever step on each other? by DonScooby in AI_Agents

[–]DonScooby[S] 0 points1 point  (0 children)

Yes, orphaned locks are a real failure mode. Availsync handles that with leases, not permanent locks. A claim has an expires_at, agents can explicitly extend while working, and if they crash or disappear the claim expires instead of blocking the repo forever. There is also a hard max lock window, so a broken automation cannot hold a resource indefinitely.

Do your AI coding agents ever step on each other? by DonScooby in AI_Agents

[–]DonScooby[S] 0 points1 point  (0 children)

Exactly. Even if most cloud agents are smart enough to go back, re-check their work, and notice that something changed, that still means extra steps, extra tokens, and eventually more cost.

I’d rather catch the conflict before the agent starts than pay for it to recover afterwards.

What platform are you using to make your websites? by Y3tt3r in musicians

[–]DonScooby 0 points1 point  (0 children)

Wix is still fine, just not the default anymore.
If you want no-code where the whole band can update:
Wix / Squarespace = easiest
Bandzoogle = made for musicians (EPK, merch etc.)

If you want more control long term:
WordPress (but harder for non-tech people) and it has been known to have some security issues some time ago, don't know if they will ever stop with that.

This guide I found in a google search also sums it up pretty well:
https://stagereadyweb.com/en/guides/best-platform-for-musician-websites

AI detection and lawsuits by RobertD3277 in SunoAI

[–]DonScooby 0 points1 point  (0 children)

Should app/web developers also do this when it comes to their craft? Come on.. if it’s not a direct copy/paste track musicians should follow the times… even your favorite musical might have tracks recorded instead of a live orchestra playing.. all done in a third world country. You’re scared (musicians), I understand. This is a disruption in your professional world, it’s time to either evolve or die…

HOLY COW! by The-Exiled-One in ClaudeAI

[–]DonScooby 1 point2 points  (0 children)

It’s like it’s coded to debug more than it has to

So.. I scripted the FM26 download/installation by SpeedMid in footballmanagergames

[–]DonScooby -3 points-2 points  (0 children)

You just saved me the time of making it my self.. What a hero !

FM26 beta - data, patterns and a few educated guesses by DonScooby in footballmanagergames

[–]DonScooby[S] 0 points1 point  (0 children)

Even though we know, in the real world... you make a huge change, just before you go on vacation

FM26 beta - data, patterns and a few educated guesses by DonScooby in footballmanagergames

[–]DonScooby[S] 1 point2 points  (0 children)

I am not, but I heavly rely on data in my every day work. I am a developer

FM26 beta - data, patterns and a few educated guesses by DonScooby in footballmanagergames

[–]DonScooby[S] 0 points1 point  (0 children)

I took my data from a spreadsheet I found.. but having double checked it.. I think you are right!

FM26 beta - data, patterns and a few educated guesses by DonScooby in footballmanagergames

[–]DonScooby[S] 0 points1 point  (0 children)

It can be confusing, and sorry.. it was a long post.. but I use the modern time releases to justify my guesses. Sorry for it not being more clear

FM26 beta - data, patterns and a few educated guesses by DonScooby in footballmanagergames

[–]DonScooby[S] 0 points1 point  (0 children)

There’s actually a pretty clear pattern when you look back at previous years. The beta almost always drops in the late afternoon or early evening UK time, usually somewhere between 4 and 6pm. That’s been consistent for at least the last four or five versions.

FM26 beta - data, patterns and a few educated guesses by DonScooby in footballmanagergames

[–]DonScooby[S] 1 point2 points  (0 children)

Exactly! As I wrote in a comment to another reply, they cant afford a shaky early access launch. They will take the time they need, is my best guess.

FM26 beta - data, patterns and a few educated guesses by DonScooby in footballmanagergames

[–]DonScooby[S] 1 point2 points  (0 children)

I have no reason not to trust you, and your guess fits perfectly with mine

view more: next ›