Adam Wołk

@notAyker Love the softshell term :)

with the shutdown of Destiny announced, I noticed a trend on marathon today. I guess that all publicity is good publicity, I noticed a lot of new players in game. So when you took run, level based matchmaking is disabled, and by rooking into perimeter, I was placed in a LOT of beginner lobbies. after checking my recent players I was seeing dozens of people who just bought the game: 1: it's very cool that new people are checking out marathon so late in wipe, esp right before season 2 2: it is VERY unfair that I was able to match against someone with 1.8 hours 😭 but also kinda funny (they killed me) pls protect the softshells

My first Marathon review aged pretty well.

@therealrthorat @StickmanCDN @PaulTassi @themattsterv I would argue that having a save pocket is net negative because deciding what to put there and post match regrets of "I should have put it in the safepocket" will generate more anxiety/gear fear.

@StickmanCDN @PaulTassi @themattsterv No safe pocket sounds awesome to elite players. To everyone else it means they quit playing. That's why Tarkov has it. If your experience is that you lose most of your fights, the game is a boring slog that wastes your time. To survive, it must add a safe pocket.

I just flat out do not know what a Marathon pivot would be. Nothing that would help significantly, in any case

This game is my recent obsession.

@Ziegler_Dev 4/4 And finally, minting keys is currently a very un-fun aspect. Sitting around for 5 minutes in a match as getting downed destroys the key is not fun and the current design incentivizes that as the most optimal strategy.

@Ziegler_Dev 3/n Upon death, it would be good to know what killed us, at least shield and gun rarity of the player that downed us. Could allow more details after run complete. Random fill is very hit and miss, would be good to match players by loot/kit value for squad fill.

UPDATE: WALKING THE PERIMETER AND UPPING THE GAME We are making an update to the Experimental queue and shifting the Sponsored Marsh map to Sponsored Perimeter. Details below: - As of 3PM PT Sponsored - Perimeter will become available. - Sponsored Perimeter will require you to have a free (green/enhanced tier) sponsored kit equipped to queue. - Sponsored Perimeter will only support crew matching, or pre-made crew queueing. To commemorate this experiment we will also be upping the floor on sponsored kits. Green sponsored kits will now be free and grey tier sponsored kits will be retired until the end of season. Thanks to everyone who has been participating in the Sponsored Dire Marsh experiment, we've learned a lot from your feedback and from observing you. As we roll out this new queue, we look forward to hearing from all of you who want to hop in and join us especially those of you at hauler who want to duke it out.

@casualblu3 I think it’s good for sponsored map modes. Before that it was a rush to who first can find any gun & shield. It leads to less rush based games.

Oh green free kits, I wonder what the thinking is here? Raising the gear / power floor perhaps as they think the standard free kit is maybe too weak?

@emsi_kil3r Nie zdziwiłbym się jakby tak było 🤣🤣

@mulander Może też filmik zobaczyło i mu się odechciało robić :)

📣Citus 14.0 open source release is out with support for #PostgreSQL 18! 🎉 Check out the blog post for details on distributed PG18 with Citus 14, such as AIO, skip-scan, uuidv7(), OAuth, RETURNING OLD/NEW, temporal constraints, and more. citusdata.com/blog/2026/02/1…

I just submitted mine!

👀 Seen this week at Ignite, members of #PosetteConf organizing team past & present Aaron Wislang (@as_w), Adam Wolk (@mulander), & Teresa Giacomini (@tgcmn). So fun to meet in person, some for the very first time. 🎉 PS - CFP is open until Feb 1. 😜 #postgresql #cfp #friends

This makes me think. In the future will we see people flayed on stage to prove they are not robots? 🫣

@vmg @dev_retarded Have you evaluated the Citus extension? It is row-based sharding in PostgreSQL with horizontal scalability. If you did, I would be curios to know your pros/cons :)

@dev_retarded Yes, for this specific workload I don’t think those kind of globally distributed databases make sense. All the tables are explicitly sharded, so we wanted something that could scale horizontally with sharding.

This is one of the things I’ve been doing at Cursor! We’ve migrated our largest database workload, the `codebase` cluster, from AWS Aurora Limitless to PlanetScale. The cluster contains syncing metadata for all the user codebases that we index. Why did we migrate from Aurora Limitless? Basically, it’s a very poor database offering. AWS could tell that the Postgres market is very hot right now and they wanted to be first-to-market with a “sharding solution” for infinite scalability. But the product they’ve launched is veeeery far from production ready. From availability, to performance to pricing… It was just a constant stream of issues. And you know with AWS, when the system works it works quite well, but when it breaks, it’s very hard to get good support, and that made operating the cluster a nightmare. Limitless just turned out to actually have a lot of limits in practice. Why did we choose PlanetScale? I did try to stay out of the conversation, because it felt kinda lame to start pitching my previous startup right after joining a new one, and obviously I’m biased because I’ve worked really hard these past 5 years on performance for the PlanetScale platform. Overall, I think all the infra folks already had a lot of confidence on the capacity for scale Vitess has, so it boiled down to whether it actually made sense to port our Postgres workload to MySQL. Ironically, what made the choice easier is that Aurora Limitless **doesn’t support replication streams** (seriously!! it’s in the roadmap but right now you’re just locked-in if you move your data in!!!), and since we had to make major changes to perform the migration at the application level, it wasn’t a significant effort to move from Postgres to MySQL while we were at it. So yes, the migration was not easy, but the end result was 100% worth it. Despite MySQL’s many shortcomings, the performance of Vitess + MySQL at scale on PlanetScale Metal is just unreal, miles ahead of anything you can do with a Postgres-compatible database right now. Can’t wait to see what the PS team does with their sharding solution for Postgres — it feels like a massive gap on the database landscape right now.

@TheSopranosClub Signing happy birthday to AJ 🤣

What is Irina doing in 2025?

@Fluffly_4 @LRThaGhost @MortalKombat Lingering metric. I was one of those who pre ordered and ended up hugely disappointed. I’m not buying new instalments in the franchise anymore.

@LRThaGhost @MortalKombat I mean it outsold every other fighting game this gen so those games would be deleted first

Play Mortal Kombat 1 now through PS+. It’s In Our Blood!

@M4C_4T4K79 Hack the planet. Zero cool biography bro.

@kosa64 Cieszę się, że trafiła w dobre ręce :)

@pjeroshkihime @raszuuu Wystarczy, że odkręci gaz i zapomni.

@raszuuu Czy stanowi zagrożenie to nie wiem, bo chyba głównie siedzi w domu i spamuje tweetami ale i tak mam nadzieję, że jest pod dobrą opieką

W pierwszej chwili myślałam, że to troll, ale weszlam w profil i to konto musi być prowadzone przez bardzo chorą osobę 💀