Re: [dev] [dwm] swallow without patching dwm -- or losing focus

On Thu, May 25, 2023 at 07:42:04PM -0300, Spenser Truex wrote: > I converted this swallow program to C, not that it makes any difference > at this code size. It's just a couple of malloc'd strings. > > https://github.com/equwal/swallow-c-- $ ./swallow '$(rm -fr $HOME)' `system` is a func

Re: [dev] [dwm] swallow without patching dwm -- or losing focus

On 23/05/26 07:24AM, Sagar Acharya wrote: > Beautiful code. As a rookie user, how will this code be used? Can this be a > complete Xenocara/Xorg alternative? > Thanking you A very humourous response. I just want my windows to open where I opened them. There is no kitchen sink included. It is use

Re: [dev] [dwm] swallow without patching dwm -- or losing focus

Beautiful code. As a rookie user, how will this code be used? Can this be a complete Xenocara/Xorg alternative? Thanking you Sagar Acharya http://humaaraartha.in 26 May 2023, 05:45 by tr...@equwal.com: > Greetings, > > I converted this swallow program to C, not that i

[dev] [dwm] swallow without patching dwm -- or losing focus

Greetings, I converted this swallow program to C, not that it makes any difference at this code size. It's just a couple of malloc'd strings. https://github.com/equwal/swallow-c-- I'd like to make it actually transfer the terminal's focus rather than async open and hide itself. That way you get

Re: [dev] running a shortlink provider

Thanks for the details! I have tough about hash maps but actually not about simultaneous requests... this seems quite bad tho. (if you have more than a few hundreds users?) I know it is insecure, but I would store everything in a txt file where each line is a link. Why is that insecure? Because

Re: [dev] running a shortlink provider

On 23/05/25 10:29AM, Anthony wrote: > On 5/25/23 07:29, Страхиња Радић wrote: > > Perhaps the most minimal solution for keeping data would be TSV files, but > > they > > are not suitable for storing data entered from the web because of > > concurrency, > > so a "real" database would be needed. >

Re: [dev] running a shortlink provider

On 23/05/25 10:29AM, Anthony wrote: > What do you mean by, "because of concurrency"? At any given moment, several HTTP clients can request posting data at the same time. They can hang indefinitely in the middle of sending data. If the process involves writing to a file, this can lead to data cor

Re: [dev] running a shortlink provider

On 5/25/23 07:29, Страхиња Радић wrote: Perhaps the most minimal solution for keeping data would be TSV files, but they are not suitable for storing data entered from the web because of concurrency, so a "real" database would be needed. What do you mean by, "because of concurrency"? I know it

Re: [dev] running a shortlink provider

2023-05-25 7:29 GMT+02:00, Страхиња Радић : > Perhaps the most minimal solution for keeping data would be TSV files, but > they > are not suitable for storing data entered from the web because of > concurrency, > so a "real" database would be needed. > Probably it can be duct-taped writing new ent

Re: [dev] running a shortlink provider

Highlight: Link shorteners always go down due to non-funding and bloatware backends. Let's have a suckless one that is cheap to run! On 23/05/25 07:02AM, Marcel Plch wrote: > On Thu, May 25, 2023 at 12:47:20AM -0300, Spenser Truex wrote: > > Hello, > > > > My internet friends and I have been want