Ceco Svidovs𐤊i

@DaVido1008 @TheCleanCarClub Also the frequency of the light from halogen is lower so it works better in fog.

@TheCleanCarClub Halogen lights are the best option. They reduce the risk of accidents caused by oncoming cars, preventing you from being blinded by other vehicles. Additionally, they produce significantly less glare.

How Different Headlights Shine.

@Elite_Hat_193 @theapplehub You asked a question. I suggested an answer. I don’t want anything.

AirPods Max vs AirPods Max 2

My iPhone 17 Pro Max battery health remains at 100% after 4 months! What is your iPhone’s battery health?

That slap was so personal 😭😂💔

@Johny_Serb @x_ecutive @Stratos_arts R u blind?

@x_ecutive @Stratos_arts Not true ,my 2016 Opel Insignia ,after 9 years i have still no idea where it is,its not visible even i look try the grill,there is nothing , and work perfect that i never updated the car softvare,was afraid that update would made it worst

Mercedes "DISTRONIC" Adaptive Cruise Control system looks so funny on older cars, like the W203 here that has it

$KAS Did you catch Yonatan’s presentation at Tokenize_LDN London ? (High video & sound quality) 👇 youtu.be/n-TyLf2t7MA A key watch for anyone serious about Kaspa’s future and the role of RTD,low-latency oracles,MEV and more!

@WorkaholicDavid Source: Trust me bro

One of my buddies called me today, he said he got laid off. Apparently, this was the thirs time he came in late, because his iPhone alarm did not go off in time. I feel bad for the dude

@Igra_Labs Mainnet? Wen?

Caravel Testnet just processed its ten millionth block without a single glitch. What's next?

@DrFonts I’m tired of seeing bad remakes of brands’ logos. I have never seen a good one even once. I think you should all focus on learning how to make good logos first. Y’all suck.

What do you think? Did he fix it? This allanpeters idea on how to fix the Spotify logo.

@WhaleInsider Inverse Wynn

JUST IN: James Wynn reopened $BTC 40x leverage short position and has now been partially liquidated.

@binance, Thanks for including me in the top 100 blockchain people list, appreciate the signal! I must decline the Dubai invite though. I do not wish to disrespect, but many of the award voters are avid kaspians who rooted for my kaspa status at least as much as for my research. Let them win or count me out. Crypto has turned from a euphoric cypherpunk project to a house-friendly casino. You may not be the culprit, but as a top player you hold the lion’s share of the responsibility to correct this, and the October crash your USDe oracle glitch helped trigger adds to what needs to be addressed. There are three classes of crypto, as @mert put it recently: commercial crypto, casino crypto, cypherpunk crypto. <> A TBTF CEX should know better and play a different game with hardcore crypto projects. When binance lists a green frog three weeks post its “launch” but skips a fair-launched-Nakamoto-Consensus-100ms-upgrade-ATH-top-20-the-only-nonbitcoin-marathon-mined project, this is not merely binance rationally calculating; it is also binance molding the market in a way that is alas misaligned with the roots of the movement. You may feel that kaspa’s sovereign money thesis is boring – that bitcoin is already money and that implementing an internet-speed bitcoin is useless - fine. Wrong but fine. But what’s the thesis for the green frog? Money is a classic chicken-and-egg product. It is a scam up until one moment before tipping point, “most of the value comes from the value that others place in it.” Considering your resources and influence, I think it's safe to say you can serve as both the egg and the chicken and make it worth your while to push sound attempts towards tipping point. @cz_binance tweeted recently that “strong projects will be listed.” But binance is part of what defines "strong", it bears responsibility for the market’s compass and impulse and definition of strong. It is not a read-only entity. Binance listing fees are legit, they are just unfit for category cypherpunk. Kaspa devs and early supporters fairly mined less than half what satoshi and hals mined. We don’t have a 20% ZEC-style founders’ reward or protocol-enforced dev fund; this is not a jab at ZEC and the wonderful @Zooko, who was crashing in my car on a late Thursday back in the low ZEC MC days – if somebody deserves to win it is zooko – but assuming binance is not taking a maxi bet, it should revisit its relationship with hardcore crypto. We are here through bull and bear, ICOs NFTs XYZs; and we are the source of confidence that restores faith and capital inflow post meme-induced or CEX-induced crashes. Please fix this. Thanks again, hashdag cc @michaelsuttonil Exhibit A: Binance Innovation Zone Exhibit B: 10 bps Nakamoto Consensus

@LightslicerGP @SLKVinyl Still the share button looks unbalanced.

@LightslicerGP @SLKVinyl I think the original looks balanced.

Should Apple add frosted glass to iOS 26?

@SLKVinyl @LightslicerGP It’s not messed up. If you align it perfectly it will look unbalanced since there’s a small handle on top of the trash can. The folder isn’t perfectly aligned either. Yet all of them look balanced.

@LightslicerGP I copied it 1:1 to exactly how Apple made it and I figured out afterwards that it was messed up 😭

420 $KAS public nodes online and counting. Steadily approaching the goal of 1000.

@cryptomatt1983 It’s Gate’s wallet. No way they have the biggest volume and only 100m $kas. MEXC has 1b…

Former Wallet #2 has added a whopping 154 million KASPA becoming the largest KASPA wallet. 👀 $KAS

@1brad_ass @saylordocs As of now Microstrategy owns close to 600k bitcoin. It’s not a few thousand…

@saylordocs He’s stated hes burning his keys so his bitcoins are never found…that money could be used in a much more positive way than making some holders more wealthy…millions of coins have already been lost, not sure why he thinks a few thousand more is a noble cause

Michael Saylor says, "I'm a single guy with no kids—when I'm gone, just like Satoshi left a million #Bitcoin to the world, I'll leave everything I've got to civilization." 👏

@coderofstuff_ @LevendiPro So it can achieve more transactions in a single day?

The transactions in this stress test aren’t reflective of real user txs. So these txs all have low fees and can tolerate severe delays (as long as the transaction eventually goes through). During high load, a real user may opt to pay slightly more (either priority or medium bucket level from the fee estimate) to have their tx processed with faster SLA.

a few points that come to mind this evening, in no particular order: - Kaspa pre-zk is a sequencing and data-carrying service; there’s no conceptual difference between txn payloads carrying EVM calldata, KRC20 inscriptions or Kasia chat msgs in that regard - in particular, the above means there’s no settlement on L1; there are no validity proofs or fraud proofs verified. It’s a one-way route: L2s listen to L1 and the data it makes available; L1 has no idea what interpretation L2s give to this data - hence an L1<>L2 KAS bridge (in this pre-zk era) cannot be fully trustless, no matter the cleverness of its designers - this does not mean all L2 funds require trust (you can have tokens that live only on the L2; think of it as any other standalone EVM, eg Eth L1) - in order for this normal L2 operation to be decentralized (other than KAS bridging which must hold some form of trust as mentioned), its codebase must be open-source and independent validators must be able to run it as they wish. I can respect a decision not to immediately open source something you worked on and holds significant IP, but the tradeoff is clear: until the L2 is fully open-source, there is a degree of centralization/trust in anything it executes, and users should be fully aware. - (btw iirc some Eth rollups were partially closed-source at their respective mainnet launch, though the case is a bit different since they had L1 settlement support) - I admire Kasplex’s efforts to bring smart contracts to Kaspa asap. If I’m allowed to be somewhat cynical I think tomorrow's launch is a win-win situation. If the launch succeeds it showcases Kaspa’s speed, responsiveness and immense throughput. If it somewhat stutters or has initial problems, they are not inherent to Kaspa and indicate nothing about the core technology and will be fixed in following iterations (or perfected by other entities). I’m not naive and I’m aware that not everyone understands the differentiation between layers, but it’s the simple truth and will eventually rise. other r&d updates in short: - dk: being worked on by some dkoders, initial implementation is already taking shape - vprogs: not only a yellow paper, a rust prototype is wip