Weed/0

4.3K posts

Weed/0

Weed/0

@weedpatchtwo

I AM divided by 0

weed.enterprises 参加日 Mart 2011
1.3K フォロー中903 フォロワー
Weed/0 がリツイート
Andrej Karpathy
Andrej Karpathy@karpathy·
This is what the ideal grocery store looks like. Minimally processed (NOVA Group 1) food only (no "edible food-like substances"), organic, local, fresh. Food should not be more complex than this, yet I don't believe this exists.
Andrej Karpathy tweet media
English
534
474
6.1K
595.5K
ᴅᴀɴɪᴇʟ ᴍɪᴇssʟᴇʀ 🛡️
@karpathy I really like it! But it’s still one level too deep. I think the actual skill is more like Intent engineering. Articulating what you want extremely clearly. As critical as it is, the context is still just support. The more important part is the clear thinking.
English
4
1
41
13.1K
Andrej Karpathy
Andrej Karpathy@karpathy·
+1 for "context engineering" over "prompt engineering". People associate prompts with short task descriptions you'd give an LLM in your day-to-day use. When in every industrial-strength LLM app, context engineering is the delicate art and science of filling the context window with just the right information for the next step. Science because doing this right involves task descriptions and explanations, few shot examples, RAG, related (possibly multimodal) data, tools, state and history, compacting... Too little or of the wrong form and the LLM doesn't have the right context for optimal performance. Too much or too irrelevant and the LLM costs might go up and performance might come down. Doing this well is highly non-trivial. And art because of the guiding intuition around LLM psychology of people spirits. On top of context engineering itself, an LLM app has to: - break up problems just right into control flows - pack the context windows just right - dispatch calls to LLMs of the right kind and capability - handle generation-verification UIUX flows - a lot more - guardrails, security, evals, parallelism, prefetching, ... So context engineering is just one small piece of an emerging thick layer of non-trivial software that coordinates individual LLM calls (and a lot more) into full LLM apps. The term "ChatGPT wrapper" is tired and really, really wrong.
tobi lutke@tobi

I really like the term “context engineering” over prompt engineering. It describes the core skill better: the art of providing all the context for the task to be plausibly solvable by the LLM.

English
530
2.1K
14.3K
2.4M
Weed/0
Weed/0@weedpatchtwo·
@elonmusk You aren't wrong, Mars should be colonized, and you should do it. But turning Earth back into Earth isn't wrong either. The politics would be the only barrier; the technology would be less difficult. Too bad there isn't a powerful enough chaotic neutral to stir the pot.
English
0
0
2
26
Weed/0
Weed/0@weedpatchtwo·
@TheRevereGC Maybe get this flag the retirement it deserves ASAP? Kind of unacceptable to fly our colors in such shape. 🇺🇸
Weed/0 tweet media
English
0
0
0
5
Weed/0 がリツイート
Dan Ostrovsky ₿ Ξ ∞
Dan Ostrovsky ₿ Ξ ∞@danostrovsky·
🚀 ICP Devs: The Future is in Your Hands! 🌐 The #1 priority for $ICP developers should be supercharging defi and interoperability in general by enabling seamless “Connect Wallet” flows across the ecosystem. Imagine the kind of magical experiences we see on other networks happening right here—it's time to make that happen. Here’s the challenge: the fragmentation of wallets and lack of support for global “Connect Wallet” flows in dapps has led to: 🚫 Lower DEX volume and liquidity 🔒 No NFT- or token-gated experiences ❌ Missing platforms like Rabbithole.gg to reward active users (though I know @konectA_Dao is on it!) @OpenChat could be a protocol to rival not just Telegram, but every social network combined. $ICP is primed for it, but we need to build for connected wallets and the data they own across the ecosystem. The latest @NFIDWallet does just that—it supports ICRC ecosystem standards and shows what “Connect Wallet” for ICP dapps will look like (check out the demo: demo.identitykit.xyz). Internet Identity, @StoicWalletApp, @plug_wallet, and Oisy will also soon support those standards. We’re investing heavily in this because making it easy for users to connect their global address and for developers to read their assets/data across the ICP ecosystem will empower $ICP devs to create groundbreaking products. We may not have the resources of centralized teams, but we can win by building for a unified internet identity connected across a thriving decentralized ecosystem. Let’s unlock the true potential of $ICP! 🌍🚀
NFID Labs@IdentityMaxis

More than just UI! @NFIDWallet just got a big upgrade: 🙅‍♂️ Forget about spam - spam tokens are categorized and can be hidden 💰 View your full portfolio value - all your digital assets in one number (powered by @ICPSwap and @_GeekFactory) 💨 Speed improvements - do it all faster

English
6
14
82
5.3K
Weed/0
Weed/0@weedpatchtwo·
@DanielMiessler I'd recommend watching @MINDBANKai @DanielMiessler. Our mission is to become the most trusted digital twin platform. We are currently building digital twins of humans, with a focus on self care and autonomy. I've been following your work. I'm very intrigued by your perspective!
English
0
0
0
14
Weed/0 がリツイート
Dan Ostrovsky ₿ Ξ ∞
Dan Ostrovsky ₿ Ξ ∞@danostrovsky·
$ICP devs - if you're interested to support all wallets connecting and transacting with your dapps without integrating each individually, especially as the ecosystem grows and new wallets are built, please join the wallet working group on June 4 at 16:00 UTC for a presentation on the current state of standards and to provide feedback on progress. The goals have been to standardize how dapps request... - delegations (for the user's wallet principal or app-specific principal) - accounts (instead of or in addition to delegations) - canister calls (i.e. ICRC-1/7 transfer ICRC-2 approve) We'll also present a utility package called Identity Kit (Rainbow Kit for ICP) to support all wallets without devs worrying about the nuances of which wallet/signer the user is using. #meetings" target="_blank" rel="nofollow noopener">github.com/dfinity/wg-ide…
English
1
11
48
3.9K
Weed/0 がリツイート
Motoko Bootcamp
Motoko Bootcamp@motoko_bootcamp·
Introducing the Open Internet Summer. A novel hackathon dedicated to super-fuel DAOs through: - Building in public 👷 - Sharing ideas and vision💡 - Exploring synergies 🌱 This summer we start by turning @motoko_bootcamp into a DAO. Read more 👇 @sebastien.thuillier/introducing-the-open-internet-summer-june-22nd-july-21st-2024-44615a3becb7" target="_blank" rel="nofollow noopener">medium.com/@sebastien.thu…
English
4
24
49
7K
Weed/0
Weed/0@weedpatchtwo·
Potential vuln? 1. Scrape open job applications 2. Generate applicant resume for this role (`$variable` different ways), 3. Apply with references to <target> in resume 3. Set top reference to <target> 4. ... ring ring 5. Profit?
English
0
0
0
117
ICP Community Conference
(1/13) ICPCC Content: Organized & Shareable Before taking time off to rest, we wanted to make sure you could share your favorite #ICPCC24 moments! Timestamps now on Youtube: youtube.com/live/qCDQKwOp9… In this tweet thread we'll also be sharing a few recently published videos: 👇
YouTube video
YouTube
English
11
35
86
5.3K
Weed/0 がリツイート
ICP Community Conference
ICPCC DAO LLC has officially been born!! 🐣 🦾 I am alive, and the #ICP community will be my voice! 🤖
ICP Community Conference tweet media
English
11
28
124
7.4K
Weed/0 がリツイート
dom williams.icp ∞
dom williams.icp ∞@dominic_w·
A world first: a demonstration of AI running *on* blockchain as a smart contract 🧠⚡️ The Internet Computer is used – the world's first 3rd gen. blockchain #ICP. AI will become the beating heart of our web3, multi-chain world, and this is only my first demo. Code will follow shortly. This is running on DFINITY's Internet Computer testnet, but you'll be able to take the code and run it on the public network as the NNS is expected to up the per-transaction instruction limit in the coming days. Some important notes. The inference engine used has not been optimized, and we will show vastly greater efficiency in subsequent demos, where the AI runs even faster, and consumes less gas/cycles. We will also propose to the NNS that smart contracts have access to SIMD instructions – which we have determined are deterministic – unlocking vastly more speed and efficiency. Lastly, currently the actor smart contracts ICP hosts run inside a 32 bit environment, which limits their main memory to 4GB. Within the next couple of months, we expect the Internet Computer to move to a 64 bit environment, allowing smart contract memory limits to be raised much higher – allowing for models with far more parameters, and thus power, to be run. Those of you who have followed my posts know that hardware optimization support is planned. Firstly this will involve WASM smart contracts shipping out matrices for processing by the CPUs on existing node machines (another advantage of the Internet Computer running on sovereign node hardware). Secondly, we plan to propose a new public node machine specification, which node providers can build to, for use in subnets specialized for hosting AI smart contracts, in which each machine will incorporate several GPUs. Naturally, this will be packaged with other technological developments that ensure smart contract determinism. This is part of our mission to enable powerful LLMs to run as smart contracts on the Internet Computer – in a forms that are tamperproof, unstoppable, and optionally autonomous (including under the exclusive control of DAOs). Our vision: you will be able to have a chat with a smart contract. A smart contract will be able to coordinate your organization (see my earlier tweet about a "Delphi"). ICP smart contracts will be able to audit Ethereum smart contracts, kitemarking those without backdoors and reentrancy bugs. And smart contracts will be able to do KYC autonmously, matching faces to driving licenses, and more. We will deliver new SDK enhancements, and work with partners, to turbocharge crypto AI developers. Secure and unstoppable AI and third generation blockchain will be two sides of the same coin. Security and AI will be indivisible. AI models will be traded as NFTs. Thanks to Internet Computer's chain key (trustless multi-chain) capabilities, all blockchains will be able to leverage AI smart contracts. The future is beyond exciting. Thanks for watching. Can't wait to give you more demos!
English
426
1.8K
3.2K
1.4M
Weed/0
Weed/0@weedpatchtwo·
Go preach. @lightning_lad91 is a GOAT. I've had the privilege of working directly with him, and his ethic is incredible. His vision is top notch, and you should be proud to have a Personal NFT of his. Imagine if Jesus had an NFT... WWJD, bud?
English
0
0
1
158
LightningLad
LightningLad@lightning_lad91·
#ICP friends - I’m at a crossroads and need some input from y’all. TL;DR - We’re buying a house and need to earn ~$30k over 8 months. I have 15hrs/wk of spare time available. - I can use this for overtime (stop work on current project) or - Raise funds w/ an quick NFT sale (continue work on my current project) Expand for more context 👇 I am currently in the middle of development on a Utility NFT that will allow developers to seek community donations in a way that protects the devs and their donors. Unfortunately, I’ve had to put that development on hold the last couple months so I could focus on a professional work project and some family matters. The work and family obligations have been met, but now we’ve been presented with an opportunity to build and become permanent residents in our current town. (Very limited housing options) I have to focus on taking advantage of this opportunity and so I’m left with the decision to postpone my development for 8 months, or see if I can raise the money now and continue developing my project.
English
9
1
21
6.2K
OpenChat ∞
OpenChat ∞@OpenChat·
To be clear! We will be using a third party for the video chat integration. 1-2-1 chat will go over peer to peer webrtc. Larger calls require a SFU (selective forwarding unit) to scale. We don't know of any good way to do this on-chain (at this time). We'll put out a blog post with all the details of how it works when we release. In the meantime, let us know of any specific questions/concerns you have so that we can include the answers in the post.
OpenChat ∞@OpenChat

🚨 Say cheese! Video chat coming soon! 🚨 #ICP #CHAT

English
19
30
137
11.3K
magICPoint ∞
magICPoint ∞@ASmagicpoint·
@lastmjs @demergentlabs @dfinity @dominic_w @aoTheComputer Thanks for this thread, very informative. I always thought of the rigid network architecture as being the "enterprise" subnets where you need similar performance to stay "in sync" and meet SLAs. My hope is "Badlands" to come with more heterogenous community nodes being possible
English
2
0
9
1.1K
lastmjs
lastmjs@lastmjs·
1/ Please take time to digest this and understand the nuances of what I'm about to explain It's too complicated to explore every possible implication and possible future here But here we go... ICP has a number of crucial weaknesses We need to pay attention to @aoTheComputer
English
44
69
273
122.7K