[-] somegeek@programming.dev 1 points 2 weeks ago

The most AI answer ever 😂😂

[-] somegeek@programming.dev 1 points 1 month ago

Where me-me?

[-] somegeek@programming.dev 1 points 2 months ago* (last edited 2 months ago)

Emacs has basically everything. If you are willing to set it up.

Like I said, my suggestion is to not get hung up on the live preview feature and use an external tool for that. This way you can decouple your editor from that specific functionality you need.

[-] somegeek@programming.dev 1 points 2 months ago

Good to hear that.

I'm also approaching it with a sort of zero trust security model. Everything, in and out is validated and sanitized. Especially Html injection and XSS.

[-] somegeek@programming.dev 1 points 2 months ago

Hypermedia APIs (i.e. HTML) are specific to the layout of your application, so there is almost never any reason you’d want to insert someone else’s HTML into your page. All you have to do is make sure you only call your own routes (htmx 2 will actually disable calling other domains by default).

Although I do control the routes, its seems like it's not common. One way is a reverse proxy so the component server is forwarded on /components path on the client. So the client can still call relative routs.

[-] somegeek@programming.dev 1 points 2 months ago

I think I should clarify: This isn't a public library (yet). It's a system I'm creating in our company for usage within our products.

I thought about web components and actually created a few. But this hypermedia approach with HTMX is much simpler to develop and maintain, and since some of the components are very heavy, the server side rendering takes load off of clients and makes complex renderings possible.

Can you elaborate why do you think HTMX doesn't fit this usage? With webcomponents, the flow will be like this:

  1. Client fetch data from source
  2. Client render the data within tge component

With this hypermedia approach the flow looks like this

  1. The client requests component with data from source from server
  2. Server fetches the data, (possibly validates it)
  3. Server renders the component
  4. Server sends component to client
[-] somegeek@programming.dev 1 points 8 months ago

I honestly dont know at this point. but my point is, people buying phones of THE evil company that takes our freedom and privacy away, to get freedom, and think that a company as evil as google will just let you have actual privacy, is kind of absurd. But, it seems like you people have done more research on this. You say there is and havent been evidence of spyware on google pixels, and I will accept that. But deep down Im pessimistic.

[-] somegeek@programming.dev 1 points 8 months ago

Seems people are pretty confident about that. I guess I am too pessimistic in tech to accept governments and big tech will allow you to have a spyware free phone by any means, but I havent done actual research (Im not a security researcher anyway) into it. So I accept the wisdom of people here.

[-] somegeek@programming.dev 1 points 8 months ago

Ever heard of hardware backdoors and spyware?

[-] somegeek@programming.dev 1 points 9 months ago

Nah their body language, shape, white fur and button eyes, paws, everything about them is cute

[-] somegeek@programming.dev 1 points 3 years ago

common SUSE w

view more: ‹ prev next ›

somegeek

0 post score
0 comment score
joined 3 years ago