Honestly all I want is for Spotify to differentiate between music I actually like to actively listen to and music that I like to play in the background 24/7 (e.g. chill hop)
Same, my spotify thinks I'm very obsessed with Ambient and Classical. I mean I enjoy those genres, but they're not my typical "active listening", I just always want some sort of sound going on in my apartment.
Also whenever I'm DM'ing a D&D game the majority of my daily mixes change to video game music for weeks because I use them as backing music.
Spotify's daily no es solve that problem for me. I always have one or two mixes with chill-hop music accumulating things I listen to when working, plus different mixes with different genres and 0% ambient music.
I wish other websites had similar recommendation systems. Spend an afternoon watching shitposting videos and YouTube will only recommends low-effort videos.
I feel Spotify makes a half decent jab at identifying moods with their "Daily Mixes" feature. Right now for me it's identified 6 sort of genres that I listen to.
It didn't identify that one of them is hip hop, and the other one is dutch hip hop, which obviously to me are the same genre, but that's alright.
It's got a classical music mix, one for rock, one for soundtracks and one for electronic/lo-fi.
It would've been cool if it knew to group electronic/lo-fi, classical and soundtrack together as my background work music, but I'm not sure how it would've learned that as normally I have to pick one of those genres while working, I have no playlists that mix them.
I've wanted this for video streaming too. After getting rid of cable, I'll often want to put something on in the background while I'm browsing the web or playing switch or something. I feel like almost everyone has a completely different thing they are looking for in active vs passive consumption and being able to tailor it would be very nice. Very straightforward example: I really don't need subtitled shows when I will be half paying attention at best. I also don't want to watch something that is new to me and also "good" when I won't really be paying attention.
If you're on Family plan, you could sign up for a separate account and use it for background music only. Kind of a hassle, but that's what I'm doing with YouTube so that relaxation recommendations aren't mixed with lectures.
Hey, Kamal from DigitalOcean here. I'm sorry that happened to you! You're right, managed Redis Databases do not support backups[0] currently. I found the page on the website that says they do and let the team know. They will correct it asap.
Hey Kamal, good to see you here. I'm sorry to hijack this thread, but I'm hoping someone from DO could provide an official response to this often-cited post on HN regarding security issues on your K8S offering: https://news.ycombinator.com/item?id=22490390
Is there a chance you could poke someone into looking into this?
I'm the tech lead for Kubernetes at DO. Just wanted to jump in and provide some clarification around the security issues you brought up.
The blog post you're referring to came out in December 2018, shortly after we released DOKS as a Limited Availability offering. By the time we announced our General Availability release in May 2019, we had done the following:
1. Changed our node bootstrapping process so that etcd information is no longer necessary in the metadata API, and removed said etcd information from metadata.
2. Firewalled off etcd so that it's accessible only inside the cluster.
3. Shifted how we run the CSI controller component so that a DO API token no longer needs to be stored as a secret in the cluster.
4. Switched from Flannel to Cilium as the CNI plugin, which allows users to configure network policies. We don't configure any network policies by default, but the option is there for users who want to use them.
These changes fix the vulnerabilities explained in the blog post. We do have further hardening measures planned, including limiting the scope of API tokens (one of the suggestions from the blog post, and also an often-requested feature from DO customers), but that's a big project so we can't provide a firm timeline for it at this point.
Hope this clarifies the current situation. If you or anyone else finds new security issues with DOKS (or other DO products) we would love to know about it. Our security team is always accepting vulnerability reports via their disclosure program: https://www.digitalocean.com/legal/contact-security/
Hey, I ran this by the DOKS team and they confirmed that this was taken care of a while back. Just to clarify, that issue existed while the product was in Limited Availability (think alpha). Nodes are now bootstrapped in a different way that eliminates the need to expose sensitive info in metadata or anywhere within the cluster itself.
Kamal from DigitalOcean here. With only a primary node and no standby nodes, a failure will cause a new replacement node to be created with its data being a combination of the latest backup and the write-ahead log. This will get you the most recent data possible. Check out this page for more info on auto failover and how it works with the different configurations: https://www.digitalocean.com/docs/databases/resources/high-a...
How is the WAL stored? If there is a problem with the storage, networking, or DC, you will not be able to get the WAL in order to bring up the DB in a new region. Also, the process of replaying WAL since last backup can take a very long time for a high traffic DB, during which time it is going to be completely unavailable.
The WAL and all backups are stored offsite and are completely handled on our end.
Re: availability, that’s right if you only have a primary node and no standby ones. Like manigandham said, there won’t be any downtime if you have a standby node.
Thanks. Will you offer a synchronous version in the future?
Since asynchronous means that you can lose previously acknowledged writes when the primary node crashes, which forbids many use cases (for example, most things involving money).
And Postgres already offers synchronous replication modes.
We used Lucene (open source) in our information retrieval course and tokenizing (w/ removing stop words etc.) is one of the things it does. If you just want to experiment, that's also another option to look at if you like!
Yep. That’s where docker compose comes in. It takes care of the whole process of linking together different docker containers as well as configuration of each of them (such as env vars).
Compose is just a declarative syntax for your stack. Ironically it's not composable. In other words, it's not a package definition--you can't ship a compose file that will "just run" anywhere. For example, most web apps require a database, but you don't want to run one database per web app. How do you write a compose file that says, "use the system postgres if available, otherwise spin up a new one". It also totally punts on secret and config management.
Helm is the closest thing to a package manager for Docker, but it targets Kubernetes, not vanilla Docker (and k8s is overkill for a single server, at least considering the time/expertise required to stand up a productionized k8s installation).
(not OP) It is for a side project that gets very little traffic. I'm still paying that $5/mo just to play with this tech but I can't say it's not too much for my use case. I guess that's not the target market for Workers anyway
Overall I think it looks great! Not too much going on and it’s easy to read. I’d suggest you experiment with adding more whitespace between different sections and especially between different projects. I’m on mobile, btw.
