正在加载视频...

视频加载失败

This is actually true. When there are nothing much between teams, in any sport, crucial moments like these can swing the momentum. Just need a bad referee decision or a small time off due to player injury and boom the momentum changes. Although I believe losing to Springboks at...

24,034 次观看 • 1 个月前 •via X (Twitter)

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

Recently there was increased discussion about DMCA takedown requests being used in bad faith between competitors on Shopify. I can confirm that the volume of these has very much increased recently. Let me give you some examples of what we are doing about it. Our goal is to work within the DMCA’s framework and make a system in which the right things happen quickly. We want to give merchants the maximum time to respond with the minimum disruption. We also need legitimate claims to resolve in favor of the claimants quickly. The first thing we did recently is to productize this properly. We shipped a feature to manage these cases directly in the Shopify admin to make it a lot more obvious. Before that a lot was managed through form emails. This process is now much simpler and faster. The second thing we did is to make the identity system more robust so that we know more about the claims filed. We consider the claimants previous cases in order to decide what decisions to take. Similarly we consider documentation from previous cases that merchants had to deal with more strongly to make accurate decisions when repeat claims are received against products. If we detect bad faith claims from accounts we take action. We recently filed multiple lawsuits against claimants in court. This matches our aggressive stance when we see frivolous or bad faith patent action in which we had a lot of success invalidating bad patents. The end result of this is that we catch spammy or frivolous claims at much higher frequency already. We also make responding to cases much easier and this can be managed directly from the admin now and is less work for the merchants. Lots of additional improvements coming- but what I can guarantee you is that that Shopify will be the worst platform on which to make fraudulent DMCA claims on. “Be merchant obsessed” is a core value here, and we reflect that better in this area.

tobi lutke

142,265 次观看 • 2 年前

HTML Artifacts are a big part of how I work with agents now. Artifacts can be more than just static files. When combined with agents, they can take action or help you take action. This unlocks all kinds of interesting ways to work with agents. This is clearly the future. Check out this writing and scheduler artifact I built in a few minutes. It uses a bit of HTML and JS. All the data is in markdown (Obsidian vaults), so the agent can access and modify it at any time. No DB needed. No sophisticated functionalities. The agent decides all that for me based on the skills, context, and memory it has access to. The best part about this simple stack is that all the important information stays with me. This has allowed me to build a recursive self-improving system and automations that can better tap into coding agents like Codex or Claude Code. I could have paid or built an entire app for scheduling posts, and there are so many of them out there. But I don't need to. I've realized a simple artifact does the job. And the simplicity of it is actually an advantage. Very little maintenance for very high returns on personalization, time, and efficiency. The other benefit of this is that I can add features as I please. That level of personalization feels magical, and we should all be pursuing more of it. All of this just keeps compounding. Of course, this example is just about writing. But I have similar artifacts for research, design, experimentation, evaluation, and so much more. And no, I didn't actually publish the post example I shared in the clip. It was just for demonstration purposes. I actually spend more time than this when writing together with agents. Lastly, having built my own agent orchestrator tool has made me realize that simplifying the tool stack is a superpower. If you are curious about how all this works, I will do a live session next week:

elvis

18,374 次观看 • 4 个月前

Officially moving on from Tech game after I get this thought off my chest. I more than welcome anyone smarter than me in regards to the football to chime in. I truly, truly, truly cannot wrap my head around the thought process here. These two plays I'm sure anyone with brain can agree officially sealed KU's slim chances in having a chance to win this game. The play calling to me seems like completely flipped in logic at best? First one, you are down 4, on your own 30 so you are not going to go for this. Ignoring that we were getting dominated in the trenches in this game and that the 'obvious' play is a run, I don't get why we make the decision in a must get spot to take the ball out of our QB's (who at the time was rolling) hands. Jalon Daniels is our best player. In an absolute must get/need, we should be relying on him to make a play. Then the second one. I obviously don't know the answer here, but I feel somewhat confident that the reason we didn't run here was because of how the earlier 3rd & 1 run went. While I don't necessarily agree with the premise of decision making on this alone, I can appreciate the recognition that we are going to struggle to gain a yard in an obvious run situation. But the thing is, we are in go for it range so the one thing you absolutely cannot have is a massive negative play. Literally anything else is okay (obviously not a turnover). I truly don't think there's a good chance we run the ball on this attempt and get a yard. But THIS situation gives you a free shot at it if you want to take it. I think this play call would have worked if we didn't let their best player run at our qb freely but I'd just argue this play had a ton of potential risk that wasn't necessary. Hell even a play action pass out of out shot gun or something rolling JD out to the left would have given us a good shot at first down with an escape route to bail out on the play if something went wrong. I'm once again for the millionth time saying I know and understand that this entire staff knows more about football in their pinky than I do. But I do think the game has evolved and game + clock management doesn't really require football knowledge/have a direct correlation to one's football knowledge. It's not as simple as ESPN's graphic says GO so you should go etc, there are variables and human behavior etc to deal with and I understand that. But we are just getting these situations downright wrong. We are flipping a coin that has a 20 pound weight attached to the heads side and calling tails almost every single time. S/O anyone who read all this but would just love some insight if there's anyone who disagrees and is a lot smarter than I!

Bryson Stricker

33,876 次观看 • 11 个月前