ffaser5gxlsll

I've been using soundcloud also for similarly long, however a few months ago I started to notice the sharp uptick in llm-generated music that killed completely the enjoyment I had out of the site for me.

It started first noticing some similar songs that repeated too often. Songs that I actually liked, so after a while I recognized them and their variation too often. Then noticing some of the tags I was usually listening to were filled just by just one or two artists. Looking at the artists themselves, they're publishing a couple of songs per hour, non-stop. They're also clearly stating that the music is generated in the artist info btw.

Problem is, this destroyed completely the "discoverability" for me. Tags are hijacked by hundreds of similar songs you can't avoid. As soon as somebody likes one of these, "related" also quickly starts to loop.

I found no way to block these. You can block users, but this doesn't prevent their songs being recommended to me. Feedback was, so far, ignored.

I can't possibly think they're not aware of this issue, so I can only assume that so far they're getting something out of it...

I'm also a regular OSM contributor and I cycle between various apps/layers. I'm in the alpine region, regular hiker, and osm is the only map source I use (frankly, I find gmaps to be garbage for anything except looking up businesses).

I regularly try comaps, but while it's pretty smooth at rendering, the detail is visibly lacking at anything except maximum zoom level. When enabling contour lines, it's cluttered and hard to read. I tried to use it a few times on hikes, and while it's still much better than gmaps, if you're looking for something to use on a hike as an actual readable map and not just something to follow directions on, I'd say bite the bullet and get osmand.

osmand has indeed confusing interface, but the map rendering itself is excellent and can be heavily customized as needed.

On the web front, tracestack and mapy are both excellent presentations.

Today there is little reason not to use Rust and it can cover both the processing side and the payload software. But people still insist on using C/C++. I'm OK with that as long as I can invoice them.

Any reason _not_ to continue using ocaml besides being less popular?

If popularity/mindshare wasn't an issue, I find the development cycle with ocaml to be nicer in several ways compared to rust on a platform where stuff like python is already allowed (I wouldn't call a full-blown linux system, even with limited memory, "embedded").

Press page-down: scrolls the galleries right. Somebody thought this was a good idea, let alone intuitive.

The universal contact function is usually there, and it's email. I tried many times: it works. Authors respond. Only very few people seem to want to keep it hidden.

I'm dumbfounded by the number of times I see comments of the form "if the author is reading this ..." on a 3rd party comment side, with a link posted by somebody else, on a forum the author is likely never going to watch, followed by an actually useful comment that you could have _ensured_ the author reads by you know... just contacting him?

Forum comments are just recipe for instant spam, and have been so in the last 10+ years. If you want to make them useful, it currently needs to be actively policed (not to mention: you can be responsible for the content posted as well in several countries now). As an author, only if you're trying to create an audience around your blog, all the hassle around it might be worth it.

Aside from outages, what really bothers me lately about GH is how slow the "app" actually is. Keeping a tab open on a PR status check burns 25-30% of a core on my cpu even when it's hidden. Reviewing large PRs has an awful workflow. Almost every diff page I load starts with "there's nothing here" then starts to load...

Meanwhile: one of the major mobile network in my country announced cisco collab/ipv6 ~5 years ago, but still doesn't provide v6, just v4 CGNAT.

Personal web server running dual stack since early 2010s currently sees 18-20% v6 traffic. When split by type, counting only mobile users it reaches 30% at peak.

Bot/crawler traffic is ironically 100% v4.

Meanwhile: enabled h3 in september last year for the fun of it, instantly at >40% traffic by request count, passing 50% since the beginning of the year, h2 accounting almost all the remaining traffic and plain ssl/http requests <1% being just bots.

but one of my biggest pet peeves is CLI / TUI developers creating their own custom themes

An even bigger one is hardcoding black and white instead of using foreground/background and use reverse when needed.

You said yourself the spam drove you off.

Yes, indeed. But I still stand by the gatekeeping though.

Sadly, it's a tragedy due to how popular github (and similar services) have become.

These sites were supposed to be by developers for developers.

It's never fine to be rude.

Moving off github into a more niche platform was the best choice I have ever made to curb such zero-effort issue and feature requests. It raises the barrier just enough.

On the other hand, I'm a dev, and I hate the "start a discussion first" gatekeeping. I participated in projects where the approach is to start a discussion on a forum first, and I get the same feeling you have as a tech guy calling ISP support on the phone.

I had to go back and check, with "modern invisible scrollbars", and those useless theme settings at the bottom I assumed the page was just some css demo that ended there and left.

For whom?

Every single web or mobile app does his own custom thing nowadays. As a user I couldn't care less how it's implemented, what I want consistency in behavior and style across the board.

It feels like this has been completely lost, even on platforms like mac where consistency used to be important.

I'd take MFC everything over random behavior if I could.

Second this. The "ui" is perhaps useful when learning to use emacs, but every emacs user I've seen after a while has all of it disabled.

I've been using emacs with the "lucid" build since forever, as it's the leanest build that still gets a graphical window working on X11 and see none of the actual "toolkit".

I guess the pgtk build is required nowdays for native wayland support.

On the server side, probably not, but I'd like to point out that old hardware is not uncommon, and it's going to be more and more likely as time passes especially in the desktop space.

I was hit by this scenario in the 2000s with an old desktop pc I had, also in the 10ys range, I was using just for boring stuff and random browsing, which was old, but perfectly adequate for the purpose. With time programs got rebuilt with some version of SSE it didn't support. When even firefox switched to the new instruction set, I had to essentially trash a perfectly working desktop pc as it became useless for the purpose.

It's dumb because a font a allowed to re-interpret the actual image, but in doing so you also frequently change the meaning of the symbol. This is not a problem for text, but for images just changing the color of the fill might completely change the meaning of the sentence.

See the old apple gun vs squirt gun. The same is true also when using stuff like whatsapp on android, where the os keyboard shows you one image from the system theme, but the one which you see inserted in the text is not what you selected, but at least is partially better than sending something without knowing how it will be rendered, which is what most chat messages have realized after trying to simply using the system font.

So at that point, you have to switch to a different custom font just for the emoji block, and you're still limited to what unicode allows instead of just bundling whatever image you want (which is a great excuse to sell new phones with "new emojis" I guess).

I dislike emojis in general when combined with running text. Especially in terminals or character-based interfaces with fixed-width fonts.

On top of that, there are only very few emojis that can be read properly at the same size of the current line height. It works for a few simplified faces and symbols, but that's it.

The fact that emoji fonts override the font color rendering is an aggravating factor. I don't want text to change color behind my choice (it SUCKS with customized color themes).

They feel like a punch in the face to me when I'm reading documentation or even worse when reading code.

Sadly, it's really hard to avoid them nowdays. I'm using a few lisp scripts with emacs to translate the common ones back to ascii for rendering.

I can point out that "Noto Emoji" is a b/w version of Noto Color Emoji, which contains a MUCH more suitable version of emojis that can be used in running text. As noted before, it's only a partial solution as I find most emojis are still not readable when scaled at the same size as the text and when simplified sometimes they also lose the original meaning (just use the damn word dammit!). But at least they don't override the color. On linux, you can force a font substitution with fontconfig to force the b/w version whenever color-emoji is used and can't be customized.

Regular PLA is actually stiffer than PETG/ABS, but it's more brittle (so has less impact strength) and a pure formulation has a lower softening temperature. It's generally not suitable for parts that go under the sun, unless it's some other formulation such as some HT-PLA variant, in which case it's actually a good choice for parts that need to be thin and stiff.

Under most cases, you won't get the same inter-layer adhesion with ABS, so while you get better impact resistance, under most circumstances PETG will yield more durable parts that won't delaminate under the same stress conditions. For outside use under the sun, you should use it's cousin ASA.

To respond to the OP.. 3D printed parts can be incredibly durable when printed correctly. The parts need to be designed for 3d-printing in mind, like most other manufacturing methods. A 1cm-thick 15% filled PLA slab that has been printed vertically might be easy to snap in half with two hands, but it becomes almost impossible to break with bare hands when printed horizontal, and requires a saw to be cut when filled to 50%+. And this using consumer-grade printers.

I'm using 3d-printed parts for work and at home, some in use for almost 7 years at this point, and the only telltale sign is the layered look.

The rods in the design are not 3d-printed, which makes sense (most plastics would be too flexible, and 3d-printing a rod is always more expensive).

Using VR glasses instead of screens is a wet dream of mine, but VR tech has been one of the worst vendor-locked tech I have ever seen.

I haven't keep up lately, but as a linux-only dev, is there any hw combo which would give me full native hardware support and the ability to develop for the platform?

(I don't count linux-on-[android|win] as a solution)

This is completely subjective.

As a student I used a ton of warez software in the 90ies. As such, I didn't have any real prejudice back then, and photoshop was the worst of the bunch from my perspective. I held that view for a long time, akin to how I consider autocad from autodesk one of the worst cads you could use despite being outrageously popular.

I have no longer an opinion on it as I didn't use it for such a long time. I'm cycling between krita and GIMP, and GIMP's UI is just fine to me, in the same way I suppose a ton of designers-with-big-opinions are more familiar with photoshop due to all the training they did on it (and probably, _mostly_ on it).

I'm still cycling through wayland and x11, and I also do get 1.5 hours more runtime on average on my old 2nd gen t14s with x11+xmonad+no compositor. It's one of the main reasons I'm struggling to move permanently, as I really don't see any advantage from my perspective as I don't use any desktop environment or feature that would make a compositor actually useful. The only thing I do notice occasionally are black borders due to shadow dropdowns in gtk4 programs that don't respect the system theme I've set.

The frustration for me is then which "flavored" version of markdown you're now using, because the evolution seems to always be "MD is simple and popular" until gets extended with subtle differences. Those subtle semi-random differences in flavors get tiring really fast.