🎉 I’m happy to announce https://t.co/NmTxud9ldB for you!
🔮 It’s tarot reading service with AI and 3d interactions.
🛠️ We already builded MVP, so you can check it out by yourself!
🌌 I will stream a building of this service every my working day. Come to the streams ♥️
🎉 Exciting news! We are thrilled to announce the upcoming launch of our new online interactive tarot card reading service!
Our platform is currently in the building stage, but in the meantime, we invite you to check out our website at https://t.co/AxMClz05L8 where you can get
this is Postmately.
you paste a product link
we make TikTok carousels and short videos
you approve
it goes out on schedule, also on our network of niche pages
for small brands, marketplace sellers and apps.
waitlist in the reply
https://t.co/zlievswidl
Cube time zone controls now cover users, dashboards, embeds, and agents, so global teams can keep results aligned to the right local reporting window.
Full demo: https://t.co/IY3bZGE0Bc
Five years ago, we introduced the first version of Cube Store, our query engine for building and serving pre-aggregations. It is a key component of how Cube builds smaller aggregated tables from semantic layer definitions and uses aggregate awareness to route queries to matching aggregates.
The volume of queries served by Cube Store has grown exponentially since last year, as agents have become consumers of business intelligence.
We've learned a lot about building, refreshing, and serving those aggregates, and how that workload differs from traditional analytical workloads in cloud data warehouses. In the blog post below, we've compiled those lessons and shared some of the architecture decisions we made to optimize serving and refreshing pre-aggregations.
Igor Lukanin did a great job benchmarking Cube Store with a set of queries adapted from TPC-H to show how it behaves across query types and scale factors.
Blog and benchmark: https://t.co/QsmtHtFzDf
Cube has a new look: cleaner navigation, refreshed visuals, and product polish across the analytics workflow.
Latest changelog: https://t.co/lMD2o4Thea
Если вам нравится Preact за маленький размер - присмотритесь к Nano Kit.
Выпустил адаптеры для Preact: https://t.co/OVAZUgeV28
Nano Kit - стейт-менеджмент экосистема размером примерно с Nano Stores, ��о с DX как у больших полноценных решений.
Выпустил туториал по Nano Kit: пошагово от базового стора до роутинга и SSR.
https://t.co/BrvIBMabMO
Nano Kit - лёгкая, модульная и производительная экосистема для управления состоянием в современных веб-приложениях.
Начал новый опенсорс-проект — Nano Stores SQL, который позволяет использовать SQLite через WASM в браузере (или React Native) вместе с остальными умными сторами Nano Stores.
Чтобы UI пользователя не ждал данных с сервера и работал мгновенно.
https://t.co/y3hLEbFmKI
1. Проблема: разработчик запускает Claude Code, переключается на другую вкладку/телефон/кофе, и пропускает момент, когда агент закончил или ждёт ввод. Внимание фрагментировано. Контекст теряется. ��родуктивность падает.
Существующие решения — звуковые уведомления — не работают в наушниках с ANC, в шумном офисе, или когда ты уже в пятом созвоне за день.
А что если фидбэк будет тактильным? Не на экране, не в наушниках — а физически, через тело.