I'll use a gif with each frame being a different country flag. Then I can access them by frame index.
That visual pattern compression though
I fixed a slowness issue so you might see the instance get quicker but if it still bad let me know.
I'm seeing quite slow response times / page loading right now. Seems like it does have some variance between normal/acceptable and very slow.
The link is broken. Looks like code was accidentally pasted there.
https://lukasatkinson.de/2025/net-negative-cursor/%20%20%20%20let%20mut%20bytes%20=%20vec![0u8;%20len%20as%20usize];%20%20%20%20buf.read_exact(&mut%20bytes)?%3B++++++++%2F%2F+Sanitize+control+characters+++++let+sanitized_bytes%3A+Vec%3Cu8%3E+=+bytes.into_iter%28%29+++++++++.filter%28%7C&b%7C+b+%3E=+32+%7C%7C+b+%3D%3D+9+%7C%7C+b+%3D%3D+10+%7C%7C+b+%3D%3D+13%29+%2F%2F+Allow+space%2C+tab%2C+newline%2C+carriage+return++++.collect%28%29%3B
404 Page Not Found
The page you have requested does not exist. Would you like to visit the start page?
Cleaned up link: https://lukasatkinson.de/2025/net-negative-cursor/
Marketing-speak, not saying much at all. Not even a hint in what they "discovered", what they plan to change, or plan to do. No acknowledgement of previous issues, making me doubt the "working with the incredible global community" as pure marketing-speak.
I also want locally deleted files to be deleted on the server.
Sometimes I even move files around (I believe in directory structure) and again, git deals with this perfectly. If it weren’t for the lossless-to-lossy caveat.
It would be perfect if my script could recognize that just like git does, instead of deleting and reuploading the same file to a different location.
If you were to use Git, deleted files get deleted in the working copy, but not in history. It's still there, taking up disk space, although no transmission.
I'd look at existing backup and file sync solutions. They may have what you want.
For an implementation, I would work with an index. If you store paths + file size + content checksum you can match files under different paths. If you compare local index and remote you could identify file moves and do the move on the remote site too.
Your git repo might get very big after some time. Especially if you move files.
Moving files does not noticeably increase git repo size. The files are stored as blob objects. Changing their path does not duplicate them.
Can you be more specific? What in what they present is bad use of AI?
What makes you think anyone blindly trusted it?
They pointed out how it was almost correct, and the two places they had to correct. Obviously, they verified it.
There and at other times, they talked about similar approaches of generating a starting point rather than "blindly trusting" or anything like that.
Blazor allows JavaScript like interactions, allows the developer to write in C# but gets rendered serverside
Blazor can compile .NET to Webassembly and run that in the web-browser.
Probably because it's much simpler to integrate than Jenkins.
Their own CI system 'Actions' is in open alpha.
Honestly, I'm glad they didn't use Jenkins. Managing it is a convoluted mess. (I don't have experience with Woodpecker CI nor with Forgejo Actions in particular, though.)
The screenshot is from my desktop with wide enough screen on Lemmy web (programming.dev).
The issue is one of scaling.
When I open the image without being resized into the website layout, it has the following visual pattern:
When I zoom out to 50% it looks (almost?) fine
Did you scale the source with ffmpeg? Do you have a visual pattern in your console background? The simplest solution would be to have a solid color as background. The second best to render a small enough size that it does not get resized in the browser.
At 1920x1038, it's very big right now. I'm surprised the font is big enough to be readable. I assume you scaled it up or have a high dpi display resulting in this.