eapotapov

I've recently bought a samsung galaxy tab s11.

I had some huawei tablet for reading before, but now the main goal was to be able to ssh/kubectl to remote machines and for quick surfing, chats, etc (my new laptop is heavy).

I was trying to find a case + keyboard with good reviews, no luck then, I didn't think it was possible, I've found out that you can use an apple magic keyboard with it and I had a spare one, so I have a case and a bluetooth magic keyboard.

The keyboard, comparing to anything that is sold for tablets is amazing, laptop experience.

For those who have the issue.

I reported the issue in discussions some time ago, but had no reaction/response.

I was able to reproduce the leak consistently. Finally I've got all the reports done by me, Ghostty sources and Claude Code and tried to fix it.

For the first couple of weeks there were no leaks at all, now it started again but only 1/10 of the times it was before.

https://github.com/ghostty-org/ghostty/discussions/9786 There are some logs and a Claude Code review md file that might be useful.

Hope it will help someone investigate further.

oh, it's actually a problem with ultra-wide screens and there is no simple resolution for this and I gave up https://github.com/microsoft/wslg/issues/590

Thanks! I did it, but I'm having problems with window resizing and mouse selection. When I try to resize the window, the actual window is smaller than it appears. Did you encounter the same issue? Related issues:

https://github.com/microsoft/wslg/issues/1008 https://github.com/microsoft/wslg/issues/633

I don't know if it's good or bad news for you, but at least you're pretty lucky to have reached this stage—the majority just get rejected.

From what I know, some people have received their visas after 12-16 months of processing. It will most likely be valid for only one year, though. Eight months is pretty early to expect anything at this point.

Here’s a Serbian-Russian expats visa Telegram group where there’s a US section. You can ask people there about their processing times: https://t.me/serbia_visas_chat

Again, I’d say you’ve had some luck!

Well, that's life. Thank you so much—at least now I know my chances.

Many Russian citizens who have moved out of Russia are currently being denied B1/B2 visas, regardless of their prior history or any proof of ties to their current country of residence. The rejection rate is around 60%, and I am among those affected under 214(b), despite having held five B1/B2 visas before, with no visa overstays or other issues.

I don't plan to move to the US, but my startup operates in the US market, and it would be beneficial if I could meet customers and investors in person.

I plan to apply again next spring (a year after the denial), and if I’m unsuccessful, I’m considering applying for an O1 visa to be able to visit the US, although I have no intention of staying long-term. Do you think this is a good idea? I’m concerned that after the O1 visa expires, my only option to return might be to apply for another work visa or O1 visa.

I wonder if anyone was really trying to do it, and if they have a defined procedure for such request (get the check, proceed with the source code access etc.)

I commute by car from Sunnyvale, CA to SF (Harrison/8th) almost every day, and I'm flexible with when I can drive there, so I started to track google maps time to find the better time.

the pattern repeats almost every day: https://monosnap.com/file/jHAuLrr1JqOxM6lSNN8H0DGFSoCcJb

1st wave starts at 5am and at the top of it at 8am then it's getting better. there's a spot between 10:30 and noon when you can drive within 40 to 50 minutes, then it's getting worse (2nd wave). if you would decide to drive at 5pm it would take almost 1.5 hours to drive to Sunnyvale

the best time to drive from SF to the Valley is after 8pm, there is a small increase in between 10pm and midnight - roadworks while traffic is still present.

it's interesting that the pattern is accurate up to the minute, it's 10:30, not 10:15 or 10:45 when there's a spot to drive, almost every day

I think the biggest problem is that the media got dissolved within social networks clickbait titles were existing before - just remember tabloids.

the thing is that when you see offline media you see: 1. the brand 2. you know how reliable is this media 3. you usually know the audience and think if you're part of it and trust the media

so in offline, they don't afraid that their reader will buy something else (well they afraid, but it's not a matter of click)

in facebook it's all just titles when reposted and people don't check where exactly it was published before clicking

so it's just like "national examiner" will have a version published in the design of nytimes or anything else - so they will not only have their audience but will try to get a slice of other media's audience

it could have been a quite complex thing to do for offline media as you need to actually print the edition, and pay money for it, but it's free for online, and you get money per view/per click

so i think it's definitely a war between media for this new spread audience on social, there should be a new way to re-establish reliability

This seems to me as some kind of defeat and that makes me sad. It's sad for me to look how great companies grew old

I think Microsoft is now afraid that people (developers that were hired by enterprises) are willing to move to *nix so much so that they will force enterprises to gave up on MS stack.

This way they could lose SQL Server customer and Windows customer at the same time - having SQL Server version for Linux will keep SQL Server customer.

I believe this wouldn't have happened 10 years ago, and moreover, it would have sounded just unbelievable.

This reminds me not only of things that could change very fast. It reminds that even when things go well with your business there's always someone thing that could "disrupt" your market, like a new dimension. And that thing won't be invisible. It will grow nearby and you will see such company and just won't assume that it represents any danger.

I've read the article and that's one more argument for me that IPO is a very toxic thing sometimes. mass marketing strategy/creating a commodity is a very hard longplay game. the prize is a huge stake of the market, but it's very challenging to get there.

now assume you have your revenue and then you get two customers that are going to pay you 25% of your current revenue (20% of the revenue after they start working with you). if you're private you just stick to your strategy and count these two clients as some random money (as they don't fit your main strategy). being public, now, if you lose these customers - you're at risk, the market forces you to make decisions, to keep these customers, to go to the enterprise market, hire sales people etc.

"In Twilio’s earliest days, multiple angel investors and VCs told Twilio’s founders that focusing on software developers would never lead to a venture-scale business. To make their case, Twilio’s skeptics pointed out that software developers have no control over budgets in the enterprise.

But Lawson, Cooke, and Wolthius were undeterred. They believed deeply that software developers held the keys to the future…and not just of telecom, but perhaps the whole world."

well now, being public you can't just do this.

imagine Amazon listening to advise to use retail-chains (system integrators in Twilio case), or should Amazon do really care about revenue coming from one specific customer (even if it's huge)?

it's really hard to keep doing what you believe you need to do when you're under pressure of the public market. I absolutely understand why do such companies go public, but that makes me sad.

just a few non-academic but tech remarks:

1. when you limit the number of requests by just dropping them there is still a huge chance to get a lot of troubles: each HTTP request from the browser now can lead to dozens of additional requests, ajax/push etc. if some of them would be dropped - the user might get a broken page which sometimes even worse than just "try to reload" one. so there should be some smart balancing / smart rules for the packets dropping

2. from my experience there are two situations when the web app gets overloaded: excessive cpu usage, excessive ram usage (when we talk about databases it's disk as well but it's a different story)

excessive cpu usage have its own scheduler/queue which usually works pretty well and doesn't have any side affects when you just rebalance/scale the system. assuming that your web app responds in 200ms and the cpu is having 300% of usage it's just going to be 600ms for you in a worst case scenario.

excessive ram usage is much worse as you can't easily "oversell" it - either you have swap and the system will start writing to the disk either some of your processes will get killed by out-of-memory killer (and most likely it's going to be something that's necessary to keep the app working). accessing the disk instead of memory is very time consuming (10-100x if you have good ssd, thousands of x if you have regular hdd). even if you stop the traffic - your system processes might still use swap memory (it takes time for linux to move them out of swap memory), so you probably won't be able to access the system for a long time (20-30 minutes more for instance). this means you should be very picky at what you set by the threshold for the limit - it couldn't be just some average value, it should be the limit of the thing that brings you most troubles when overloaded.

the bastion host was our inside project as we manage thousands of servers and somehow need to manage access to them. opensourced a week ago, now in active development. any questions, feedback - appreciated

what's really interesting for me is their brand-name vs white box comparison:

DRAM one-bit flip, Brand: 1 in 2700, White box: 1 in 950 Disk subsystem: Brand: 1 in 180, White box: 1 in 180

Assuming that brand-name desktops have brand-name memory and disks it means:

1. brand of your non-SSD desktop-level HDD absolutely doesn't matter. 2. brand-name memory is 3 times less likely to fail.