https://help.kagi.com/kagi/plans/plan-types.html#fair-pricin...

Now every service will be spamming you notifications and emails even more desperately to bait you into "using" the service so they can bill you. More clickbait and scare tactics on news subscriptions. Also goodbye monthly subscriptions.

It only works for Kagi because they're pretty decent folk.

My main gripe with web components is that while they expose the first half of the tree traversal (from the outside in, via connectedCallback), they don't provide access to the second half, after child elements have been created. (akin to Initialize and Load events from ye olde .NET)

    customElements.define('html-import', class extends HTMLElement {
        connectedCallback() {
            const href = this.getAttribute('href')
            const fetch = new XMLHttpRequest()
            fetch.responseType = 'document'
            fetch.addEventListener('readystatechange', (function onfetch(e) {
                if (fetch.readyState !== XMLHttpRequest.DONE) return
                const document = fetch.response.querySelector('body') ?? fetch.response
                this.replaceWith(document)
            }).bind(this))
            fetch.open('GET', href)
            fetch.send()
        }
    })

customElements.define("include", class extends HTMLElement { connectedCallback() { fetch(this.getAttribute("href")).then(x => x.text()).then(x => this.outerHTML = x) } })

I ask because I've spent multiple days trying to get a viable non-local WebRTC connection going with no luck.

view-source:https://thelongestyard.link/q3a-demo/?server=Seveja

The code is here: https://github.com/jdarpinian/ioq3 and here: https://github.com/jdarpinian/HumbleNet. For example, here is the file where the RTCPeerConnection is created: https://github.com/jdarpinian/HumbleNet/blob/master/src/humb...

I feel your pain. WebRTC is extremely difficult to use.

[1] https://github.com/dmotz/trystero

I disagree that the paper not mentioning ‘OVER’ implies that the paper authors secretly think pipe syntax is a bad idea. They probably just wanted to keep the paper concise, or forgot about that one less-used bit of syntax.

Do you think that ‘OVER’ keyword implies something fundamentally wrong about pipe syntax? If so, how?

They didn't add anything.

Yea, it's not native, but its more the native dev experience, and its actually quite portable.