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.
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 have an ancient laptop from 2008 with 4GB of ram that runs a modern KDE desktop
Try Alpine Linux, with Xfce which can do most of the same things. Then enable swap compression -- add this to the end of the kernel line in your bootloader:
zswap.enabled=1
This compresses everything going to swap, and decompresses it coming back: less disk reads and writes, and less space used.
4GB still seems excessive, by at least one and probably several orders of magnitude, for what vanilla KDE actually does: browse files, manage windows, and edit text. And KDE is one of the best modern options.
> 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?
Yeah, it's one of the reasons I use a Microsoft account to collect the PC entitlements and then create a local user account that has a sane profile name and never touch the online account again.
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.
Many/all? also need to have some form of manual input as a backup, so you're not forced to sync all your passwords to e.g. a library's computer just to log in, if your house burns down or something.
(1) is already true today. There is no way for services to enforce whether a passkey is stored in software or hardware.
(2) I understand you don't like the user experience. But to make a technical clarification: requiring a user action to prove there's a human involved in the login action (e.g. by clicking a button in UI or requiring Touch ID) does not necessarily mean there's another factor involved at all (MFA). What you are describing is more of a "liveness check" than a separate factor/separate credential.
(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 personally believe that many of these "influencers" do not believe any of the stuff they spew into the public space.
reply