Загрузка видео...

Не удалось загрузить видео

На главную

What if candlesticks weren't just data points on a timeline but nodes in a living network? Visibility graphs do exactly that. Take a rolling window of price, connect every pair of bars that have unobstructed geometric line of sight to each other, and you get a graph a real...

44,699 просмотров • 5 месяцев назад •via X (Twitter)

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

🛜 Remember LAN parties? I do LAN means "local area network" and it was essentially the internet but locally only in your home or company in the late 90s and early 2000s So you could connect to other computers to play games or share files, kinda like Airdrop but via a cable and 30 years ago, people would even meet up at some person's house and bring their entire computer (back then a big PC tower, CRT monitor, keyboard and mouse) and everyone would connect to each other Which is were you'd get all the WaReZ games, MP3 music, etc. cause nobody had internet yet, or if you did it was super slow, so LAN was much faster to transfer files I know Windows 3.11 did have support for LAN networking via NetBEUI and it "should" work, but of course on I don't have a network cable that goes to an Ethernet network hub to other computers But...we could just act like we do? I asked AI to build a virtual Ethernet hub (a hub routes traffic) that acts like a local LAN, but instead of connecting physical computers in a home, it connects other browser sessions on the internet that have running Windows 3.11 open at any time, and with DHCP it can assign an IP to every browser session dynamically, so they literally all become part of a local LAN on the internet! It runs on a virtual NE2000 network card that sends its network data not to a network cable but via Websockets to wss://pieter.com And it works, well kinda, I just started and its' not perfect, but I'm able to PING in MS-DOS from one tab to the other! Next is setting it up inside Windows 3.11!

@levelsio

217,281 просмотров • 2 месяцев назад

context engineering vs graph engineering. every few months the list gets a new word and everyone treats it as a replacement for the last one. these two are not on the same list. one decides what the model sees this turn, the other decides what exists at all. the cleanest way to tell them apart is to ask what a single unit of work looks like. > context engineering is the window the window opens empty, every single time. you assemble what goes in it. the prompt, the docs, the history, the tool results. the assembling is the work. the window only grows. it never shrinks on its own, so eventually something gets dropped. usually from the middle. usually without telling you. then the turn ends and the window is thrown away. not archived, thrown away. the next turn opens empty again and you re-explain what you already explained. good context engineering is knowing what to leave out, not what to pack in. the unit of work is one window. > graph engineering is the structure the same material arrives from the same sources. instead of packing it into a window, you pull entities out of it, resolve the duplicates into one node, and write typed edges between them. nothing here is stored as text you hope to find again. it is stored as a thing with a name and its connections to other things. when the turn ends, the graph is still there. the next turn does not start from zero. it starts by querying what already exists, and the query walks edges instead of guessing at similarity. good graph engineering is deciding what counts as the same thing twice. the unit of work is one relationship. > they are not alternatives the graph is what refills the window. context engineering decides what fits. graph engineering decides what there is to choose from. remove the graph and every session starts blind. remove the context work and the best structure in the world arrives as an unreadable dump. that also tells you which one broke. the answer drifted from what you actually said, or forgot something from this same session. that is the window. the answer is coherent but invents a connection that does not exist, or cannot join two facts it has clearly seen. that is the structure. people debug the prompt because the prompt is the easiest thing to edit. it keeps taking the blame for failures that live a layer down. save this - then read the full breakdown below

Hanako

19,160 просмотров • 1 месяц назад

Loops vs. Graphs, clearly explained! loops are great, but they have a ceiling: a loop makes one unit of work better. it cannot decide which units exist. so you end up with a very good agent running the wrong three steps, in the wrong order, one at a time. Graph engineering fixes this by moving the decision up a layer: what runs, what runs at the same time, and what never runs at all. you need both. here's how it works: a graph splits your system into two kinds of decision. ↳ inside a unit: the loop. produce, check, correct, repeat until green ↳ between units: the graph. split, fan out, merge, gate, send back Prompts → Context → Harness → Loops → Graphs you get parallel work, isolated contexts, and steps that stop running when nothing needs them. the trick is being selective about what becomes a node. only spend a model where judgment lives. merging, ranking, deduping and schema checks are edges, and edges are code. free, instant, and they cannot be argued out of a verdict. a graph where every edge is an agent pays rent on its own wiring. one thing to know before you scale it. a graph has two return paths, and almost everyone builds one. ↳ the correction edge is short. a gate rejects one unit back to the step that produced it, and it fixes the run you are in ↳ the learning edge is long. an accepted result goes back to the splitter as a constraint, and it fixes every run after skip the second and you get a graph that is fast and never gets smarter. next week it starts from the same place with the same blind spots. and a smaller one that eats whole nights: when a unit fails, return that unit, not the batch. send back four slices because one failed and you have just rewritten three correct ones. do it twice in a run and the run never converges. below i have quoted my full guide on graph engineering. it covers the three topologies, the verifier patterns, and where the gate should actually open. save this and read it below ↓

Hanako

73,867 просмотров • 18 дней назад

Build better RAG by letting a team of agents extract and connect your reference materials into a knowledge graph. Our new short course, “Agentic Knowledge Graph Construction,” taught by Neo4j Innovation Lead Andreas Kollegger, shows you how. Knowledge graphs are an important way to store information accurately but they are a lot of work to build manually. In this course you’ll learn how to build a team of agents that turn data– in this case product reviews and invoices from suppliers–into structured graphs of entities and relationships for RAG. Learn how agents can automatically handle the time-consuming work of building graphs — extracting entities and relationships (e.g., Product "contains" Assembly, Part "supplied_by" Supplier, Customer review "mentions" Product), deduplicating them, fact-checking them, and committing them to a graph database — so your retrieval system can find right information to generate accurate output. For example, you can use agents to help trace customer complaints directly to specific suppliers, manufacturing processes, and product hierarchies, thus turning fragmented information into queryable business intelligence. Skills you’ll gain: - Build, store, and access knowledge graphs using the Neo4j graph database - Build multi-agent systems using Google’s Agent Development Kit (ADK) - Set up a loop of agentic workflows to propose and refine a graph schema through fact-checking - Connect agent-generated graphs of unstructured and structured data into a unified knowledge graph This course gets into the practicum of why knowledge graphs give more accurate information retrieval than vector search alone, especially for high-stakes applications where precision matters more than fuzzy similarity matching. Sign up here:

Andrew Ng

168,153 просмотров • 1 год назад

This info about META will BLOW YOUR MIND American “I worked in IT for like 13 years” “I learned a lot about data privacy — and social media and what apps are notoriously bad when it comes to data privacy. At the very top of the list, the worst offender, the worst app for data privacy is Facebook Messenger” “Let me just explain this to you. If you have Messenger on your phone and you don't have any other apps by Meta, you don't have Facebook, Instagram, threads, nothing. If the only thing from Meta you have on your phone is Messenger and you connect to a WiFi, Messenger makes a map of that Wi-Fi network. - It collects information about every single device that is connected to that network - So every phone, every computer, every tablet, every printer, every camera, every thermostat, every smart TV, every Roku device, and on every single one of those devices - They're collecting the name of the device, the IP address of the device, what type of device it is, whether or not your device has access to that device And this doesn't just happen on your home network, it happens on every Wi-Fi network you connect to. —- And it's a lot more information than just, oh, there's 200 devices connected to this network. No, it's detailed information about every single device. Like, here's a mobile device connected - it's an iPhone - It's titled Jeremy's iPhone - It's running iOS version blank blank - Its IP address is blank blank blank blank - Its MAC address or its hardware ID is blank blank blank But they also collect a crap ton of information from your actual phone. Like - The names, phone numbers, email addresses, and social links of literally everyone in your contacts. - Your location history - Your browsing history. - A detailed list of every single app that you've ever installed - YOUR PASSWORDS - YOUR FINGERPRINTS - YOUR FACE ID Spoiler alert, it's not. Downloading Messenger means that you consent to their terms of service. You give consent just by downloading the Messenger app. Using the service and downloading the app gives consent. Consent for your phone to be used as a data collection device. To collect data about every place you go and every person you're in contact with. — Messenger is easily the worst one”

Wall Street Apes

215,676 просмотров • 1 год назад