dastx

Aah! Pardon me. That makes more sense.

> At the end of the day, this is the only way that non-Chrome browsers can meet Google’s hegemony

Except these quirks include a whole lot more than just Google. Some of the domains in there:

1. nytimes

2. twitter

3. ralphlauren

4. baidu

5. warbyparker

6. nfl

7. gizmodo

8. microsoft

I'm not sure what each different piece of code does but there is many more domains in there.

This is what I keep reading, but when I tried that, auto fill didn't work for this.

> and React for a responsive component-based UI.

Heh. I clearly got too excited to read it properly back when they announced it.

I stand corrected.

I don't know. I guess I figured since Keepass and KeepassXC didn't have it, it might be because the most security and privacy conscious don't do it.

Would love to know too. I've recently thought of something that would be great for go wasm.

Last year 1Password announced official support for Linux, and released a beta. Surprisingly it wasn't an electron app but proper desktop app.

Keepass and all is great. But it doesn't have first class support for anything but passwords.

I'm sure many people will cringe when reading this, but I also save credit cards in my password manager and use it to auto fill when I need it. This unfortunately isn't supported by Keepass et al.

It has templates, which are supported by some implementation but not others. Which also isn't great.

Whatever happened to Tox project?

You are right. I never knew analise was a word, but I know analyse is the right spelling. I'm gonna chalk this up to auto complete error (really I don't know why I spelled it as analise).

Also the fact that Google hasn't updated their app in three months because they don't want to be bound to the change Apple made.

This sounds like it came from the PR department.

But besides that, I don't think Microsoft engineers in their day to day work ever mention embrace, extend, extinguish. Amazon's motive is profit. They're darn good at it too as we've seen. But that's all it is. If in the process they destroy an OSS company, as they've done, they don't care, because now they have their source and no competition.

Anecdotally I know a single ex-AWS engineer, and this person heavily dislikes their position at AWS.

Also Dive is a good tool to analise docker containers.

I don't know if I'm misunderstanding, but if by 'compose support' you mean docker-compose, then podman-compose has existed for a lot longer than v3.0 (which got released yesterday). First commit was nearly two years ago.

Sadly it doesn't feel as polished as docker-compose, I can only assume it's due to the lack of API. Specifically, podman-compose just translates all the docker-compose.yml file directives into podman cli commands, which doesn't seem to be handled gracefully.

Certainly is a weird requirement. Could this possibly a governmental requirement? I certainly know governments have some silly requirements.

I've been running multiple services through podman on a pi without any issues. Certainly not the same as production though.

Layer caching seems to work for me. Note that rootless stores images (and everything else), in different place from rootfull. It may be that you're caching the wrong directory.

Either I'm not reading this correctly, or this cannot be accurate. As an example, in the UK, Virgin Media has a coverage of 96.98% for speeds greater than 24Mbps. A far cry from Netflix's 3.6 Mbps figure.

For data extraction I highly recommend weboob. Despite the unfortunate name, it does some really cool stuff. Writing modules is quite straightforward and the structure they've chosen makes a lot of sense.

I do wish there was a Go version of it, mostly because I much prefer working with Go, but also because single binary is extremely useful.

I'm not saying it's the solution. I'm just pointing what is idiomatic go. Certainly there are arguments for and against code generation.

Where I work we are a go house, and the number of tools I've seen in our pre-commit configurations and in our development environment setup scripts is pretty intense. So is the number of questions around said tooling. There's a lot more friction than I'd expect. I can't even use lack of experience as an excuse for these questions because they're really talented people. Some of them have worked on the product for years, and have literally moulded the product's tooling into what it is today.

Example from the docs:

    // pill.go
    package painkiller
    
    //go:generate stringer -type=Pill
    type Pill int

    const (
      Placebo Pill = iota
      Aspirin
      Ibuprofen
      Paracetamol
      Acetaminophen = Paracetamol
    )

Then running `go generate` will yield:

    $ cat pill_string.go
    // Code generated by "stringer -type=Pill"; DO NOT EDIT.
    
    package painkiller
    
    import "strconv"
    
    func _() {
     // An "invalid array index" compiler error signifies that the constant values have changed.
     // Re-run the stringer command to generate them again.
     var x [1]struct{}
     _ = x[Placebo-0]
     _ = x[Aspirin-1]
     _ = x[Ibuprofen-2]
     _ = x[Paracetamol-3]
    }
    
    const _Pill_name = "PlaceboAspirinIbuprofenParacetamol"
    
    var _Pill_index = [...]uint8{0, 7, 14, 23, 34}
    
    func (i Pill) String() string {
     if i < 0 || i >= Pill(len(_Pill_index)-1) {
      return "Pill(" + strconv.FormatInt(int64(i), 10) + ")"
     }
     return _Pill_name[_Pill_index[i]:_Pill_index[i+1]]
    }

Note: indentation is messing up because of Hacker News, so ignore the indentation.

I disagree. If the library follows semver, or has a predictable way of managing its versions, I would personally set it as broad as possible without breaking compatibility. Especially with something like cryptography. If a critical bug is found, you don't wanna be stuck at a version from a few years ago. Setting a broad pinned version allows you to update this as part of your day to day development.

That boiler plate usually can be generated for you. See Go's stringer which does all the magic for you. All you have to do is define the type and constants, and a go generate directive.

It depends on how you want to pin. You probably always want the latest API compatible version for a package like cryptography. But as I read from that thread, it seems cryptography doesn't use semver, thus you doing something like `>=3,<4` is not really feasible. In addition, this change was introduced at 3.4.

They have a jq script[0] that removes everything but the necessary data for the cost estimation.

[0] https://github.com/antonbabenko/terraform-cost-estimation/bl...

Freenas is the open source equivalent.

Better yet, the Violentmonkey docs: https://violentmonkey.github.io/api

There are some apps that provide this.

- https://github.com/zedeus/nitter for twitter

- https://sr.ht/~cadence/bibliogram/ for instagram

- https://github.com/iv-org/invidious for youtube

There are likely others.

The problem with the automation solution you mentioned is that, it'll be just as slow because of the JS it will need to run.

> I've played with Tvheadend before and the way DVB-T works is multiple channels are placed on a single multiplex, so you only actually need 5 tuners to receive 30 channels.

Maybe I'm misunderstanding, but this sounds like it'll be different per channel/network. For example here in the UK, the BBC airs multiple channels through one multiplex stream, so if you have 1 tuner, you can watch all the channels in the same mux. But one mux can have more or fewer channels than another mux.

When I moved from the Netherlands to the UK, it was what I wanted to do, though I was young and didn't have much besides an idea. So I quickly gave up on it.

I suppose the question is why do you need to have it looped, why not just set up TVHeadend accordingly, and stream it, then through kodi or an alternative, simply use it as a cloud set top box.

This is how I've been using our FTA channels in the UK. I've got a tuner that receives the channels, and tvheadend that streams it to my TV, where I can record, or simply watch each channel.

This is probably similar as self-hosting some services vs letting someone else deal with it. Hosting something like Elasticsearch requires a lot of knowledge and understanding. If you run it yourself it's free! So you end up doing it yourself, but really you'll need to spend engineering hours on it. Engineers being one of the most expensive expense in a business, you've suddenly not really saved much, and you'd have been better off having Elastic do it for you, and you could have started using it in less than a week rather than months.