A screenshot of two comments on reddit.
The first comment is by a deleted user and the comment has been removed. The second comment is a reply to the deleted comment and it says: “That solved it. Thanks!”
A screenshot of two comments on reddit.
The first comment is by a deleted user and the comment has been removed. The second comment is a reply to the deleted comment and it says: “That solved it. Thanks!”
As much as reddit sucks right now, getting rid of decades of tech solutions that are not found anywhere else (not on the fediverse either) is not a solution. back up your reddit stuff somewhere and link to it from reddit, but don’t delete it, and don’t delete it and tell people ‘because lemmy’, people will hate lemmy.
Instead of “because lemmy”, I’d say reddit now charges money for the content, but they did not pay the creator.
That’s a problem with many companies… for example, Google Maps relies almost completely on its local guides that spend many hours of their free time adding content to google maps. Google makes money with ads, but in my >5 years of being a local guide, I only got a 15% discount for Google store as reward (after being a local guide for 4 years) which I don’t even need…
I don’t mean to brag, but I was a very active Guide for a couple years and I am still in the top 10% even though I haven’t posted a review in two years. My profile info shows that I have had hundreds of thousands of views.
They gave me a pair of Google Guide themed socks. They were cheap, poorly sized, and wore thin quickly.
My wife wrote a lot of reviews on Google Maps and all she ever got were some socks.
It’s infuriating, and even more when you start looking for that profit pattern in companies that range from “philanthropic” foundations leeching from volunteers while buying their own companies stock, to academic journals with CEO’s earning ridiculous amounts of money over research that someone else paid.
Use “Because API changes” instead of “Because lemmy”. But I agree; changing it to a link to Lemmy instead is better. Theres a shit-ton of valuable information buried on Reddit.
yeah, but Reddit was shit long before the API changes…like abandoning open source 7-8 years ago.
Well without a public API it may be quite impossible to mass delete stuff (for non EU-citizen at least, EU citizens can always do a GPDR delete request -otoh you basically have to connect your reddit account with your real name to do that so big nope as well) in the future, so i fully understand why so many people did it
Will it cause collateral damage? Yes. Am i happy I did it when it was still possible? Fuck yes.
Honestly, those decades of solutions are useless unless they have both a version number and a date associated with them. And if that date is more that 6 months ago, it’s probably still useless even if it has both.
It’s not just tech solutions. It’s solutions for everything.
You say that, but when your employer is still running Windows Server 2012, you’ll find a lot of 10-year-old solutions to problems are still very much applicable.
Even beyond that, there are a lot of new versions of things that are still built on legacy software. Some things change but some things just remain the same for a long time.
It’s usually still a good-enough jumping off point. My fiance came across this just yesterday, her sound in Overwatch kept cutting out and found a 2 year old solution from Overwatch 1 and it got the issue fixed. I’m gonna be bummed when all that data is gone forever.
I’m running a GTX 1060, have debian Servers and my Powerline Adapter is from 2015. ipv4 is still dominant and the x11 protocol hasn’t been changed in over 40 years. Plenty of tech widely in use today isn’t getting updated or replaced or updated every 6 months
I posted a reply with a “quick fix” to a Lenovo T14s issue, quite some time ago. That reply has kept getting “Thank you” replies now and again. I suspect that that will continue for a long time to come.
There is a lot of that kind of useful information on Reddit that doesn’t get outdated for at foreseeable future.
Hell. I found a 14 year old solution to a Borland database issue I had at work, buried in some old forums, so don’t dismis the value of old information.
Not necessarily on that last point. Alot of people run older hardware, especially recently with the economy dialing back and negligible updates being made hardware wise the past 5-6 yrs. Like i DD a '15 i7 MBP with Arch linux, and if it weren’t for the Saved documentation in the Arch Wiki for this 8yr old laptop, I would be SoL on getting many things working.
These solutions are not always workarounds for bugs. Sometimes they are ways to do something non-trivial, and that nontrivial something can still be done in the exact same (or at least very similar) way even after several major version releases.