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.