The word "additionally" evading guardrails is comical.
You need structural separation. Separate agents for public vs private. Prompt or context washing is not enough.
The word "additionally" evading guardrails is comical.
You need structural separation. Separate agents for public vs private. Prompt or context washing is not enough.
Stuff like (in-site) header color or labels can also help significantly.
I guess I don't have many hosted side projects. Those I do, I don't put them on separate domains. I doubt people use or care, so I haven't added monitoring for individual projects specifically. I guess I could and should do that now that I established my own online monitoring without third-party free tier limitations.
I use Red Sift (free) for certificate monitoring, since Let's Encrypt dropped expiry warning notifications. Given it's automated, it's never been an issue for my self-managed projects, though.
For is-online/is-reachable monitoring, after free services I used became more restricted, and none matched my simple needs, I created Meercat Monitor, which runs on my server and checks some of my and work related projects/services. Simple checks scheduled checks, email notification, and a simple history and status view. Something simple enough and open source so I can audit and manage sources.
I forgot to add the description and chapters. I added them now.
They go over how the web and frameworks decided against horizontal, apart from deliberate emphasis, they go over some desktop layout attempts, failures and successes (more of the same vs navigation), a chapter about (paper) documents as the source, and endless panes now using horizontal.
You can edit titles here on Lemmy. You can fix the title.
I second that monitor setup is a personal preference. Personally, I prefer alt+tabbing (repeatedly) over using multiple monitors. No need to rotate my head, to seek with my eyes. My colleagues seem to prefer using multiple monitors. One colleague has an ultra-wide. For me. a single 1440p is best.
What makes you think it's a lockfile issue? If they sighted a patch upgrade then updated the lockfiles but then noticed a breaking change, then lockfiles are irrelevant.
If it's actually like they claim, I understand the frustration. (Not that I know this project in particular or how it gets integrated.) Without clear versioning and/or changelogs/release notes managing upgrades is cumbersome, sometimes impossible.
In some cases I've had to ask for clarification in PRs because release notes were not clear, PR was not clear, and resolved ticket was also not clear on the thing or solution.
Apparently they had issues before, so maybe they could have expected "patch may not be patch-only".
I don't think there's a particular need to defuse into a productive discussion. Something like that, with no repro or respect - lock and close, with a comment on why/that onproductive and disrespectful/what it could have been.
Tone should always be respectful. Something like this should have been a respectful, open suggestion, explaining the issues no clear semver causes.
If they don't respond to your needs - you can accept it or leave/fork.
The first version included a 'Fuck you' but they edited it away.
I hope this isn't considered a "meme" by the rules. Kinda depends on the definition - which the rules has none of.
:squint: :P
Depends on the spec/implementation. If it's random generated tokens then I imagine they're not [necessarily] one per user. You could generate an arbitrary number and get new ones arbitrarily, regularly.
Without some technical information, with only this press release, we can't tell.