pluto_modadic

wind, boats, whales, current interference/interfaces, cthlulu rolling over...

glad to see more features!

sounds like some peeps could contribute code to fix wayland / compositors to enable talon's accessibility hooks :D

"found out right away"... by people with time to review security bulletins. There's loads of places I could see this slipping through the cracks for months.

Package managers are constraint solvers. You could manually figure out if XYZ shared library works with somebody else's code, or, you could expect that they would label the range of shared library versions their code needs.

Note to self... don't use Odin.

I think Micah misses the mark here. ICEBlock has vulns, yes, but this was inappropriate.

I've known users to type passwords in the username field. you implicitly do NOT know all secrets (e.g., a password is hashed).

secrets can also churn, so even if you did your example would require something besides an in-memory array.

and, the final point: what if your secret masking code fails on an exception, too ;)

PII is different from proprietary info. customer's email? PII. mask it. your code's stack trace? proprietary info. employees can see that to troubleshoot.

you disobeyed a code of conduct? that's not a good look.

things were on the backlog, but more important things absolutely needed to be done.

I think they do a good job with test coverage, compatibility, and sustainable support. Can't say that about most every other hype database made by a fortune 500 and shut down 3 years later.

if you drive down the road and decide on a whim to pull into a restaraunt, you shouldn't be looking down at your phone as you order. fast food is for impulse purchases.

a LARGE amount of /drive through specific/ food purchases are impulse purchases /as they're driving down the road/. You /don't/ want someone using an app to do that. It misses the mark of what actual customers are doing in favor of "let's do a cool thing because smartphones/AI exist".

This reminds me that in protocol buffers you can deprecate and extend field names in a backwards compatible way and it's handled semi-sensibly. At the very least, it makes you think about schema migration (of HTTP fields in this case. DB fields and class fields are different...). If you aren't using practices that make e.g. adding another enum option to state sensible (e.g. in a language or linter that requires passing interface checks, class X must provide method Y)

my initial gut take from the title was "OH MY GOODNESS don't let {x} toxic developer who writes TERRIBLE code see this as justification". There are enough toxic bros who either 1. think this is unnecessary or 2. think it is perfectly solved.

re: intermediate representation and projectional editing: yes, editors are now getting better at helping you refactor code (rename function in language XYZ is possible in language servers for IDEs, /no AI required, it works better when a human coded AST tool does it/)

projectional editors aren't around /because the more complex parts of it are harder/ - BUT - I could definitely see more intelligent refactor tooltips written by humans.

For example: in Rust, if I've been passing a pointer vs borrowing (or whatever), pattern A for most of my code, then pattern B and it complains, it would be useful to have a tooltip that goes "do you want to refactor all the other references/parameters to pattern B" instead of Rust's default "this function isn't using pattern A" borrow checker error.

reading this as a security engineer trying to get ahead of misguided PMs who buy into the AI hype and don't know 1) it's immature 2) it's not secure & 3) whether their business use case is viable for the R&D we're about to put into it.

I get the feeling there's going to be either 1) a great revert of the features, 2) a bunch of hurried patches, or 3) a bunch of legacy systems operating on MCP v0.00-beta (metaphorically speaking)

:lol_sob:

India's payment network is a good case study. The US is /not/, because US banks are lazy.

I think it shouldn't require registering /with/ cloudflare. cloudflare should just look up the .well-known referenced and double check for impersonation, and keep score on how well behaved each one is.

muahahahaha, muahahaha!

galactic source != aliens, astrophysical origin != aliens.

Ghibli images are not "cows", they're /an artists style/, and a particular shop that has expressly asked that you *not copy their work*, because it cheapens what humans do.

lots of people not considering UNPHAT - https://gist.github.com/rponte/67c78e6b3ee349a6e14cb8fb155b7... / https://stevenschwenke.de/pragmaticSoftwareEngineeringUNPHAT - some solutions didn't exist in the past. you evaluate your landscape and your problem, and try to find a good fit.

it's true, wordpress is self contained - it does bundle in a lot of overhead (database, php) - but it has a good story for quickly getting a presentable site. Static sites require learning about template engines, git (possibly), FTP...

"I don't need a curb cut or a seatbelt, so I won't benefit from society having them" ( https://en.wikipedia.org/wiki/Curb_cut_effect )

a datacenter getting "priority" over potable water to feed the data farms instead of, say, requiring "humans first, datacenter if there's any left"

then you get into makefile escape hell (similar to yaml hell)

AI agents have been known to rip out mocks so that the tests pass.

what is a server browser? is it like how on disboard you can find discord groups?

yeah, cheaper to just denylist that username and remove the storage.

managers who don't understand the technicalities of what their engineers are doing only need a status update or strategy to /sound/ smart: they judge by smell. everything under the surface veneer is bullshit.

it's smart mobile text prediction. nothing more. slop is if you asked it to write the same, identical essay, and it came out with no personality, just the same bullet points, the same voicing... everything unique about the creator, everything correct about the profession, are lost. it's a cheap mcdonalds burger.