ทวีตที่ปักหมุด
cozy
77.6K posts
cozy
@vec0zy
| one must imagine oneself cozy | contributing to: @premialabs | @edenaesthetix | @ch4pbot | @tomedocs
~losrel เข้าร่วม Temmuz 2011
2.1K กำลังติดตาม42.6K ผู้ติดตาม
ouhhh… husbandt…
you spen 2k on maca mini, say you have special agents, stay up very late, no build nothing, so late for work too many time. now anthropic build special agent, cost no mronies… can just use shell phrone. now we are homeress and im so cold…
Thariq@trq212
We just released Claude Code channels, which allows you to control your Claude Code session through select MCPs, starting with Telegram and Discord. Use this to message Claude Code directly from your phone.
English
ch4p does this too. 0 external dependencies and unique tool calls/abilities per gateway channel
ch4p.ai
Vercel@vercel
Your users are on Slack, Discord, Teams, WhatsApp, Telegram, GitHub, Linear, and more. Your agents should be too. Chat SDK lets your agents run on every platform from a single codebase. Watch the announcement ↓
English
Rented out a castle for a 20 person private dinner on April 2nd
We're bringing the best traders, sharpest thinkers, and biggest eaters together for one night
Few slots left, who should be there?
English
@BFreshHB @KyanExchange @vxdenton @crypto_linn @Sellingvol @HackermanAce @blocmates @therollupco ty! been a long time coming
English
@KyanExchange @vec0zy @vxdenton @crypto_linn @Sellingvol @HackermanAce @blocmates @therollupco Congrats team!
English
The Kyan Private Beta is NOW LIVE!!!
Referral code holders are able to start trading on Mainnet Arbitrum at app.kyan.blue
Spots are CAPPED, so get in FAST!
Waitlist users will be rolled in progressively.
Good luck, have fun 💙
x.com/KyanExchange/s…
Kyan@KyanExchange
The Kyan Private Beta will be going LIVE TOMORROW! Referral code holders will be able to start trading on Mainnet Arbitrum at app.kyan.blue 💙 Spots are capped, so make sure to get in fast! Waitlist users will be rolled in progressively. x.com/KyanExchange/s…
English
cozy รีทวีตแล้ว
We are letting in a very limited amount of people during the first few days.
Shoot me a DM if you want a code, I think there're still a few spots left!
Kyan@KyanExchange
The Kyan Private Beta is NOW LIVE!!! Referral code holders are able to start trading on Mainnet Arbitrum at app.kyan.blue Spots are CAPPED, so get in FAST! Waitlist users will be rolled in progressively. Good luck, have fun 💙 x.com/KyanExchange/s…
English
cozy รีทวีตแล้ว
@LilQwantXBT @KyanExchange @vxdenton @crypto_linn @Sellingvol @HackermanAce @blocmates @therollupco I posted a code in the tester group for u
English
@KyanExchange @vec0zy @vxdenton @crypto_linn @Sellingvol @HackermanAce @blocmates @therollupco Get me in!!!!
English
cozy รีทวีตแล้ว
They are live with private beta today!
Got a bunch more cooking for you guys over the next few days.
Kyan@KyanExchange
The Kyan Private Beta will be going LIVE TOMORROW! Referral code holders will be able to start trading on Mainnet Arbitrum at app.kyan.blue 💙 Spots are capped, so make sure to get in fast! Waitlist users will be rolled in progressively. x.com/KyanExchange/s…
English
yep ur right, our versioning is whole-site snapshots. u version the entire doc set (v1, v2, v3) and users switch between them. it's built for library/api docs where u cut a release and snapshot everything.
what ur describing, per-document versioning tied to individual git commits, where "privacy policy" is at v3.2 while "security policy" is at v1.0, for example, is a different model entirely. tome doesn't do that today.
being honest, that's a pretty specialized workflow (git-backed per-doc versions, interactive diffs, suggest-change flows). it's closer to a cms with version control than a docs platform. tome could potentially support that kind of architecture as a plugin or extension
if that's your core requirement, you might want something more like a git-backed wiki or a custom next.js build where you have full control over the versioning layer. tome is strongest when you want a polished docs site up fast with ai + api tooling. the policy library use case might need more bespoke infrastructure than we'd provide out of the box currently.
happy to keep chatting about it though. it's an interesting problem space and something i may be interested in building out!
English
I’ll have some more thoughts on your other comments later, but one quick clarification: your versioning is for an entire snapshot of the “library”, right? I can’t do independent versioning of a given “doc” within the library. If we assume the git/PR workflow is tied to a given markdown file (as it would be in my policy library use case) THAT document would have a version independent of other docs. Computing it gets a little hackish (branch based tags probably the easiest), but I’d want the generation able to handle it (relatively easy) as well as the authoring/editing/commiting logic (non trivial).
English
tome v0.5.0 just dropped!
two new theme presets:
- cipher - cyberpunk vibes. acid yellow-green text, vibrant blue accents, Bodoni Moda serif headings. inspired by Marathon
- mint - i think you know... = )
both are WCAG 2.1 AA-compliant out of the box.
also in this release:
- API reference pages now have a wider layout (1100px), so your endpoints stop getting cut off
- cleaner subheadings (removed the # prefix)
- all apps default to light mode (still respects your system preference)
- all preset fonts are now loaded automatically
upgrade: npm i @tomehq/cli@latest
docs: tome.center/docs/theming
English
@bitfloorsghost @big_duca @AwakenTax he’s such a stud. between duca and the team at @Darien_Advisors, they literally made my taxes last year the most effortless experience ive ever had at tax time
English
been using a really terrible tax software for years, basically in an abusive relationship because im too scared to change
@big_duca has been helping me try and move over to @AwakenTax and i feel like i've gotten more help in 2 days than the last 5 years with the other
English
appreciate the thoughtful comparison! to clarify positioning, tome isn't a "lite" anything. different philosophy.
on what u need specifically:
- git-versioned content - we have this. multi-version docs are built in today. u define versioned directories (v1/, v2/, etc.) and automatically get a version switcher in the header. tome.center/docs/guides/ve…
- wysiwyg editing - on our roadmap. and ive already baked in some security and sandboxing in preparation.
- git pr workflow - tome is file-based markdown/mdx in ur repo, so pr-based review workflows work out of the box. that's the intended flow. = )
- interactive diffs / "suggest change" - not built yet, but this is a great use case. we're building in public, so i would love to hear more about the policy library scenario.
vs fumadocs: they give u building blocks inside next.js which is great if ur already deep in that ecosystem. tome is a standalone docs platform. u get ai chat, api playground, mcp, migration tooling, themes, and deploy w/o stitching anything together. start writing in five minutes, not five hours.
short answer: yes, tome can handle this. happy to chat more about ur use case and look into adding the "suggest change" feature.
English
thx... so like a doc-centric "lite" version of fumadocs? (plus some features around the margins)
Not trying to gloss over key features, just trying to get my head around positioning.
I have a couple of features that I'll eventually have to extend for a policy library use case and want to understand the platform: would love to have git versioned content with wysiwyg editing and approval workflow. Expecting to use git PRs as my workflow (doesn't seem to be a better OSS solution there atm), but want to have the ability to show versioning in generated content, interactive diffs (hover to see prior version, etc), and "suggest change" sort of workflows.
assuming that vision, will I be able to adapt tome, or should I go with something more heavyweight like fumadocs?
English
happy to! mkdocs/material is excellent, and im a fan of it.
where tome is different:
- js/ts ecosystem - mdx lets u drop interactive react components directly into your docs
- built-in api reference + playground from ur openapi spec
- ai chat widget (BYOK: bring your own openai or anthropic key)
- built-in mcp server so ai agents can read your docs natively
- one-command migration from mintlify/gitbook
- multiple theme presets out of the box
- me. = ) i ship fast and fix issues just as quickly. i want tome to be the most feature-rich and polished oss documentation framework out
if ur in the python ecosystem and want battle-tested stability, mkdocs/material is a great choice. if ur in js/ts land and want interactive docs with ai and api tooling baked in, that's where we live.
English
@TomeDocs I really like what I'm seeing, but please help me understand where you're better/different than a mkdocs/material (zensical) solution.
English
cozy รีทวีตแล้ว
If anyone else is affected by coinbase shutting down their commerce accounts you can use
checkout.llamapay.io
It's API is a drop-in replacement for coinbase commerce so you can switch by just replacing urls and keys
Plus much more efficient + lower cost
mbaril010.eth 🦇🔊@mbaril010
Hey all, looks like @coinbase @CoinbaseBiz is killing their coinbase commerce platform and the business account are only available in the US and Singapore. So CT what are the option to replace them ? @MoonPayCommerce ? Who else ?
English