Matrix is even more overwhelming than slack in the same sense that email is more overwhelming than lotus notes. Maybe overwhelming is fine if the use for the tech isn't siloed to solving communication in only one part of their life.
The CC licenses should probably be adjusted to make a DMCA attempt a permanent revocation of license. That way DMCAs can flow in the opposite direction and people can learn things.
Realistically speaking, you’d still need to enforce breaches of whatever license you choose but most open-source projects don’t have the resources to pursue those cases.
Maybe there’s a case for a consortium of open-source projects that can pool its resources and serve as an insurance policy to fight back against license violations or malicious/stupid DMCA takedowns.
We have so many organizations but in the last 2 decades nobody has thought of creating colloborative legal fund and insurance system to combat and in many cases enforce licensing violation.
Open source projects should have a kind of union of their own. Then again I wonder if it would ever be possible because corporate money has became a key donation source and in many cases many OS projects themselves have become corporatized.
Whenever you file a DMCA appeal with GitHub/etc you would have the option to file a takedown on the jack ass. Some projects doing it occasionally would trigger the right conservative fears at corporations to reduce the market.
We already have precedent for this kind of thing too, for patents. For example, the Mozilla Public License says this:
> If You initiate litigation against any entity by asserting a patent infringement claim (excluding declaratory judgment actions, counter-claims, and cross-claims) alleging that a Contributor Version directly or indirectly infringes any patent, then the rights granted to You by any and all Contributors for the Covered Software under Section 2.1 of this License shall terminate.
Ah, you are too optimistic about the desktop in general. Landlines and desktops failed in the developing world first. It is contracting back to workstation users of old (STEM academia, IT, graphics) and maybe Adobe will do their hold out again like refusing to properly support windows when Mac was in the hole but they should get pretty desperate as the gateway platforms to their products become unwanted by the general population.
Reading the article of December 2nd it seems accurate to me. Ubiquiti was wrong about the scope, that the incident was external. It says the suspect was pretending to be a whistleblower. It sounds to me like the suspect wasn't a liar when whistleblowing so what would Krebs retract?
1. Sales time is free. Even with established clients they are likely to work project by project and expect detailed quotes/estimates and initial discussions that take a lot of time, then there's billing and general business handling..
2. There is a forever war between large generalist consultants and niche consultants. Working ~alone you will probably have to be an expert in a niche and there is always business pressure to use a large consultant for everything even if their work is sub-par. (Accounts payable, etc, don't care about quality of consultants but about number of tasks.)
Planning for these factors is important, and combined with having no one to bill for more general maintenance hours and attempts of various orgs to get their "standard discount" for volume, being a startup, or being an NGO it is important to make sure you ask for a high enough rate. With contracting, seeking 1.5-2x is a minimum in most tax systems, with consulting at least 3x your intended income from an equivalent full time job.
Making OSes or browsers you are in a market share competition whether you like it or not because that dictates a lot about changes to how the environment deals with you in the future. One can ignore the least engaged/satisfied/likely-to-contribute users and their perceptions at one's peril.
Cool, it is a lot to start researching but you sound like you use a very similar style to things I am used to in other languages.
On guice/gwizard/maven, if I understand correctly I would be defining new guice DI for something like a message broker (and gwizard's solutions for similar modules might serve as a template) while probably just using direct dependencies in maven for something that doesn't need to be mocked in unit tests or replaceable in production?
You could make a new guice module for the message broker, but you don't have to. If you want to use a message broker, just bind the service object as an eager singleton in your application module.
The main reason to make a separate guice module for the message broker is if setup requires a lot of boilerplate. You can put it all in a common jar artifact and include that in different services. But that's overkill if you just have one service, or if the broker has a fairly friendly interface to start with.
Guice is just a little bit of structure to bind together Normal Java Code. You don't need to wrap services or do things eg "the spring way". Just use the service; if you find yourself repeating code, consider abstracting it into a separate module.
What's the use of being a shill for civilisation ending environmental policy? I think Dr. Strangelove himself demonstrates the character profile..
If the world is going to stick to a sanctions plan it needs to destroy all those pipelines now and sanction Russian Oil, shutting down only the parts of Russia's economy that don't reinforce Putin's power is only going to work if it has been done early enough and it has been over 2 decades, so probably it is not.
Because when you have a lot of money, you can loan money at really low interest rates. Rates that are lower than the rate of return on the investments you'd have to sell to avoid the loan in the first place. If banks are willing to give you really cheap money, you take it.
They also have many many billions sitting in cash accounts with CS earning 0 (and in some account negative rates).
But yes, deals are much easier to structure as 100% debt and the investment, maintains liquidity and limits liability. Set up investment co, borrow with gaurantee from parent etc.
Matrix is even more overwhelming than slack in the same sense that email is more overwhelming than lotus notes. Maybe overwhelming is fine if the use for the tech isn't siloed to solving communication in only one part of their life.