zaphod

joined 1 year ago
[–] [email protected] 15 points 8 months ago* (last edited 8 months ago)

That third screenshot, assuming good keyboard navigation, would likely be a godsend for anyone actually using it every day for regular data entry (well, okay, not without fixes--e.g. the SSN and telephone number split apart as separate text boxes is terrible).

This same mindset is what led Tesla to replace all their driver friendly indicators and controls with a giant shiny touchscreen that is an unmitigated disaster for actual usability.

[–] [email protected] 14 points 8 months ago

Amazing how Google and Apple differ on so much, but in this respect they are in total agreement...

[–] [email protected] 21 points 9 months ago

"Huh weird, I tried to use and it's not working. Welp, guess I better fix it..."

[–] [email protected] 7 points 9 months ago* (last edited 9 months ago)

That's a goal, but it's hardly the only goal.

My goal is to get a synthesis of search results across multiple engines while eliminating tracking URLs and other garbage. In short it's a better UX for me first and foremost, and self-hosting allows me to customize that experience and also own uptime/availability. Privacy (through elimination of cookies and browser fingerprinting) is just a convenient side effect.

That said, on the topic of privacy, it's absolutely false to say that by self-hosting you get the same effect as using the engines directly. Intermediating my access to those search engines means things like cookies and fingerprinting cannot be used to link my search history to my browsing activity.

Furthermore, in my case I host SearX on a VPS that's independent of my broadband connection which means even IP can't be used to correlate my activity.

[–] [email protected] 2 points 9 months ago

Oh god, I'm old...

[–] [email protected] 2 points 9 months ago* (last edited 9 months ago)

Your first two paragraphs make the picture worse, not better.

As for your last, I'm not writing an economics thesis. It was a quick analysis to illustrate a problem no sane person disputes: streaming services have substantially driven down revenue for artists, to the point that for many it's genuinely impossible to create their art while making a living wage.

Is it better than piracy? Sure. At least the artists are getting something (well, unless you drop below Spotify's streaming cutoff, in which case you can get fucked). But it's still a shitty deal and gives consumers someone else to blame as artists slowly bleed out.

[–] [email protected] 2 points 9 months ago

The economics with the artists haven't changed. Until they do I'll still use them to pay artists a living wage.

[–] [email protected] 2 points 9 months ago* (last edited 9 months ago) (2 children)

Assuming each of those tracks is about 3.5 min long, that's about 250 hours of music. Given your numbers they paid an average of 7 bucks per hour of music.

For context, 25 years ago a typical 45 minute album would fetch 15 bucks. And that's not accounting for inflation adjustment.

I'm sure that's totally sustainable for those artists...

[–] [email protected] 57 points 9 months ago* (last edited 9 months ago)

As a former product manager where the CEO led the sales team, I feel seen.

[–] [email protected] 1 points 9 months ago* (last edited 9 months ago)

Honestly the issue here may be a lack of familiarity with how bare repos work? If that's right, it could be worth experimenting with them if only to learn something new and fun, even if you never plan to use them. If anything it's a good way to learn about git internals!

Anyway, apologies for the pissy coda at the end, I've deleted it as it was unnecessary. Keep on having fun!

view more: ‹ prev next ›