与「Ask_BLACKPINK」相关的搜索结果

🎁6월 30일 오후 12시 (KST) #블랙핑크# 와 함께하는 트위터 블루룸 라이브🎁 #Ask_BLACKPINK# 해시태그와 함께 트윗으로 질문을 보내주시면 블랙핑크가 라이브에서 직접 답변해드려요🖤💘 #Ask_BLACKPINK# #TwitterBlueroom# LIVE Q&A with #BLACKPINK#

Get ready for #NewMusicDaily# Presents BLACKPINK with @AppleMusic. Come celebrate the release of #THEALBUM# with us! Sign up for a chance to join & ask questions live. Reserve your spot (US Only): #BLACKPINK# #JISOO# #JENNIE# #ROSÉ# #LISA# #YG#

This is Farzapedia. I had an LLM take 2,500 entries from my diary, Apple Notes, and some iMessage convos to create a personal Wikipedia for me. It made 400 detailed articles for my friends, my startups, research areas, and even my favorite animes and their impact on me complete with backlinks. But, this Wiki was not built for me! I built it for my agent! The structure of the wiki files and how it's all backlinked is very easily crawlable by any agent + makes it a truly useful knowledge base. I can spin up Claude Code on the wiki and starting at index.md (a catalog of all my articles) the agent does a really good job at drilling into the specific pages on my wiki it needs context on when I have a query. For example, when trying to cook up a new landing page I may ask: "I'm trying to design this landing page for a new idea I have. Please look into the images and films that inspired me recently and give me ideas for new copy and aesthetics". In my diary I kept track of everything from: learnings, people, inspo, interesting links, images. So the agent reads my wiki and pulls up my "Philosophy" articles from notes on a Studio Ghibli documentary, "Competitor" articles with YC companies whose landing pages I screenshotted, and pics of 1970s Beatles merch I saved years ago. And it delivers a great answer. I built a similar system to this a year ago with RAG but it was ass. A knowledge base that lets an agent find what it needs via a file system it actually understands just works better. The most magical thing now is as I add new things to my wiki (articles, images of inspo, meeting notes) the system will likely update 2-3 different articles where it feels that context belongs, or, just creates a new article. It's like this super genius librarian for your brain that's always filing stuff for your perfectly and also let's you easily query the knowledge for tasks useful to you (ex. design, product, writing, etc) and it never gets tired. I might spend next week productizing this, if that's of interest to you DM me + tell me your usecase!

LLM Knowledge Bases Something I'm finding very useful recently: using LLMs to build personal knowledge bases for various topics of research interest. In this way, a large fraction of my recent token throughput is going less into manipulating code, and more into manipulating knowledge (stored as markdown and images). The latest LLMs are quite good at it. So: Data ingest: I index source documents (articles, papers, repos, datasets, images, etc.) into a raw/ directory, then I use an LLM to incrementally "compile" a wiki, which is just a collection of .md files in a directory structure. The wiki includes summaries of all the data in raw/, backlinks, and then it categorizes data into concepts, writes articles for them, and links them all. To convert web articles into .md files I like to use the Obsidian Web Clipper extension, and then I also use a hotkey to download all the related images to local so that my LLM can easily reference them. IDE: I use Obsidian as the IDE "frontend" where I can view the raw data, the the compiled wiki, and the derived visualizations. Important to note that the LLM writes and maintains all of the data of the wiki, I rarely touch it directly. I've played with a few Obsidian plugins to render and view data in other ways (e.g. Marp for slides). Q&A: Where things get interesting is that once your wiki is big enough (e.g. mine on some recent research is ~100 articles and ~400K words), you can ask your LLM agent all kinds of complex questions against the wiki, and it will go off, research the answers, etc. I thought I had to reach for fancy RAG, but the LLM has been pretty good about auto-maintaining index files and brief summaries of all the documents and it reads all the important related data fairly easily at this ~small scale. Output: Instead of getting answers in text/terminal, I like to have it render markdown files for me, or slide shows (Marp format), or matplotlib images, all of which I then view again in Obsidian. You can imagine many other visual output formats depending on the query. Often, I end up "filing" the outputs back into the wiki to enhance it for further queries. So my own explorations and queries always "add up" in the knowledge base. Linting: I've run some LLM "health checks" over the wiki to e.g. find inconsistent data, impute missing data (with web searchers), find interesting connections for new article candidates, etc., to incrementally clean up the wiki and enhance its overall data integrity. The LLMs are quite good at suggesting further questions to ask and look into. Extra tools: I find myself developing additional tools to process the data, e.g. I vibe coded a small and naive search engine over the wiki, which I both use directly (in a web ui), but more often I want to hand it off to an LLM via CLI as a tool for larger queries. Further explorations: As the repo grows, the natural desire is to also think about synthetic data generation + finetuning to have your LLM "know" the data in its weights instead of just context windows. TLDR: raw data from a given number of sources is collected, then compiled by an LLM into a .md wiki, then operated on by various CLIs by the LLM to do Q&A and to incrementally enhance the wiki, and all of it viewable in Obsidian. You rarely ever write or edit the wiki manually, it's the domain of the LLM. I think there is room here for an incredible new product instead of a hacky collection of scripts.

"I've always loved passing, it's always one of my greatest joys to get my teammates an assist... it's truly for me better than hitting a great shot." NBA Player Correspondent @Kon2Knueppel crashes KAT’s presser to ask him about his playmaking this postseason!

Last week, I attended the @ElonMusk and Jamie Dimon @SpaceX discussion at J.P. Morgan. Jamie asked Elon how he had changed over the past 20 years as a leader and a person. Elon's answer wasn't about success. It was about what's next. He said he has learned a lot...has made mistakes and still has much to learn... Then he added, “I think maybe the future AI will say ‘not bad for a human’." Elon, thank you so much for what you've done for humanity. Congrats to you, @Gwynne_Shotwell, @BretWJ, and the entire team. What is even more remarkable... this feels like day one, that you are just getting started. PS. When people ask "what is the next SpaceX and who is the next Elon?" Simple answer. There is NO NEXT!!! Elon Musk is a mensch!

Why do I often ask questions about illegal immigration, birthright citizenship, election integrity & fraud? Because if government doesn't make the sanctity & benefits of citizenship for our *existing* citizens its top priority, we're going to see a lot more of the forceful, understandable -- and deserved, IMO -- anger, frustration & uprising of "ordinary" Americans like this well-spoken gentleman as they reach the breaking point of their tolerance for being exploited