jedahan

framework 13 pro might fit this. Saying from someone who just migrated from m4 macbook pro 14.

I wish tap trust operated at the author/committer level than identifier level.

Its very personal and situation dependent, but I truly believe that if you work at Amazon or Facebook and do not want to support this, you can.

This is the kind of rationalization I am referring to.

Not sure if you meant to reply here?

Reminder if you work for any of these companies (not unlikely on this site) you are actively enabling this. If your first reaction is doubt, deflection, rationalization or discomfort, there are ways out.

That network is shared with police departments in cities outside Seattle per the article.

Code is a liability - the more there is, the higher potential for bugs and poor performance. I'd recommend treating cheap code like cheap toxic waste, and try to minimize how much is generated.

No need for the extra tap step, this works fine alone:

    brew install Arthur-Ficial/tap/apfel

They certainly have more choices than implementing in this manner, and can choose to not implement it as well.

Absolving Apple of responsibility gives more than they deserve.

great for astral, sucks for uv. was nice to have sane tooling at least for a few years, thanks for the gift.

I prefer low effort human thought to low effort llm output.

Making home read-only can get there, and I can't find the project that forced using XDG paths. I think it used LD_PRELOAD or somesuch trick.

edit: https://soc.me/standards/defending-home

I do the same for years and had no idea that disabled emails are blocked, is that documented anywhere? Will have to switch if so.

When I tested all the p2p messengers I could get my hands on for Android and iOS about two years back, the only one that worked at all without having a router around was Briar. Glad to see it helping people.

I was wondering the same thing. My best guess is that is to guard against operator misuse. Like usb-a only plugging in one way. Anything that is secret will never accidentally print to stdout. String interpolation in bash with `—option $empty` might be safer than `8<$empty`. Have to explore more but yeah, this is a new pattern for me as well.

:(

I am describing what I see on Element X on iOS today. If someone replies to threads, it is not hidden and navigable on this client. Even after switching the labs feature on, the app was showing the thread interspersed with the rest of the conversation.

Uninstalling the app, reinstalling, and making sure the labs option is turned on before navigating to a room with threads, is behaving how I expect.

So maybe, its a bug that the room does not re-render after toggling that setting.

I felt bad making a long thread once I opened Element X and saw it didn't have support for threads.

Someone let me know later that threads are hidden behind a Labs setting, but it only allows the client to reply to threads, but still exposes the entire thread inline for the channel which sucks up all the air in the chat.

Pre-launch I seem to recall using an entirely different product with the same name, that supported CUE or HCL and had a better gui editor. I think post acquisition they scrapped it for the current (and IMO) worse reskin.

Good question - I am just putting up robots.txt, and seeing little to no decrease in traffic. I have not tried verifying that server logs user agent corresponds to specific IP addresses. Do you have resources where all the AI bots post their list of IP addresses? Would be easier to just ban by IP completely. From what I've read these bots rotate and use residential blocks so I am not sure I can even see all of them.

My experience disagrees with the 'Respects robots.txt' column for most of the bots listed. Would love to see more details of how they determine that metric.

I am having trouble imagining the failure mode you are trying to avoid.

It sounds like threads implementation of federation is broken. What effects does toggling that federation setting on or off do?

Like if someone is following “duplicate” accounts of yours and therefore would see double posts, that person can unfollow one. Still double work for you that kind of sucks.

Scuttlebutt had some work done on publicly declaring two identities as the same, I wonder what that would look like for posts. Like a post-id or simple equality comparison or hash could work server side or client side.

I wish the coating lasted longer, I had to throw some tape on mine to keep using it - the rubber keeps wearing down.

Helps the maintainer focus their efforts during review. If you wrote that exact sentence, a maintainer would keep "understanding of the codebase" as a place for potential sources of incorrect assumptions higher in mind than otherwise.

Run a community space that uses its own SSO, and needs to share passwords for socials and the like.

Been using this since it was merged. No issues so far, appreciate the work.

Love the relaxation of git-specific guardrails to make jj workflows better.

Not sure why, but this reads as an AI generated summary. Can someone confirm/explain? What does it mean to create new cybersecurity?

I wonder if it respects prefers-reduced-motion, though I don't know if I have that set in my browser, I do have it set with my OS.