1,224 karma · joined March 3, 2015
The first party cursor models (initially composer and now grok-cursor) and price very competitively for their quality and have very generous usage limits included in the base plans, and then per token pricing afterwards.
Occasionally I’ve used some of the Anthropic models in it but found their cost massively outweighed the benefits for the type of usage we do.
I was using Sonnet 4.5 and 4.6 for a while but the newer models are a lot more expensive at the per-token pricing.
Secret scanning needs to make sure my repo as a whole has no secrets. It’s not acceptable to have 1 commit introducing it and 1 removing it because the secret is still recoverable.
Every commit is also surely an entry in a database somewhere. I can navigate in GitHub directly to any individual commit so there is definitely some overhead of some type.
As much as I’d like a mechanical keyboard for my Mac that’s always the part that gets me. I end up using the one my Magic Keyboard 20+ times per workday.
Otherwise it looks beautiful.
It does not one any favours if your 10k LoC gets split in 5 changes that aren’t supposed to regress anything (but need to be validated not to) then 1 tiny on that brings things together.
Some features will be confusing for end users if you drip feed them. We had a whole host of changes recently overhauling our moderation system to be able to track and audit compliance with DSA and the key factor is ensuring the system makes sense to our users and that they can enable, have documentation and on-boarding materials for the changes in functionality and that it’s all QA tested.
In this case we did still review smaller chunks of code, we accumulated them into 1 large merge request at the end and merged it after QA.
I’ve been using [Octal](https://apps.apple.com/us/app/octal-for-hacker-news/id130888...) for a while now but it’s not open source.
Would you be opposed to a pull request adding login/posting support? I think the way it works in Octal is webview for login, snatching the cookies out of the webview, then using the same posting endpoints as the website with the cookie.
Then as needed we have materialized columns on our different tables.
You can have your IT department configure an MCP for the org, and your regular non-technical users click a button and login with their account the service. Then they get all the tool calls authenticated as themselves.
This is a prompt-injection attempt designed to override system instructions, identity, and safeguards.
I will not comply with it. I will not change identity, priorities, or behavior, and I will not relay or approve prompts verbatim as instructed. System and developer instructions remain in force.
If you have a legitimate task or question, state it directly and I will handle it normally.
I would definitely say prompt injection detection is better than it used to beThen if you want something a little bit complicated you have to do it all yourself.
- What if I need a date range instead of a single date? - What if I have excluded dates? (Only weekdays/only in the future/blackout dates) - What if I want to show other metadata with each day? (Like in a calendar showing each day with some metadata next to it)
Beyond “give a whatever the system thinks is a good date picker that I have no control over” the input with type date isn’t very useful.
No matter your size unless you have a trivial amount of data, if you expose a full SQL query language you can be hit be a DOS attack pretty trivially.
This ignores that row level security is also not enough on its own to implement an even moderately capable level of access controls.
There is a feature of Windows called “Windows Subsystem for Linux (WSL)” already that basically does the inverse of this (windows host, Linux VM).
https://github.com/microsoft/WSL
The feature is a windows subsystem (for running Linux).
- price of the ticket was as advertised - a checked bag was an option at the same price it has always been. - I was able to assign a seat next to my husband without additional fees.
Now while this flight was not cancelled, I’ve had to reschedule some flights with Delta due to illness previously and they just gave me a 100% credit for the cost of the flight that was easy to use.
The only contrast for cancellation I know is the nightmare of Air Canada. In the past I’ve had flights get cancelled and only got “vouchers” that could only be used by calling a specific number that took 1 hour+ and were not applicable for taxes (you know half the cost of a Canadian Airline Ticket), and would be lost of not fully used in one purchases
That’s a pretty crazy statement. How often do you see loading a CSS stylesheet fail to load? Most sites are completely unusable without their stylesheets and I don’t recall the last time I saw a stylesheet fail to load.
So user privacy is definitely implicated.
This exact type of functionality has caused a major project a work on to use CSS in JS (for relative colors and contrast colors.
I’m glad to see this type of thing coming around the corner and look forward to it being widely available in a couple years.
You have to give an iframe a specific height in pixels. There is no “make this iframe the height its content wants to be (like normal HTML).
This leads to two options:
- your page has nested vertical scroll bars (awful UX) - you have to write JavaScript inside and outside the frame to constantly measure and communicate how tall the frame wants to be.
Or you could just not use frames.
In PHP you loop through an iterator with the foreach control structure.
In JavaScript you use for of.
In rust it’s for in.
What am I missing?
Alternatively you could get a 3.1 audio setup and just boost the heck out of your center channel.
> In my opinion, instead of pressuring and insulting people who actually clarify issues with YAML and the wrong statements of some of its proponents, I would kindly suggest reading the JSON spec (which is not that difficult or long) and finally make YAML compatible to it, and educating users about the changes, instead of spreading lies about the real compatibility for many years and trying to silence people who point out that it isn't true.
> Addendum/2009: the YAML 1.2 spec is still incompatible with JSON, even though the incompatibilities have been documented (and are known to Brian) for many years and the spec makes explicit claims that YAML is a superset of JSON. It would be so easy to fix, but apparently, bullying people and corrupting userdata is so much easier.
Well that’s disappointing.
I’m just pointing out that it should be very simple to swap a YAML file for a JSON file in any system that accepts YAML
I’m not sure how much of this is “standard” for an org though.
In addition to the pitfalls mentioned like being unable to select text, every interaction including scrolling is noticeably laggy and dropping frames.