Wore a bra the first time yesterday (and the night). It just feels awesome :heart_trans: And it has some cute lamas on it too :3 #trans#mtf#transjoy#lama
Nice. #gitea did it; they're now makeing #giteaenterprise where they added already more features. And there's no doubt that they'll continue this path forward, putting more and more effort in the enterprise version and keeping the free version from getting these features via contributions since it would ruin their company.
And best thing is: they already are stealing code. They took stale PR's and put it into the Enterprise version. Thats just disgusting. And unlike gitlab, which EE is not only opensource (i.e. readable), they also have a lot of paid engineers to built their product, unlike gitea, where like 95% of work is done by volunteers, not only now but in the past included. It's espc disgusting for how cheap the features are, like an IP allowlist. Which gets even more sad when you think about what would happen if a volunteer would contribute similar features to the free version. Atleast we have not to guess as it is clearly stated in their contributors guidlines: they have added a clause once they became a company, that they can "politly refuse" any PR by simply not responding. That stinks for me after a tactic of keeping face while not allowing any code that would conflict with the enterprise version.
Urgh. Wanted to play a bit #Genfanad (was a browser #mmorpg a bit like #runescape with a good load on humor over the genre itself), and just now found out they pulled the public servers and working on a new version where the combat is entirely replaced through a tradingcard-game-ish system. Idk, but it seems so random and honestly not a good decision imho. I know it's somewhat of a obcession lately in some parts of the gameing industry lately to shove a tcg into everything, but come on, as a replacement for combat? Also: just sad to see a game "die", bc now all progress people had is just lost.
After spending yesterday entirely by re-implementing #tcp in #userspace I now know:
TCP is weird
we have the PSH flag that completly makes the data ignore the TCP sending/recieve buffers and directly writes into the application's stream
ACK can be part of literally any other package; you also can SYN, FIN or PSH data while ACK'ing
zero-length data packages technically exist, but they dont do anything; they dont even wake up the FD when it's in a epoll
the #linux#kernel is funny: it responds with RST to incomming TCP packets, even on raw sockets; you'll need to drop them via #iptables if you want to implement TCP in userspace
Learned a lot! Now I can go on and create a few tests for #webservers; mainly SYN floodings and so on.
@adnan While QUIC exists, the majority of webserver software & proxies only run on HTTP/2 to my knowlege; and mostly the consensus is that QUIC only has really benefits in very high volume scenarious or on edge-routers.
Another reason is that HTTP/3 was standarized only recently in mid 2022; so we'll dont see increase in widespread use until maybe 3-5 years from now.
Also im working on an own web- & async-framework, which both need TCP; the webframework for HTTP/1.1 & HTTP/2 and the async ofc bc TCP is still one of the biggest standards xD
Nice, either I accidentially discovered a bug in c++ / gcc, or I use references so horribly wrong gcc cant help me anymore (which totaly is an possible option).
Apparently generates gcc some code in the prelude of a member function that overwrites parts of the data inside a reference, which it is not supposed to do.
@mai_lapyst you might want to investigate your testing setup... this should have been trivially detected.
And yes, references are just immutable pointers. Their main purpose is to provide the syntactic sugar of not having to de-reference, which is needed, for example, for operator overloading.
@simontoth@mai_lapyst how is this helpful? How is it trivially detected if you don't already know how references and pass by value works? Even if you do know it's an easy mistake to make if you jump between languages
The most tiresome thing in #webdev is picking the techstack. So many choices to make: plain #javascipt or a more restricive language like #typescript , which ofc is often depending on the overall frontend framework to use: #svelte , #react , #preact , #solidjs ?
Or do one completly deviate from the classical way and use rather a techstack via #wasm , such as #rust with #dioxus ?
So many questions to answer and that still is only the js side of things, you then have to think about your css framework (if you want to use something like #tailwindcss ), your font choices, and ofc if and what styling library you actually use ontop of our frontend framework; e.g. #bootstrap , #blueprintjs , #tabler.io and so on.... which also often depends on your framework of choice!
@mai_lapyst yes my approach is to ask why I'm doing the project: is it to make a thing or to learn a thing? If the former, I have a tried-and-true stack (for me that's Django+HTMX+Tailwind but YMMV), if the latter then it's whatever it is that I want to learn about, and if it turns out to be worth learning then it gets added to my tried-and-true stack.
@danjac Yeah thats true. Only problem is when you are burned out by your current tried-and-true stack (ruby w. sinatra+mustache templates & manual js) and tried to many different other frameworks, libraries and languages in a maybe too quick manner xDD
Also: Actually didn't knew about HTMX so one thing more to look into lol
I post about fairly anything that crosses my mind or goes on in my little corner of the internet x3
Other things might include mental health, #transition and so on!
So if any of that interests you feel free to follow!