I have been following RA for years now. There is a small public company (OMX:SYNACT) I found that are in its Phase 2b with a medication that looks very promising. They completed their Phase 2a with statistical significance in a couple of key indicators. It looks like to be on par with JAK inhibitors but with a cleaner safety profile and no need for injections.
Unlike the JAK inhibitors that suppresses the immune system, their pill instead resolves the inflammation by activating receptor 1 and 3 in the melanocortin system. Phase 2b completes this summer and I am personally super excited to see the results.
When looking at the linked archives [1] it seems that they sit at around 4GB/day. Is that really all of the data that the US stock market generates a day? I thought it would be at least 10x that.
As a vendor you can add a license / subscription for your stack in your 1-Click App image. Some vendors –such as Plesk and cPanel– are already doing this today. We plan to make this easier for both you and your users this year with direct billing.
@eddiezane, recurrent billing/subscriptions would turbocharge the use of your marketplace for paid images. It would allow vendors to charge a lower upfront amount, which would lower the barrier to experimentation. Users could dive in and, if they like the software, keep the droplet + subscription going indefinitely.
A very DigitalOcean twist would be if you allowed the subscriptions, like the droplets, to be billed per hour.
For instance, a user could deploy a $5 droplet to test a $2 per month image. If the user terminates the image within one hour, the total cost would be 7c for the droplet and 3c for the paid image, totaling 10c. If DO takes a 30% cut, the vendor receives 2c (woo-hoo!). It would be, essentially, a free trial, but with the benefit of establishing the precedent, in the user's mind, of paying for good, supported, server software.
If, however, the user wants to continue using that image, they will pay $5 every month for the droplet and $2 for the image, of which the vendor receives $1.40 every month.
Another very DigitalOcean twist would be if the vendor had the option to charge a percentage of the droplet price, allowing them to charge less to users of the cheapest droplets but more to users of large droplets who are, presumably, deriving more value from their use of the image, and would be more likely to require support from the vendor.
For example, the vendor could set his price at 20% of the droplet cost, meaning that a $5 droplet would cost an additional $1 per month or 1.5c per hour (of which the vendor would receive one cent).
The vendor would make the money necessary for a viable business on larger droplets. For example, on an $80 (16GB) droplet, the image cost would be $16 per month, of which the vendor would receive $11.20.
An image with a hundred or so large users and a few thousand small users would become a viable business that the vendor could energetically promote outside DO, pulling more users into the DO platform.
My hope is that DigitalOcean will approach this marketplace with imagination, not make too many presumptions about how it should evolve and allow actual demand to shape it. While it is good to showcase the images that are going to be useful to a huge number of users, such as the generic WordPress image, your marketplace could truly soar by allowing a vast hinterland of lesser-used images, that, cumulatively, would result in far more usage. Let a million forks bloom. It would differentiate you from all the other hosts who offer one-click generic WordPress.
For example, imagine if thousands of WordPress plugin and theme creators decided that pointing towards their DO Marketplace image was the easiest way to get their customers up-and-running, and the most effective way to continue getting paid for their work. At a stroke, DO would be harvesting a 30% cut of the massive paid WordPress market AND attracting a vast number of new users to your platform.
Not just WordPress, of course, this applies to all forms of server software. DO is in a unique position here to create something akin to the explosion in mobile software development that the App Store sparked in 2008. It would allow thousands of independent developers to create thriving businesses that deliver real value to millions of users, while truly differentiating DigitalOcean.
Could you father children while being on TRT? I have heard that there is a chance that you can become infertile while on it, and after you quit, there is a chance that your "system" does not start up again.
Yes, TRT doesn't make you sterile. But it likely lowers the quality of your sperm. There is a small chance of becoming infertile and there's a small chance your system won't start up again if you decide to stop. Generally though, for people that have naturally low levels and are on TRT, they wouldn't want to stop and return to those levels after experiencing life at normal/high levels.
I'd love a tool that lets you keep a history of "cloud migrations", where you write both the "up" and the "down".
We did a dirty solution for this with Ansible. We have a base playbook (with roles and all that jazz) that sets up a server and then we can write patches which are separate playbooks.
After the patch has run we simply store the patchlevel in a file on the server so that we dont "double-apply" any patches on the next patch-run.
I feel really worried about the Kernel project now that they have let Identity Politics breach their walls. These kind of things have a tendency to split a community rather than unite it.
The kernel project is surely one of the most successful software projects ever. Having survived for 20 years, why change a winning formula?
I have always considered Linus un-political and more interested in getting sh*t done and getting it right above anything else, so why he would sign-off on this is a mystery to me.
I don't think it was, at least not that black and white. If the community really was that split the project would not have survived for 20 years. Surely we would have seen a fork where the involved factions split off.
I think this is a very vocal minority in play here. From my understanding these changes did not come from any of the core contributors but rather from activists. The used divide and rule; if you don't sign off on our political documents you are with "them" and we will let everyone know what a horrible human being you are.
It seems the loud voices about how bad the CoC is aren't actually kernel devs...
But there is atleast one known kernel dev who spoke up about Linus' behaviour, and eventually just quit developing for the kernel.
edit: not to mention those who don't want to touch the kernel because of his behaviour. one guy said the only contributions he makes to the kernel are for his employer. if it wasn't for that, he'd not touch it.
For the 30 years where it was one project, the community was split? And now that it has been forked because of outside political issues being forced in, that's the same amount of split as the last 30 years?
Either that, or some people tend to see "vegetarianism" and "dictatorship/genocide" as orthogonal, while seeing "low-life scum on the internet" and "complaining about too much political correctness" as not orthogonal?
Should the separation not be between ``low-life scum on the internet'' (the far right) and ``not being explicitly politically correct'' (being apolitical)? ``We need more political correctness'' (the far left) is on the reflected axis of ``complaining about too much political correctness'' (the far right).
>evoking Hitler was a bad way to make your original argument
You'll notice that I was reducing to the reduction to Hitler, not reducing to Hitler himself. And this is not such a long stride to take, as the reduction to nazism had already occurred in the quote that I was criticizing.
[1] https://avro.apache.org/
[2] https://parquet.apache.org/