Honestly, you ever tried to look back through a long thread on Discord? It's impossible. If you want to read the original message that started the thread, good luck, you'll be scrolling all day and may never get there. How anyone can claim that's "easy to use" is beyond me.
Discord works for quick discussions happening right now, and that's it.
The problem they're addressing is that some sites they were scraping from have begun instituting measures to stop them. The site went from working beautifully to working barely at all, with most sources either loading incredibly slowly or failing to load at all. I followed the discussions a bit on their discord, and it seems like the first recommendation was for users to host their own proxies. From what I see on the site's initial splash, that still is one of the recommendations. I'm guessing they also rolled out the browser extension as an alternate method for users who don't want to set up a proxy, since they were getting tons of people on thsir discord complaining about it being too hard or whatever.
But yeah, who knows if the extension is safe. The project is open source, so you can always examine it for yourself. But at that point you may as well just host your own proxy.
Edit: looked into it a bit more; the extension's originally proposed purpose seems to be to get around CORS restrictions on certain sources. Seems the original proposal was here: https://github.com/movie-web/movie-web/issues/581
I used to work at a company that held to the concept of "don't be a hero." Basically, if you were having to step up, work overtime, and always go out of your normal routine to "fix" stuff, then you're actually enabling bad processes.
I think the same concept applies here. If you can't let any code be submitted without personally reviewing it, then there is something wrong with either the review system, the onboarding system for new devs, or the continuous integration system that should be catching mistakes. Same goes for triaging: if no one is triaging because it's too exhausting and leads to burnout, then some other system may need to be devised for handling outstanding issues.
Obviously this is much harder to deal with in an organization where most contributors are volunteers. But if we want the project to survive and not be taken over by corporations who can afford to pay people to deal with this stuff full time, I think it should be addressed in a different way.
Don't forget to upload them all to crates.io. Add them to the list of useless crates that no one will ever use.
Companies are using subscription models because it has proven to be far more profitable than a one-time purchase. Why sell the product to each person just once when you can sell it to them over and over again? You no longer have to constantly develop new products and versions, and you now only have to maintain your existing product.
And it works because people buy it.
I'm curious to see whether this survey shows that the amount of jobs programming Rust has increased.
I'm guessing because there's literally no penalty for it. May as well steal content to give you more interactions, if that's what you're after.
I don't really get why we need social media elements in GitHub at all
First 1/3rd is a bit of fluff but after that, good article.
Ah yes, the Wadsworth constant.
That's actually what the comment above was suggesting, which is why I was wondering why you couldn't get it to work. Glad you got it working!
What does "FE" stand for in this context? Sorry if it's obvious, I just don't see anywhere that it's actually written out.
I sure hope this is not how most CS courses are being taught
I thought problem inputs were randomized for each user?
Did we read the same article? This mentions nothing about infighting between groups.