The pain of working with a large codebase without a proper architecture at the outset is that changing the core architecture becomes very difficult. And then the only question is how many workarounds will have to be implemented to release a new idea 🫠

Added feeds viewing in Atsky. This is the only section where the paths differed from Bluesky. Now, you can switch from Atsky to Bluesky from Almost any page by clicking the logo in the corner. And vice versa - by changing the address from bsky to atsky

I finally decided to take a look at the permissions. There's some customization already, but it's still a bit clunky. I'm wondering if I want to prioritize this or if the client doesn't really need it 🤔

And immediately a different start to the day The downside, though, is that you might not even start reading the news because you'll be busy liking all those ❤️ fluffy ❤️ beauties ❤️

In general, it’s even a little strange to me that, having such an open protocol, applications are so separated from other products

Not just decentralize, but also delayerarize 🤪😅 (When you're creating an abstraction, the key is to stop in time. So I haven't yet decided to think in that category [yet])

I would like to share a bit more about the concept - in case it resonates with someone else too 🙃 So, on the UI side, there would be several predefined card types: stream, media, story, post, links - designed for different placements like the top bar or side panel...

And now I can create a widget for myself as well I just wanted to see some beautiful photos before scrolling through my feed and then continue reading the news. Released in a simplified version, I'll see how useful it is and then improve implementation 🖼️

It's funny how on Christmas Eve they decided to figure out how the restrictions are configured. For now, I'm sticking with the aggressive and blunt blocking, but I need to figure out the more subtle options...

Released 📌 A bit about the idea: AT Protocol is an open network, and each application essentially acts as a layer within it. So why not make it possible to connect those layers? Stream Place is a great example of this kind of integration, but I think the potential goes much further

The final implementation is taking a little longer than I originally planned. But I'm almost done. And I think this is exactly how it should looks like 📹

I'm trying to finish all the ideas that have been on hold since the beginning of the year. And one of them is the light theme 🔅

That little bright line with its rounded edges is now one of the most pleasing elements of this redesign. It's nice to finally get around to the little details 🙃

One of the questions I ask myself is: what might Bluesky look like if we tried something different? One of those things is Apps 🧩 That's why they're now in Atsky - where you're used to seeing stories (but at atproto we have our own types of stories)

One of the nice perks of working on Atsky is the detailed [Bluesky's] architecture analysis. The way posts are structured used to seem chaotic, but now I realize it's all very simple - I just needed to understand all the helpers and types

I’m still figuring out how and what to share in terms of the personal stuff, so I’ll leave a few photos here again. Just to remind that I’m still real (and still connecting and interacting with the most wonderful people ❤️)

Do you know what bluesky should be called, given that it's built on the AT protocol? Atsky! I didn't even realize how well I chose the domain 😅

I can't put it off any longer, as there's still a lot of work to be done. So I've released the first part separately 🌌 So what's new at your sky?

I’ve been working on Atsky’s details these days, preparing it for future updates. I’m really hoping to give it a second life

Just checking that the embedded link still works, and in the meantime, you can wrap your year

I initially built graphs using coordinates, but I didn't even think that it would be so easy to transpile it into 3D

It was a good year, but it's far behind the previous one

* Just checking the tags, good morning everyone

If I had to choose what NextJS is really good at, it would be tooling

Need stable caching? Run it in a separate service! Published @nimpl/cache-server - it allows you to run cacheHandlers in a separate service, and your application will work with it via the API

"softTags - Tags to check for staleness (used in some cache strategies)" This is the only place where you can verify that revalidatePath was actually called, not just a generic cache strategy detail

Next.js caches fetch results. If I use fetch inside my caching logic, will I end up in the silliest loop?

A photo of the moment where I convince myself to go back to work on this package

Importing contacts from Twitter or Instagram by analyzing handles and names - that's how a modern import should looks like... Otherwise, what's the point of all this handle-focused work?

Wait, contacts? What? I'm sorry, but maybe what your product team really needs is an introverted person or zoomer...

It's nearly two weeks til new year! Don't be that sucker editing all your footers at midnight. Set it automatically with the power of ✨AI✨

Finally, I've implemented a cache layer for the file system. It's still one of the most basic and cheapest storage options, though. Along the way, I found many interesting APIs for working with streams, directories, and fs...

While working on a cache function for react-router, I ran into an interesting problem: how to generate a key for the cache entry? Like how do you get a unique key for the current context, for the current content, while still keeping it stable between runs or HMR? ...

So, I store the cache, including RSC payloads, in my storage. Does this mean I can return this cache directly at the CDN level with a certain configuration?

Also, judging by the tests, nextjs with cacheComponents responds about twice faster then React Router (80ms vs. 150ms) But because of this partial rendering, you feel it as a terrible lag

Added support for displaying cache lists layer by layer It works great for self-host and React Router, but with nextjs in Vercel, it produces strange behavior because it seems to create multiple cache-handler instances and I can't control this in serverless 🫠

Morning

Oh, I remembered the crutches we wrote in the previous place to display RSC in the storybook (which didn't work even after the storybook officially added support for them) 🫠

I spent the entire day optimizing caching and updating the structure. I managed to improve performance, standardize layers and add more documentation. +232 -232. Perfect 😌

So, if I enable cacheComponents, each bsky post object weighs about 1 KB. If I also cache it as a component, that's up to 3 KB. So Redis will give me about 10,000 posts. If the post lifetime is one minute 🤔

One of the common problems with using a separate root for the global-error is that when you update the root directory's styles or themes, the 404 error is forgotten How common? Well...

The Cached View widget has been published (@nimpl/cache-widget) 🎉 Suitable for all frameworks as it doesn't depend on anything. It helps not only with debugging but also with simply understanding what's going on

I finally managed to successfully integrate this cache view window into Next.js and React Router 7 Tomorrow I'll be checking the critical cases and probably adding it to the demo 😌

Researchers have found two new vulnerabilities in React Server Components while attempting to exploit the patches last week. These are new issues, separate from the critical CVE last week. The patch for React2Shell remains effective for the Remote Code Execution exploit.

Wait, what do you mean by "compiling via TSC won't be ESM-friendly and I need to use additional workarounds just to add the extension"? 🫠

I just hope that at least this time there will be no cringy posts that this great opportunity of the great king is written in nextjs