kj4ips

It's still patent encumbered[1], NACS just gave the physical specification, and says "use CCS HLS". The Tesla-SC protocol is still a black box. I wonder if this is going to involve a rollout of logical CCS on existing SCs.

[1] Tesla's patent pledge is not even close to a grant and its "good faith" rules almost certainly exclude all current major automakers.

I run a gitea instance on a moderate SBC backed by a NAS over iSCSI.

The SBC runs updates weekly, rebooting as needed as per zypper ps. It takes about 2 minutes for a reboot cycle, and reboots about 50% of the time. During this, the service is hard down.

The NAS selfupdates roughly monthly, and it takes about an hour. The service is stopped during this time.

This gives me a "perfect hardware" uptime of about 99.8.

I've had a single hardware failure in the last year, but it had the service down for 3 days waiting on shipping for a part, which gives an empirical hardware of 99.17.

I've not had any major maintenance on this setup in the last few years, though I expect to replace the NAS's drives in stages over the next few weeks. However, for a best-case, I'll give it 100.

My internet has not gone out in 2.5 years, so I am going to give it an optimistic 100.

My power, however, has been out for a total of 30 hours, of which, 28 hours outlasted my UPS. Based on syslog from NUT calling shutdown, until the first timestamp on reboot, therefore I have a Grid+UPS power availability of 99.68

If we compose all these, we have a total uptime of 98.65 of total services, which is far less reliable for basic operations (git cli interactions) than any of Git(Lab|Hub), Bitbucket, SourceHut.

This only covers all services down cases, my single-system setup doesn't often partially fail, and isn't engineered to hide maintenance (and doing so would be far out of scope and budget). Large services tend to fail partially, as they are composed of many individual systems with varied duties, and the system is often designed to fallback to basic function in the event of failure.

Not to even mention the question of capacity, which my 4c 8t of amd64 comes nowhere close to the CDN-ish power of the major SaaS's in this space.

Interesting, I honestly had expected that was already the case over there, with how expensive rapid charging is compared to residential rates on this side of the pond.

I guess our cheap prices for both oil and energy (in the us) might make us an anomaly.

It's all relative, EVs have the potential to be greener than their alternative, but actual public transit and non-powered transport are always going to be better where they are available.

It's all too easy to disregard "good" solutions because they are not "perfect".

Even when I lived in range of the local public transport, it's 1/hour frequency, limitations on baggage, and limited hours meant that I pretty much only used it as an alternative to walking back, since it was marginally faster, and climate controlled. It's miles better than nothing, but it still pales in comparison to access gained from the use of a personal vehicle.

Having read the above, I definitely agree that the Hummer EV is an exercise in American excess, just like the H1-H3 before it. I'm personally in the favor of miles traveled method, with modifiers for curb weight and anything else that impacts the intended uses of said tax. Specifically, I'd like to see an odometer based system charged at tag renewal (or in arrears, to make it more predictable).

Then reduce&repurpose the current gas tax for uses to mitigate externalities caused in post-sale use.

I'm also in favor of a similar externalities penalty for electrical generation (even though the current state of combustion generation is much cleaner than a typical ICE), so that economic forces are able to operate taking that into account.

I agree heartily. In order to gain access to "good", reliable internet, I had to move to the former "new-money" part of town, which is now pseudo-affordable. There is extremely limited non-vehicular options. The road out of the subdivision has zero shoulder, a one-way bike lane, and no sidewalks. Local residents don't respect the pedestrian easement, and ignore the posted speed limit across low visibility hills. The times I've walked that route, I've either been threaded with violence for "trespassing" or almost struck by vehicles. Never once has the bike lane or easement been unobstructed the whole way.

Other parts of the subdivision connect to a "greenway", but it is very broken up with missing sidewalks, and only has limited crosswalks. It really is only useful for getting to a nearby park (which is nice), but not for any essentials.

Some of the local residents (including myself) have been asking the city for some funding (or even to take advantage of grants) to improve the walk ability, but there is a smaller contingent of more influential folks that either threaten lawsuits should the city install sidewalks/walkpaths, or just take up tons of time so that everyone is tired and wants to go home by the time we get to speak.

While we've gained some visibility and good rapport, we've not really managed to change anything, and it's starting to feel futile.

In my state, they just raised the "EV tax" on registration from $100 to $300.

I have mileage records, and even using today's gas tax rate, (which will cause an overestimate) I never paid more than $225 a year, and that was a year 30% above average, and with the lest efficient vehicle I've ever had. 2020 was $80, and if I scale for the mileage I had in a typical year, that comes to $144.

The state gov't came out saying that it was based on the average amount people pay, but the numbers they provided used MPG values so low and mileages so high, you'd think they came from a motorhome doing the coast-to-coast tour.

That's quite a bit of kitchen equipment, sounds like they're removing a kitchen, and a few espresso setups.

They are also selling a bunch of sit/stand adjustable desks and large displays.

IMO, Nintendo has always been a bit behind on hardware, and most of their draw is the exclusive titles.

I have both a switch and a steamdeck, and if a game is offered on both, I'll buy the PC/Steam version.

The deck is larger, but actually fits quite well in my large hands, and I'm quite impressed of the amount of games that run well on it. It's not a replacement for a true gaming PC, but it's access to the existing steam library (and other PC games if you are clever) makes it quite an offering.

The devices have majorly different target markets, which makes it hard to compare them.

> but an issue I see is that users are now only able to get ports through the init system

The capabilities can also be specified by a fs attribute using setcap(8). This works like setuid, in the the capability is set whenever the file in question is exec'd. *

> Only root can restart a systemd service right

By default, only root can manage system-level systemd services, however, you can add policykit rules to allow specific users (or groups) to perform actions on specific services.

* Certain sandboxing techniques will break this (like no_new_privs)

I always assumed the expiration date on card was somewhat of a holdover from before online transaction verification was the norm. The bank would assuredly refuse to renew a card that was in default, so the user couldn't just keep using it at merchants that were still using paper slips.

Though a new account number is not quite as much of a big deal as it may seem. The issuers publish lists of old->new mappings, so that processors and merchants can update records, and some networks/issuers will accept reoccurring transactions on old numbers, as long as those were started before the number was issued.

It's kind of amazing what the issuers and networks will accept.

It depends, I've got some junipers that only pass the application processor the first N bytes of a packet, and even captures are limited to the first N bytes. Vendor docs say that if you need captures, you should do them on the switch, or use DPI and route everything through the application processor.

My understanding is that a human is //supposed// to be observing the vehicle the entire time that smart summon is in use, hence why the end-user has to hold down a button on the app the entire time the vehicle is in motion.

My understanding is that smart summon operates on a completely different set of rules than navigate on city streets, even though they might share some common functionality, like object detection and mapping.

The main difference is that not all credits are refundable. If you have a $7500 nonrefundable credit, but only have a tax liability of $5000, that extra $2500 just vanishes.

I vaguely remember a pizza delivery company facing a fine, because its website actively broke screen readers, and therefore was considered as discriminating against the blind.

Memory says a blind would-be customer complained loudly, but was ignored before they engaged the authorities with a formal complaint.

Sounds like a case where formal methods might be both appropriate and funding might actually be available for that.

I personally disagree. I live on the extreme west end of a time zone, and I greatly enjoy having an more daylight during my after-work leisure time. Without DST, I would have almost no post-work sunlight outside of the actual summer months.

I remember being bitten my `which` on Solaris not giving return codes. I was not yet aware of `hash` or `command`

At $PREVIOUS_JOB, I tried to maintain dotfiles that could be used on Solaris and RHEL interchangably, and I had a bunch of conditionals for enabling various completions.

We've done some pretty f'd up stuff to folks of color in the past.

One of the most notable examples is that of the Tuskegee study on untreated syphilis, where we denied effective treatment w/o informed consent.

PoC have higher infant mortality rates, and the myth that PoC have more tolerance to pain (and therefore require less anesthesia) is still quite prevalent.

It was bad enough that we had to actually produce a report on what is considered the "bare minimum", but even that has not been totally effective. (https://www.hhs.gov/ohrp/regulations-and-policy/belmont-repo...)

This is most likely a problem with this specific smart contract, from what I understand, if the EVM on the "winning" miner were to produce a state transition that did not faithfully follow the SC, that block should be rejected.

Polygon is a little different, due to its proof of stake system, where there is no "winner" and the validators (Heimdall instances) "check" the work of the actual block producers (Bor instances). It also has a slasher-like element where only one Heimdall instance needs to prove that a block is incorrectly executed for it to be rejected, so a malicious actor would need to compromise all active Heimdall instances to be able to lie.

That's where most of it comes from in the US, interchange rates on credit cards are not regulated, so they're generally somewhere around 2%.

Which, coincidentally, is the benchmark for "decent" credit card rewards.

Some cards will offer rewards on certain kinds of purchases, often up to 5%, but offering only 1%, or nothing for other purposes.

Since the average person only has a single credit card, the majority of cardholders produce more in interchange fees than they collect in rewards.

There's also some complicated accounting voodoo that I don't truly understand, that effectively means that banks can treat extended credit as a pseudo asset, plus, whenever alone is outstanding, it's value is added to the virtual money supply.

It is possible for an individual customer to get significantly more in rewards than interchange, but as this is a relatively small portion of customers, most issuers do not seem to care.

It looks like the way the license is written, they would have to release the source of the entire AWS console, and possibly everything that is AWS.

IMO, the SSPL's cloud provision is a "Japanese No", it is so wide in possible interpretation, that only the Eclipse foundation could actually provide such a service.

Random question:

The Cloudflare revolvers definitely went down (1.1.1.1 and 1.0.0.1), do we know if authoratative DNS did?

I have to wonder if it would have. Unless you have some kind of route visibility collecting took, or a bunch of simulated traffic sufficient to pop the CPU on the vMX that represented atl01, it would all appear to work. I wonder if you could generate traffic, and scrape snmp counters as a proxy?

Or some kind of tool that processes the resultant routing tables to generate some kind of "route usage" for every given link and device, maybe even feed it with a table of expected traffic to given destinations.

> # Management practices

>

> Cloudflare's core business is networking. It actually embarrasses me to see that Cloudflare YOLO'd a BGP change in a Juniper terminal without peer reviews and/or without a proper administration dashboard, exposing safe(guarded) operations, a simulation engine and co.? In particular, re-routing traffic / bypassing POPs must be a frequent task at scale, how can that not be automated so to avoid human mistakes?

We don't know if this was entirely the case, based on the timeline for the initial incident that prompted the change gone awry, there very well could have been an ITIL-Style CR created and processed within this time.

Judging by the edits made, this wasn't just simply taking a POP out of service entirely, but reducing the amount of (or eliminating all of the) traffic from neighboring POPs sent to compute at the ATL location. I can't image that this exact type of change is all that common. BGP anycast actually makes things significantly more complicated when removing edges.

As far as the mechanics go, with junos's CLI, there's not a lot of difference between what the intended command would have been, and the one that actually happened.

---

What they probably wanted

| example@MX1> configure

|

| {master}[edit]

| example@MX1# edit policy-options policy-statement 6-BBONE- OUT

|

| {master}[edit policy-options policy-statement 6-BBONE-OUT]

| example@MX1# deactivate term 6-SITE-LOCAL

|

| {master}[edit policy-options policy-statement 6-BBONE-OUT]

| example@MX1# commit

---

What might have happened

| example@MX1> configure

|

| {master}[edit]

| example@MX1# edit policy-options policy-statement 6-BBONE- OUT

|

| {master}[edit policy-options policy-statement 6-BBONE-OUT]

| example@MX1# deactivate term 6-SITE-LOCAL from prefix-list 6-SITE-LOCAL

|

| {master}[edit policy-options policy-statement 6-BBONE-OUT]

| example@MX1# commit

---

Initially, this seems like quite a bit of difference, however, Junos has a hyperactive autocomplete that triggers on spaces,. that deactivate could have been as short as "dea ter 6 fr p 6"

I'm not aware of any routing simulation product that is able to simulate complex bgp interactions, and report on effective routes of simulated traffic, as well as CPU load predictions. The closest I am aware of is running GNS3 (or a bunch of VM routers) overnight and capturing SNMP.

On the other hand, automating these kinds of changes would seem trivial, but such a service would have to be as fault tolerant as any other project, but is most certainly a worthwhile endeavor especially since integration is actually relatively easy, Junos provides some nice REST and XML APIs on the management interface that can do pretty much everything the CLI can, except start a shell.

For some reason, I am able to view the linked page while logged out, even in a private tab.

Title appears to be really misleading. While it's particularly annoying that you cannot disable the slack like embeds, there are workarounds, and it's being tracked as an enhancement request.

I can still use jira itself without linking either GitHub or Google drive.

I feel like I'm missing something, the document mentioned a lease, so I am wondering if these repeaters reside on Cal fire owned property, or owned towers. They're not exactly small pieces of equipment, besides the mast and the actual radios, the filters (diplexer) take up quite a lot of space, and there's likely a generator on site as well.

Regardless of land or tower ownership, the provided email doesn't have any timeline, which is somewhat unprofessional when we're talking about something that takes weeks to remove.

Redis is an example of this. When redis saves in the background, it will for and use COW to shapshot a point in time, while the main redis thread keeps going with the normal redis. If you disable overcommit, redis can fail to fork, when there is actually sufficient memory to save the db.

Some time ago, I made something using a similar technique to redirect to router configuration pages. Used WebRTC to get local IPv4, then spawned a worker and timed it, if it came back fast, I assumed it was there, and redirected the user, otherwise I tried a different common "router" address. I was unaware of dns rebinding at the time.