Outrage over a single low-quality paper, of which there are thousands across academia, misses the larger point. The real issue is the systemic problem within academia, where creative thinkers are often stifled early in their careers. Researchers find themselves forced to align their work with the direction of funding sources or their superiors' interests, resulting in a significant misallocation of resources. Annually, billions of dollars are buried in research that lacks true innovation or independence. This is a far more critical issue than the work of this literal nobody dean. What's even more funny is that the same individuals quick to criticize such low-hanging fruit often do everything in their power to avoid scrutiny themselves, especially regarding the inefficient use of tax dollars and the insignificance of their research areas.
This isn't just a low quality paper. It is two paragraphs long. Its very last sentence is a sentence fragment. It just says "Rest may be important for train operators. Rest is also important for this particular kind of fly species."
I've seen low quality papers get published before, but they are enormously better than this. Even the very worst papers I've ever seen in peer review and given strong rejects to are enormously better than this. This wouldn't even cut it for a poster proposal at a conference.
I would expect a 6th grader writing a science report that they were given two weeks to complete to produce better writing than this.
As a European, I really don't care. My US colleagues are all buying houses and going on expensive ski trips while I can't even afford a used car. I am a much better software engineer than they'll ever be and yet I'm stuck in this hellhole and will never be able to afford my own home. Time for the market to cool down a bit.
Okay so I self-host Vaultwarden, what do I need to do to fix the vulnerability? The article mentions another flavor of the self hosted docker image though.
I have nginx-proxy docker container on top of vaultwarden - there aren't any alias directives there. Vaultwarden itself appears to use rust with some http framework called "rocket" [1]. Sorry I'm not familiar with rust world.
But anyways, said vuln doesn't apply to vaultwarden.
Vaultwarden does not include or use nginx, and neither does its official Docker image. Unless you are using nginx yourself (you'd know) this does not affect you.
Yep, mainly focused on two sports soccer and rugby league (#1 sport in my country) which both have a culture of 3, 2, 1 voting system used in my app. I emailed the presidents or coaching staff of hundreds of clubs introducing the product.
Hi, big fan of Rebass, Theme UI..although sometimes Theme UI with Next.js doesn't work right out of the box, are you still the maintainer of these libraries?
And how did you get the word out for your boilerplate product, just on Twitter? Do you have any tips on how to find a niche where a good, well maintained boilerplate is missing and how to make it profitable?
Thanks
Thanks for the nice words! I stopped maintaining ThemeUI when I left Gatsby in 2021.
In terms of getting the word out, it's really all based on my personal audience. I haven't found a repeatable marketing channel outside of just… tweeting about it, which is also visible in declining sales as I saturate that channel.
I want to come up with such an idea and do the same but I always think "wow my idea is amazing" but then after a few days I realize that it's not really what the market needs. Do you have any tips on how to improve this ideation process?
Io be honest, i'm not much of an expert on this either. I've built several projects and have abandoned midway.
I put down all of my ideas with a title and 2 lines of description on evernote whenever it strikes (mostly when seeing a problem, there could be other solutions that exists for this problem at this point).
And whenever in an unrelated instance I encounter a variation of the problem again, which if I believe could've been solved by that idea that I had, I give it a serious thought into researching for solutions and if none exists, I get to build.
I wouldn't call this an ideal process, it just works for me. The bad side-effect I have come to realise from this process is, I build products for which there doesn't exist a solution, which means either the market isn't there or isn't big enough.
The previous project was the same situation (fileql.com, ended up selling it) and now RosterBird. They stay small for relatively long time as you also have to convince users that they have a problem in the first place.
