oger

However for starters I would stick with the more well known sources directly from Qwen or from reputable players like Unsloth:

https://huggingface.co/Qwen/Qwen3.8-27B

https://huggingface.co/unsloth/Qwen3.8-27B-GGUF

This is even more profound than Karpathy‘s approach to storing and retrieving knowledge - and certainly one of the most inspiring blog posts / papers I have read this year.

And you can think of extending this approach to domains like sales and marketing.

This is probably the most convincing use case for OpenClaw and Hermes.

But: as you are opening your heart and brain to LLMs it raises the question if local inference might be the best approach.

While I see the point of limited capacity, it also shows that Google did not plan for rate limiting / throttling of high usage customers. This is ALWAYS the problem with flatrate pricing models. 2% of your customers burn 80+% of your capacity. Did see that in former times with DSL, not too long ago with mobile and now with AI subscriptions. If you want to provide a "good" service for all customers better implement (and not only write in your T&Cs) a fair usage model which (fairly) penalises heavy users.

Good on them that they want to provide a way to bring back customers on board that were burned / surprised by their move.

BUT: The industry is missing a significant long term revenue opportunity here. There obviously is latent demand and Claws have a great product market fit. Why on earth would you deactivate customers that show high usage? Inform them that you have another product (API keys) for them and maybe threaten with throttling. But don't throw them overboard! Find a solution that makes commercial sense for both sides (security from API bill shock for the customer / predictable token usage for the provider).

What we're seeing right now is the complete opposite. Ban customers that might even rely on their account. Feels like the accountants have won this round - but did not expect the PR backlash and possible Streisand effect...

Both Google and Anthropic are choosing the wrong route here. While I see the formal aspect of abusing an OAuth token and burning through subsidized tokens, this only creates an internal accounting problem in the short term.

Meanwhile the rising popularity of Claws creates a yet untapped new market segment where users spend significant tokens.

A „soft“ migration of users by explaining to them how the API works, how to pay and how to change from OAuth would be way smarter.

The way this plays out right now is that current Claws users are massively penalized by being suspended indefinitely and new users will think twice. And we can expect a solid PR disaster / Streisand effect for the „poor“ model providers like OpenAI or Anthropic.

Commercially choosing the soft route by warning and throttling will be way smarter and possibly generate more long term revenue

So here goes my OpenClaw integration with Anthropic via OAuth… While I see their business risk I also see the onboarding path for new paying customers. I just upgraded to Max and would even consider the API if cost were controllable. I hope that Anthropic finds a smart way to communicate with customers in a constructive way and offers advice for the not so skilled OpenClaw homelabbers instead of terminating their accounts… Is anybody here from Anthropic that could pick up that message before a PR nightmare happens?

Aperture is dearly missed even today. And to make matters worse: you cannot even import Aperture libraries into Photos any more. Essentially leaving you with picking out the raw images from the package. And don’t get me started on excellent support for tethered shooting in a studio setting. And I could go on and on. The only thing I really missed in Aperture was first level support for Nik tools which are cool for their adaptive and non destructive masks.

Sigrok was offline for a couple of days but seems to be back online.

While researching the outage (which seemingly was caused by AI scrapers hitting the site hard) I learned that interesting discussions about the future direction of the project are happening on the mailing list

https://sourceforge.net/p/sigrok/mailman/message/59249346/

It seems PayPal is having issues with their login according to downdetector.com . Multiple reports on X with similar issues: Login problems, Captcha loops ad infinitum.

Issues seem to start around 15:00 GMT

The topic of per-country pricing was mentioned several times.

I was wondering how big the price differences would be so I set up a quick form to collect some data points from several countries and for several products.

It would be cool if you could provide some data - I would then share it back as a reply to this thread within 1-2 days after closing the survey. The latest data entry will be possible on Sunday.

https://forms.cloud.microsoft/e/DjDgH62s21

I didn't have look on the studies but I would not be surprised if a decent amount of participants were completely healthy individuals. And maybe (more from random sampling) some unsuspicious mildly overweight without other problems. Especially in the earlier cohorts of testing.

Is that the cost in the U.S.??

That's why the Brits are having it ;-)

Great writeup. Simple heuristics very often work wonders. The fraudsters are out there and try to pinch holes in your shield. Some time ago we were running a mobile service provider and had some issues with fraudulent postpaid subscribers - however the cost of using background checking services was substantial. We solved it quite effectively by turning the background checks on when the level of fraud went over a certain threshold which made them go away for some weeks. We kept this on and off pattern for a very long time with great success as it lowered the friction to sign up significantly when turned off…

Same experience today (Mon Feb 24). Actually I am negatively surprised.

The researchers did a great job in pointing out the failures in what basically is an old DIN standard that should not be used in this century. I congratulated them after the talk as I did similar research and didn’t get it finished for 38C8. Their presentation is spot on. The attack vector is definitely feasible and publicly known for a while. I honestly don’t understand why nobody in the industry wanted to switch to a safer alternative. The reaction by EFR will create an unnecessary Streisand effect and after all they will be able to upsell their customers to a (soon to be legacy) 450 MHz LTE system.

Seems multiple users are experiencing the same phenomenon...

When opening a SharePoint folder in Safari on MacOS, an empty file named "preload" is downloaded without any user interaction. Currently Microsoft is not reacting any more (as usual) and blames it to be an issue "at tenant level" (as usual) - which it isn't.

While this is weird (love this word...) this is also unacceptable and potentially dangerous behaviour.

Has anyone experienced the same issue and found workaround?

This is one of the uglier variants of a "classic"...

Sorry - but 3.5 mm / 1/8“ jacks / plugs are crap. They are prone to kinds of contact issues / noise, are not sturdy enough to withstand lateral forces like their 6.3 mm / 1/4“ siblings. Their pull out force is either non existent or plug destroying. Unless they are of the rare threaded type I try to avoid them (just as barrel jacks). Better get a (mini-)XLR or Lemo connector…

It's truly sad to see this beautiful place and collection of historic items being dissolved.

tl;dr: Don’t trust (optimizing) compilers. And NIST.

We all are probably guilty of falling for the convenience trap here or there. But setting up the sync between Dropbox and the NAS (Synology user here) with a one-way, don't delete, don't overwrite policy is a good lifeline to have - you know, just in case...

Naah - she‘ll be right mate ;-)

Signs of life from Lasse and a link to his web containing more information: https://tukaani.org/xz-backdoor/

Definitely sounds like a no-brainer / reasonable next step.

Most ISPs have CND appliances in their racks to save on uplink bandwidth. And from a satellite perspective the uplink (in this scenario: the downlink from the satellite to the gateway) definitely is the expensive bottleneck.

You want to avoid congestion and every bit of caching could be helpful.

Then it comes down to the mass and power budget (and the reliability of flash drives in space) - but that doesn't seem too terrible.

That could already be the case. Round trip time to the ~500km orbit is about 4 milliseconds (+ all other network elements before, after and in between). They claim to have a >5000km link running for significant time. Now think of a fibre link of that length and how many repeaters / routers will be needed due to attenuation and physical constraints. I can clearly see a path where Starlink laser links could be a viable option to subsea cables - at least for some priority traffic...

It's like compiling your compiler with the compiler you compiled. And eating your own dogfood is a proven tactic to have dev teams feel the pains of a product just like a customer does.

Elliott Williams (editor of Hackaday) held a very interesting talk this year at CCCamp that in very simple terms explained the components of a PID loop. Highly recommended! https://media.ccc.de/v/camp2023-57111-pid_loops_control_all_...

What are good and battle proven tools to

A) monitor traffic on my home network - especially in a MikroTik environment

B) identify malicious activity

Thx

Occam's razor tells me that this exploit route as described in the press release sounds way too complicated and that too much luck must have been involved. Therefore I am sceptical if we will ever hear the real story.