HN user

alyandon

2,626 karma

Please consider adding to the discussion by replying instead of only upvoting/downvoting.

Email: my hacker news username at hotmail.com

Posts0
Comments681
View on HN
No posts found.

Yeah, once Google has ripped all the MV2 code out of chromium it'll be very interesting to see how long the chromium reskins are able to maintain their private forks.

I also expect Google to be a bad actor and do everything in its power to pointlessly refactor the chromium codebase specifically to make keeping MV2 alive as painful as possible.

I stick with LTS releases so last honest attempt would have been on a Kubuntu 24.04 LTS system.

What is a compositor - thing that actually draws window content on the screen? Whatever KDE provides?

Edit: To be fair to KDE/Wayland, the Wayland Kubuntu 24.04 experience was vastly improved over Kubuntu 22.04.

I empathize but every time I try a Wayland based desktop I always end up encountering weird bugs and corner cases with basic usability that drive me back to X11.

I'll be sad if that is still the case when 6.8 rolls around as then I'll be hunting for another DE.

I'm pretty much neutral on the whole LLM thing as it has positives and negatives just like most other technologies. If their declaration had been scoped to "don't use LLMs and automated tooling to submit PRs for our packaging workflows and processes" that would have been fine.

Instead they go well beyond that and include this:

  * Applications containing AI-generated or AI-assisted code, documentation, or other content are not allowed.
So yeah, that's pretty much hysteria at this point. It's their project and their infrastructure though so they get to set the rules - I'm just going to shrug my shoulders and continue to not use flatpaks.

Same here but I'm using a ssh based proxy to avoid having my local ISP data mine my web traffic. Definitely not going to turn it off either to read a blog.

I really wish admins banned based on actual behavior instead of IP address != residential/mobile.

Old versions of Netscape Navigator had settings where you could tweak that kind of stuff - I don't recall if IE3/4 did or not.

Given the web of the 90s didn't include tons of overly complex javascript most of the settings were targeted at how much ram/disk was used for caching website assets IIRC.

It's the principle of the thing though - we should have the ability to set resource allocation limits instead of potentially handing our entire computer's resources to a random website just because we clicked on a URL.

Back in the ancient days of the web, browsers allowed you to set resource limits (ram, cache, etc) to prevent websites from hogging the limited resources of your desktop system.

It's really a shame that all major browsers have since decided that you as a user should have almost no control over how much ram and storage any arbitrary website can consume now.

It seems that AI-scraping hysteria/paranoia has reached a point that more and more resource sites completely block me without any recourse (e.g. having an account) if my traffic is coming from a datacenter IP. I really wish sites blocked agents/IPs based on actual bad behavior instead of reflexively blocking by IP != residential/mobile.

I do understand the frustration though. I've had to deal with bad bots scraping every crevice of a few web based services I host and while most went away after I tweaked robots.txt there were a few I've had to blanket ban IPs assigned to entire ASNs because the bots on their networks refused to play nice.

Zulip.com Values 5 months ago
  It instead is a chat where a thousand group chats are open, and no once wants to read any of them.
I really wanted to like Zulip and use it as a personal chat service for a small group and it was exactly that feature that made it basically unsuitable. Forcing everything into titled threads did not make any sense for lots of user to user interactions that are ad-hoc in nature.

I didn't think it was terrible software by any stretch of the imagination - just not really suitable for informal communication.

It does seem like a lot of doctors prescribe GLP-1s without any corresponding education on the dietary changes one should make while on them. A friend of mine's mother was hospitalized briefly because she was basically starving herself of proper nutrition while on GLP-1s.

Since I already knew that rapid weight loss is very unhealthy, I intentionally eat very nutrient dense foods in order to keep my weight loss in a reasonable range.

Another N=1, I've noticed zero impact on my desire to engage in my normal obsessions while on GLP-1.

What GLP-1 did (initially) was give me horrible insomnia that peaked a couple of days after taking the injection so I had to time my dosage so that I suffered through that on the weekend. That got better over time and eventually went away after about 6 weeks.

Regardless, as another poster mentioned, it's a weekly injection and if you don't like the effects you can stop taking it.

Exactly - the FTDI drivers refusing to work would have been reasonable and emitting a log or error message that my device was counterfeit would have actually been helpful. Instead, they vandalized end user equipment by permanently bricking the devices which is arguably illegal.

I am not nearly sophisticated enough as an end user to spot a counterfeit FTDI usb-to-serial device so I am not going to risk buying that brand and end up with their drivers intentionally bricking the device.

KDE doesn't need 4 GB of ram - that's just what my laptop happens to have which is more than ample to run the OS + KDE + native applications.

It's the web browser and electron based apps that are the primary consumers of ram on my desktops with the DE and OS ram usage being minimal by comparison.

I have an ancient laptop from 2008 with 4GB of ram that runs a modern KDE desktop and related applications just fine that I use for troubleshooting stuff. However, the moment I open a web browser it basically falls to pieces.

I hate everything about this. :-/

  https://antonz.org/go-1-26/#httptest-example
> To fix this issue, the HTTP client returned by httptest.Server.Client now redirects requests for example.com and its subdomains to the test server

I'm really conflicted about the idea that the https client should silently hijack requests to example.com in order to make a dummy certificate work... or am I just really misunderstanding?

  (1) is already true today. There is no way for services to enforce whether a passkey is stored in software or hardware.
Challenge: Go and try to register a non-blessed passkey type with PayPal and come back and share your experience.
  (2) I understand you don't like the user experience
Pretty much my complaint. Passkeys allow for service providers to do dumb things that result in terrible UX. With Password + TOTP, I don't get asked to touch a sensor, enter a PIN, enter an unlock password, etc.

I'm a bit of a curmudgeon about this.

Until service providers are no longer allowed to:

  1) force the type of passkey stores used (e.g. hardware vs software) when I am providing the passkey store
  2) force me to MFA (e.g. forcing touch ID, entering pin or unlock password, etc) when attempting to use a passkey
I'll continue to stick to plain old boring password + TOTP. I fully understand the security trade-offs like phishing resistance but password + TOTP is secure enough for me.

I had put it off for several years because everyone kept telling me how awful the prep was. My doctor kept pestering me to agree to do it so I eventually relented.

Turns out, I needed to go to the bathroom frequently during the day which was an annoyance but I never had anything close to an "accident" nor did I feel any strong urge to evacuate at night. So the whole experience turned out to be a huge nothing-burger and I had a few polyps that got sniped that weren't cancerous - so now I have peace of mind that I didn't have before.

  They say there’s no Emacs — only your Emacs.
This hit home for me. I spent about 6 months working exclusively with emacs to get past the "this is weird/hard because it is unfamiliar to me" stage. At the end of the experiment, I went back to using vim and IDEs.

My take personal takeaways from the experience:

1) capslock/ctrl switching is helpful in so many other areas - so I kept that

2) emacs is something you want to "live in" (e.g. learning to rely on eshell) if you want to really become proficient with it

3) emacs is something you have to be willing to tweak/adjust via elisp to suite your personal preferences if you want to really really really be proficient with it

I didn't hate emacs but it also wasn't for me.