ramblurr

Why does your comment here contain more information than the blog post from tailscale itself?

I am just a layperson when it comes to pixel art, but to me the example in the article is clearly garbage/low quality.

- the magenta background is still visible along the edges - the color palette is all over the place - random noise pixels of totally different colors are visible scattered around - the lighting and shading doesn't look that good

It's definitely a trend. But it's also arguably not ASCII art. But maybe I'm just moving the goal posts.

1. The first paragraph has a callback and link 2. You're not the intended audience of the post most likely

So like OHTTP but for UDP traffic? I suppose they are using MASQUE CONNECT-UDP?

They are careful to not exactly claim the same anonymity properties of Tor, though I think a lay reader will read that differently (ie, that they do have the same anonymity property as Tor).

That said being able to verify the inner wireguard conn to mullvad is nice. Of course you have to trust them that they aren't colluding with mullvad to share your identity/ip. But same goes for OHTTP.

>So give the options to a model that doesn’t have the context of your editing process.

> I conjured a bit of software to manage this for me[...]

I don't understand how the annotation application shown helps with the stated goal of preventing the model from praising you. What's the actual software assisted workflow?

Paperback copies in EU seem to be very expensive (90+€ on amazone.de) unfortunately.

What does this have to do with the linked page? Not a criticism...I just don't understand like I am missing context.

Care to share more about how/what you built?

(as discussed in clojurian slack):

The argument seems to take the leap from 'Ring is the wrong abstraction for what I want to do' (fair enough) and concludes 'Ring is inadequate, and therefore Clojure has a viability problem.'

Ring is explicitly designed to be web-server agnostic and therefore intentionally does not expose the full Jetty/Jakarta surface. Many using ring aren't using Jetty!

If your app requirements are specifically EE/Jetty-centric, then bypassing Ring may be entirely reasonable, but I don't see how that becomes an argument against Ring's design, much less against Clojure’s viability for enterprise applications...when enterprise means "serious business" not "Jakarta EE".

There are a few actual issues with Ring's design (that are in the issue tracker) I can think of when it comes to it's ability to express valid HTTP semantics. But "it doesn't OIDC" isn't one of them (that's sort of a category error?)

All that said... The charitable reading of "Clojure has a larger problem for its future [...] in which we can produce enterprise-grade web applications" is one where the "we" is limited to Derek's company/team, which yea, sounds like they need more Jetty/Java EE than Ring provides. But if the "we" is the Clojure community as a whole, then I would dissent.

But with a debit or credit card?

Bamboo has been sketch and proprietary since the beginning. It's such a shame to see the maker community get sucked in (though I guess there is precedence wrt Fusion et.al.)

Your comment is also rather vague, how is it relevant? Did you observe something interesting?

Agree so much! It's so interesting all the different use cases and interpretations of those use cases people have.

Like this self-hosted project aims for "simple deployment"/less infra, but I can't imagine how you end up at "use Cloudflare proprietary offerings" and reconcile that with "self hosted".

But if you host the node app yourself and point it at your own seaweedfs/minio/garage that's still more infra than node process+SQLite file.