I love that you had such an annoying update experience that you went ahead and created 2 memes about it and postet into a total of 4 communities, only to vent your frustration. Keep going, this is great!
I love that you had such an annoying update experience that you went ahead and created 2 memes about it and postet into a total of 4 communities, only to vent your frustration. Keep going, this is great!
The only thing I’d note is to be careful with your issue #2, because this sounds like it could break with autofill. Some autofill implementations may fill invisible fields (this has actually been an attack vector to steal personal info), so blocking the IP because an invisible field labeled “email” has been filled could hit users too. Otherwise, 100% agree!
I think this is kind of a temporary workaround. In Apples ideal world, the Vision Pro would actually be transparent and you could see the users eyes for real, but the tech isn’t ready to project what apple is doing on glasses. So they settled for a VR headset and put eyes on the outside. Eventually in however many years it takes, they will actually use glasses and won’t have to do the screen on the outside. They must believe, that being able to see Vision Pro users eyes is integral to the product, or at least important to the product being accepted by everyone.
I think loops tend to be faster, but well done recursion might be just as fast. I just wanted to mention performance being a point of consideration when making these decisions. I 100% agree that poor (API) architecture is probably one of the biggest reasons for slow software. It’s just that every bit of poor performance adds up along the way, and then we end up having fast computers (that are orders of magnitude faster than anything 15 years ago) running bloated electron apps (that are sometimes even slower than their equivalent 15 years ago) and it’s just frustrating.
I agree that junior devs should focus on readability, rather than focusing on everything and just getting it all wrong. but as you say, if you have more experience, performance should be a point of consideration.
On a side note: not caring about performance “until you find performance issues” is a huge problem with modern software imho. That’s the reason apps are so slow, updates take so long, everything uses so much space. I’d wish that performance would always be a point of consideration, not an afterthought once there are problems.
The thing is, I do see ads when I open the embedded video/playlist on youtube! I don’t think businesses would specifically avoid embedded playlists, but then happily advertise on playlists on youtube. It just looks like an oversight rather than a business decision to me.
yeah I know, makes no sense. I’ll use this workaround for as long as possible, but I’m sure I’ll have to move to Piped or Invidious sooner or later.
I selfhosted Invidious a while back, but gave up on it when it stopped working and I couldn’t figure out why. I have no experience with Piped.
I settled on a third alternative, but I don’t want to point too much attention to it because I think it might be flying under Youtubes’ radar at the moment. But let me say this: if you embed a youtube video on a third party site and have it be part of a playlist with only the video in it, you won’t see any ads. so for example I’d be embedding a link like this: https://www.youtube-nocookie.com/embed/dQw4w9WgXcQ?playlist=dQw4w9WgXcQ&vq=hd1080&autoplay=1&modestbranding=1&rel=0 on my own page and can then watch it without ads :) if you have any questions, feel free to hit me up.
EDIT: Well, I just got the first ad using this method. So it seems youtube is cracking down on all ad avoidance methods and they found this one too. Only one ad so far, so it doesn’t seem to be as bad as their own site, with (sometimes multiple) ads before almost every video, but I’m sure it’ll happen. Guess Piped/Invidious it is!
I’m completely out of the loop on this one. Can someone point me in the right direction?
That ‘S’ looks wonky somehow. Otherwise good meme!