1,301 karma · joined April 20, 2015
Some suggestions for this to be able to succeed:
- Documentation, documentation, documentation, the only place where I could that the three supported ways to write a serverless function are with Go, Rust and AssemblyScript is somewhere hidden in a tutorial. It all has to compile to WebAssembly so I guess that's the limiting factor.
- Examples?
- Using git as source of truth for the configuration/state of a system is cool. Please link to sample repos so I can see what a system with a website, some functions that touch DB and files, and the configuration etc looks like.
- How does the database part work? Client SDKs?
- There are lots of protocols with unclear names that are only briefly mentioned here but then seen in random places in configuration: https://tau.how/01-getting-started/01-local-cloud/#protocols
- The Concepts part of the documentation is buzzword soup, it's impossible to derive any meaning from it other than that the author dislikes Kubernetes and probably used some generative AI for the content.
- Roadmap, plans, versioning, plans on how Tau version upgrades should go, ...
I just found this after seeing a note from corepack about updating our pnpm. This is perfect for our workspace. We have a JS monorepo with ~20 packages and currently use syncpack to keep versions of most packages in sync, but this looks far nicer and we will be fine with just a default catalog.
Not having to see "typescript": "5.5.3" in 15 package.jsons and similar in PRs will be nice.
It's unlikely we'll see any admission on why exactly the vote was withdrawn, but it's probable that the situation became untenable for the political parties involved, one of which lost massively in the Belgian elections about two weeks ago.
In an short interview in De Tijd [1] with one of the Belgian MEPs pushing this (Hilde Vautmans, OpenVLD, liberal, lost big), and another short line in De Morgen [2] from outgoing Belgian Minister of the Interior who was part of the talks for this new version (Annelies Verlinden, CD&V, Christian democrats), both of them made it appear like they mostly just care about getting it done (because nobody else has succeeded yet). There is a lot of "but think of the children", and zero technical expertise.
This morning, after the press attention, high rank party officials across the spectrum (and from the parties mentioned above) publicly called the proposal dangerous, so it's likely the pressure worked this time.
Next time this can come up for the vote will likely be from Hungary. They are taking over the EU presidency in a few weeks, and have already said this is on the agenda for them. Considering the current political climate there I would assume they are more likely to bring it to a vote, but hopefully that vote is less likely to succeed. Still, there's no time to rest, the proposal isn't dead.
[1] https://www.tijd.be/ondernemen/technologie/fel-privacyprotes...
[2] https://www.demorgen.be/snelnieuws/verlinden-buigt-voor-luid...
The best I can come up with is that domains used like this should really have TLD level protection from resale. With email so often being the key to a whole account, letting the access to that be put at risk by an IT admin letting a domain expire or an organisation simply forgetting about an old domain is kind of insane.
Meta has a small collection of tools on AWS to deal with large SEV0 events like these. Another one of them is a basic communication tool that does not use Meta's own servers for anything (including auth), a super basic version of the internal SEV tool.
The CCS adapter used here not working basically tells you the Cybertruck doesn't want to talk CCS yet. A CCS charger with a Tesla adapter is essentially equivalent to what NACS will be. This also means that as it currently stands the Cybertruck won't be able to charge on non-Tesla NACS chargers without an update.
On Superchargers this is not relevant. Superchargers can talk Tesla's own protocol (which is not in NACS, and is CAN-based) to the Cybertruck and can talk the NACS/CCS protocol (PowerLAN) to NACS cars / CCS cars with an adapter.
There was an internal search provider (bunnylol) that had tools like putting @od in front of any FB URL to generate a redirect of that URL to your currently checked out On Demand server. Painless to work with! Nice side benefit of living on the same domain as the main sites is that the cookies are reused, so no need to log in again.
I can't say it's the case for OPs case specifically, but I absolutely saw code that automatically closed tickets in a specific queue after a random(15-75) minutes to avoid being consistent with the close time so it wouldn't look too suspicious or automated to users.
A quick document.querySelector('#player').style = '' in console allows proper fullscreen viewing.
I got to use it at work at Meta (as end user), and it seemed to work quite well. They delivered Android SDKs/IDEs and a bunch of other things that I'd personally install through Brew with Munki.
Even as a Meta employee I remember it taking multiple months after moving from Europe to the US before I could use US-gated products (late 2020/early 2021).
This feels more like someone went skydiving with a homemade parachute in strong winds above an active volcano.
So yeah, circumstances.
I didn't realise how much I'd miss the driving when I moved back to Europe and switched back to a not-insane income level.
The longest one has been a 4400 mile EV (CCS) roadtrip in 2 weeks in July 2021, taking me from Seattle to Yellowstone to Arches to Big Sur and back.
Now that I'm back in Europe and no longer own a car it's probably the one thing I miss most about living in the US, the amount of unseen roads available to go drive on.
Amazon settled for this domain that should make everyone think "phishing?", but people will probably get used to.
- Amazon announcement: https://www.aboutamazon.eu/news/amazon-prime/amazon-com-be-l...
- Some press: https://www.retaildetail.eu/news/general/amazon-now-launched...