t2r3121

Every time I try to use the platform feature I get it working well in one or two browser on either desktop, android or iOS and then later find out it works pretty badly on one of the other platforms

For visual and SAR, sure, but there are other missions like electronic warfare and signals intelligence that are still well served by aircraft.

1. The audience changed. Billions of people came online in the 2010s on smartphones, streaming works better for them.

2. For most people bandwidth did not increase at the same rate as video file sizes during that period, streaming could do smart things like serve transcoded media sized to fit your screen and internet connection. It's only recently with HEVC and AV1 that video file sizes have caught up.

3. Streaming can be easily monetized, p2p generally cannot.

I only charge my phone at my office desk typically. So I'll go a whole weekend without charging.

The CGNAT problem is solvable in the majority of cases via multiple solutions (tailcat/DERP, for example), but that certainly doesn't make a mobile connection's upload any better for sure.

Peer to peer died because (1) a lot of the world, especially outside the US, has terrible upload/bandwidth, (2) HTTPS CDNs got _really_ cheap, far cheaper that p2p technologies like BitTorrent+WebSeed.

There are a minority of users who care about being able to host videos that violate YouTube/TikTok/Instagram policies. Unfortunately, a significant part of that minority is working with infringing or illegal content, which both prevents ad networks from working with you and attracts attention from law enforcement.

Yes, the article also points out that the idea is not new, but rather that this research was focused on addressing practical problems, such as corrosion of the engine's parts.

> GPS spies on everyone.

Point of clarification - GPS/GNSS does not work that way. The GPS in your phone only _listens_ to GPS signals and is not transmitting to/observable by the satellite. https://ciechanow.ski/gps/

Only local tyranny, like the county government.

Because the hard part of running it is making it highly available despite the inherent fallibility of distributed computing, which is an infrastructure problem, not an AI coding problem.

Temporal is fully open source, you can run the entire thing on your laptop or your own server. People pay for the SaaS anyway, because dealing with the distributed computing problems is hard.

(There are some other projects inspired by Temporal as well, but if you want to run something in-house, you're probably funding a minimum of 2-3 engineers to handle on-call, and for that price the SaaS is competitive).

The less-technical staff I mentioned would have wanted visual design, not text files.

Sadgely, this is a throwaway account that I don't want linked to my identity

Temporal doesn't run your AI compute for you, you bring your own hardware on prem or in your cloud account or whereever. Their SaaS is a control plane to coordinate and orchestrate the workers.

Another cool thing is it handles version rollouts. Say a customer started some kind of business process on v1.1 of your code, and then you deploy v1.2. You can configure whether that customer should continue that process on v1.1 - even if it's something that takes a long time in the real world - or whether they should be upgraded to 1.2. And it's not just one version but you can do this with an entire rainbow of versions across your business (think A/B testing, custom workflows for different use cases, lots of dev and staging environments, etc.)

When you write traditional distributed systems/cloud native code you have to handle all the failures and retries somewhere. Anyone who's run an Ansible playbook or similar and had a failure halfway through leave the state of the systems in a weird half-state is familiar. Or dealt with spot preemptions or nodes failing or getting unlucky with OOM killer or hardware failures or a myriad of other failure modes.

In Temporal, you use their SDK to mark which code is either:

- Deterministic without external dependencies on network, disk, clock, etc.

- Non-deterministic (e.g. accesses a filesystem, dependent on clock time, talks over the network)

You can write the code without handling flakiness or retries and the Temporal control plane handles all the progress tracking and retries for you. Progress is tracked at the individual line of code for deterministic code, or for non-deterministic code, tracked at function boundaries defined by the programmer. You buy into more complexity upfront, but it makes the application code way simpler and easier to manage overall.

They do a lot of other cool stuff on top of all this, and their Temporal Worker Controller architecture is particularly well suited to running massive scale processing/AI workloads on Kubernetes (handles a lot of stuff like autoscaling without interrupting work, rainbow version rollout, etc.)

I use Zed (https://zed.dev) as my agent harness and either the $20 ChatGPT sub + Sol for personal/independent projects or an enterprise Claude account for sponsored/paid work. From the stats for my current work I use about $400/mo in tokens and a lot of that is non-coding work like pruning JIRA, managing business documentation, making dashboards - so my true coding agent cost is significantly less.

It's pretty simple, you could probably set up something like that by:

Configure some kind of CLI tool to talk to your ticketing system and git repo so you can programmatically interact with them. If you don't have a ticketing system, instruct the agent to use local text or markdown files to track issues and progress.

Ideally, make your code runnable in a way the agent can use. For my webapps I build a test harness so that I can run all the endpoints and workflows via reproducible tests against an embedded database. This is easier than it sounds, e.g. there are libraries out there to embed PostgreSQL or SQLite into source code, you can set up a test harness so you can run unit tests, integration tests and workflow tests that use your real frontend, server and database.

Paste this comment thread into the agent prompt and tell it to run a similar loop on your code base: a session that searches for vulns and writes up a report, some way for a human to do a review pass on the report, a session that indexes the reviewed findings into tickets, and sessions that fix the fixable issues and submit patches to your repo. The next search session should first read all the open issues so it doesn't duplicate work of earlier sessions.

LESS IS MORE - avoid fancy agent tooling and skills, don't cargo cult from others, build your own tools as you find your own needs. If something can be automated, use the agent to write tools and tests for it, don't just keep prodding the agent to do it.

I used to ask this question back ~2015 - I was seeing companies with massive, clunky CMS installs just so their non-technical/less-technical staff could update their websites without filing tickets to IT/dev. It seemed to be more about those departments wanting autonomy and not having to wait weeks or months for internal IT/dev to make site updates. The consensus within one dev group was that the company would have been better served by hiring someone who knew HTML/CSS/Javascript to embed with the non-technical people and edit a straightforward frontend site for them.

I mean... you can literally do that now. You can set up a loop to iteratively pentest, review and patch a codebase (with human supervision as you prefer) and it'll find and fix more vulnerabilities in a day than a pentest team used to find in a quarter, for a tiny fraction of the price.

This isn't a joke, this is now part of my pre-launch SOP. I even have it tracking everything so I can log stuff to fix vs. known shippables vs intentional design/false positives vs. upstream stuff which doesn't have a fix available yet, and keep track of which builds have the fixes. Almost entirely automated, I mostly review the findings and do some categorization/enrichment during the pentest review stage, and do a human code review pass as patches are submitted.

Stuff that used to take me multiple hours to write a fix for and then weeks to get code reviewed and deployed now get done in minutes.

IKEA has made video games for a long time: https://store.steampowered.com/app/447270/IKEA_VR_Experience...

A human driver can't tell. I've had gun guys mistake my airsoft guns for real ones. Average person who isn't familiar with both real guns and airsoft has no chance.

I own airsoft (pellet) guns people have confused for real ones when I left them on a shelf in my house. If you don't know what to look for they look quite convincing these days. Take a look around https://www.evike.com/airsoft-guns/ - everyone deletes or spray paints the orange tips because they make you really visible on the airsoft field.

It's a direct ripoff of https://scp-wiki.wikidot.com/scp-3008, a popular sci-fi horror story set in an IKEA. At the time the game was also using IKEA's brand colors.