I agree. I don’t have the time but someone should point this out to the dev via an issue on GitHub.
Shine Get
I agree. I don’t have the time but someone should point this out to the dev via an issue on GitHub.
So basically don’t use this in anything commercial because the phrase “feel free” is different to legally libre and gratis. I personally wouldn’t touch this until it’s released under a reputable license.
Shame they didn’t use a proper license when publishing.
Reference for the admission?
This Building Looks Like It Was Designed In Microsoft Word
And it’s made by a Bitwarden developer.
They highlighted it was a bug and said it would be fixed very soon after it was flagged. It was addressed in a matter of days. You can build the server with the /p:DefineConstants=“OSS”
flag still and you can build the clients with the bitwarden_license
folder deleted again (now they’ve fixed it).
I don’t understand why you’re throwing FUD about this. Building without the Bitwarden Licensed code has been possible for years and those components under that license have been enterprise focused (such as SSO). The client is still GPL and the server is still AGPL.
This has been the way for years.
Cool. They got that sorted nice and quickly.
Edit:
I don’t get why people think they’re suddenly doing stuff under a different license to subvert the open nature of the project. They’ve been totally transparent on what isn’t part of the GPL/AGPL licensed code for years.
SSO, the password health service, organisation auth requests, member access report blah blah have been enterprise features under the Bitwarden License for ages and they architected the projects in a clear and transparent way to build without those features since they added them.
What is up with the bird at the end?
Exactly. Source it from upstream at build time or something so it’s transparent.
You’ve been on vacation for 5+ months?
Also wouldn’t it be best to post this communication in the issue thread?
Given how long this has gone on now, it’d probably be best to inform your community that you’ll be removing BLOBs from the source and for them to be produced during build otherwise this shadow is going to remain.
This was the first time I’ve ever heard of your software and has kind of made me want to steer clear of it.
He didn’t bother to learn about outdoor survival before he left. He arrived in Alaska with little food and equipment. He was offered free food and equipment to take with him by the driver who took him to the trail but he refused.
He didn’t take a map. He was 800m from being able to get back across the river and towards civilisation but instead returned to the bus to die.
His death was avoidable and selfish and the romanticising of his death glorifies being an idiot and taking entirely unnecessary risks.
Nintendo Cease and Desist in 3… 2… 1…
Weirdly I’d say it was the other way around. Late 90s marketing used “AI” to inflate basic decision trees whereas “AI” in the context of this gun running an ANN model is a better application of the term. I’m old though; AI has been a buzzword since the 80s when every org wanted their own expert system (all pitched/marketing as “AI”). There was so much groundwork for these “AIs” that never really came to be - like the whole Semantic Web movement with RDF in the late 90s and ontologists in every major org. And now you can practically replicate that with few-shot.
I’m not suggesting we’re near Data, far from it, but that AI has been a buzz word for a lot longer than people have noticed. It’s just a lot of the technology is now commodity and in consumer products, so the average person gets marketed to also. I remember pitches about the C128 and big orgs like GM swinging around AI for things like “it’s got more RAM” and “we’re using a database”.
Computer vision stuff has been labelled AI long before LLMs hit the scene and that’ll be what’s going on under the hood of this thing too. Sinden’s light gun required a big white box/border to be drawn around the edge of the screen so that it could track the movement of the box to understand where the gun is being pointed. Which is pretty ugly and you still had to mess around with getting emulators set up to use it (thus the product was pretty niche).
If Dashine have got a model that can detect displays without the need for a border, that alone is epic. But also, by shipping a mini games console with the gun so you can just play a game with no messing about, it’ll get better sales numbers and possibly reignite interest in light gun games outside of the emulator space. Naturally there’s no light gun games on Steam, PS5, Xbox stores right now so you need the gun on the market first before you can energize developers to ship games for them. So Dashine have been smart with this and might “trigger” a return of this genre to living rooms. Fingers crossed!
This is StackOverflow after all. Your question is wrong. Your problem is wrong. You are wrong. I am right. Thread locked. Go read this other post that is totally unrelated to your problem I’ve decided isn’t the problem you’re facing because. I. Am. Right.
Nonsense. If they were perfect, wouldn’t they have used a question mark? Your judgement of character is laughable. What empirical evidence is there that they are perfect?
(How was that?)
Acclaim Studios Cheltenham was developing the game but it was cancelled due to the collapse of Acclaim and eventual bankruptcy.
Give it to meee
Nice! And MIT too. Perfect; I’ve given it a star now.