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
What do the engines have to do with plasma around the hull, or rather its leading edges, caused by supersonic speed, which never ever even enter them?
And if you're thinking of the exhaust, why would that matter at all for signals reception and transmission, with the exception of a small cone from right behind?
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.
It's much more of a storage space problem and a device running 24/7 problem. With the desktop of yore you can just leave them running and attach cheap HDDs to them for media storage. Nowadays, most people have laptops -- which are explicitly closed for most of the time -- and phones -- which doing 24/7 upload on will kill your battery life. And neither support 3.5" HDDs.
BitTorrent is certainly built around the idea that upload can be slow. Even if user have upload 100x worse than download, 100 seeders can saturate a leacher, and then the leacher becomes a seeder.
The problem is just that he doesn't stay a seeder forever, because of the other problems.
Phones are charging ~8 hours a day whilst you sleep though. And few people mind the phone seeding stuff on your home WiFi whilst charging. Many users could also spare 32gbytes for seed data too, especially if the app was smart and automatically reduced the store size before the phone started to notify you of low storage space.
If a typical user uses preertube 30 mins a day, that still gives a 16 to 1 ratio between seeding and leeching, and a 1024 to 1 data storage to data viewed ratio, meaning there is a good opportunity for a big back catalogue.
YouTube, Instagram, and TikTok (especially) are becoming stricter and stricter about the kinds of content they allow to exist and spread on their platforms. Right now I think an alternative is non-viable but it's increasingly possible that won't be the case in the near future.
3- Also, this is rebroadcasting, technically a textbook definition of piracy even when that content might normally be obtained for free, especially if the content began encrypted.
(Because some laws are stupid. Please support right to repair and DMCA reform.)
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.
Yes, because the amount of pirated content floating around was not 1/100th the amount that is out there now, and obtaining content is easier than ever. Especially when you have a sanctioned "library" that hosts it all for you for free.
And we haven't yet found a way to solve recommendations for full P2P networks without making them trivial to game via sybil attacks. This makes truly decentralized P2P unusable in ways most people use Youtube.
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.
Meh - you can block ports inbound without state tables. I think you're ascribing purpose to what i imagine is a sclerotic and dysfunctional entity.
When i was 20, i was reflexively cynical, because it let me pose as intellectual without the burden of having to learn or think. As an adult, i find that pose very fucking obvious.
My interest was piqued by the concept of natting ip6, and why an isp might do so, and why cgnat might be disabled if you ask the isp to disable ip6.
...bb-but I thought cynicism was the same thing as experience![1]
No but seriously, I agree it is primarily "we can't be arsed to change our methods".
"Primarily" is not everything; the other 10-20% is the long tail of everything else. Europe is getting much harder on filesharing[3][4] because of business interests, and - despite the much better regulation - there's probably some "you shouldn't be hosting things on a residential connection anyways, pay us for a business connection peasants" like in the US[2].
Of course, all these ready-made restrictions are then easily adaptable for abuse (when's the next Chat Control proposal anyways?), so there's not much pushback from above...
Cynicism is easily a thought-terminating cliche, but it is unfortunately earned nowadays, especially as a coping mechanism for a feeling of helplessness against the usually stupid, sometimes malicious forces at play (Hanlon's Razor doesn't account for weaponization of stupidity).
Sure, but cgnat doesn't defeat filesharing, because of your STUN and your DERP and what-have-you.
It's common, at least in the UK, for residential lines to block smtp inbound. That's an ACL, which is operationally ~free. NAT does not serve the purposes you've outlined.
Some cynicism is warranted about, e.g. chat control, but it's better explained by good-faith desire to fight egregious crime coupled with low care for the privacy invasion. Other people have different values to you and me.
It's hard to reconcile an EU government in anyone's pocket with gdpr and dma, which afaics serve citizens and no big interests. Like most governments, the EU is somewhat fractious and incoherent, so it's not a given that everything they do is citizen-friendly. But i, for one, accept that law enforcement should exist; accept that this is inevitably a trade-off against citizen rights; concede that preventing the next bataclan is nigh-on impossible; and understand why some might, to that end, desire greater power to comb through conversations. I don't agree, but i also don't need to assume conspiracy. At heart, the problem is not that all government is evil - although you're welcome to that view - it's that thick pillocks vote without any consideration of nuance.
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.
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/
I was in NYC during a no king protest, it was the lamest public demonstration I ever experienced given how bad the circumstances are. On a weekend, everything was done after ~2-3h, then back to work as usual on Monday. If you miss that short period of time you wouldn’t even notice something happened.
If there is one thing you can all learn from Europe is how to do a protest that cannot be ignored by your administration
Trump wants the violence. There's a difference between protesting a government that will follow the rules even if the people don't, and protesting a government that won't follow the rules even if the people do.
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.
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).
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 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 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.
I remember Facebook's corporate news sites [1] were running on WordPress.
In most web frameworks its not terribly hard to extern content (you probably do this already for translations) and just have a nice little yaml or json thats easily edited.
reply