I do essentially both: robots.txt backed by actual server-level enforcement of the rules in robots.txt. You'd think there would be zero hits on the server-level blocking since crawlers are supposed to read and respect robots.txt, but unsurprisingly they don't always. I don't know why this isn't a standard feature in web hosting.
For my personal stuff I also included a Nepenthes tarpit. Works great and slows the bots down while feeding them garbage. Not my fault when they consume stuff robots.txt says they shouldn't.
I'm just not sure if legal would love me doing that on our corporate servers...
Since nobody has mentioned: iOS 17 and macOS Sonoma brings family sharing to password managerm. Sonoma also brings support for using native passwordsl manager in Chrome using a chrome extension developed by Apple.
For families who are hooked into Apple's ecosystem, this can provide a much better password management than third party tools.
Note: This is sort of true but is highly misleading.
csv export is only possible on a Mac (https://discussions.apple.com/thread/251108577). So, iPhone/iPad/PC users are pretty much out of luck Additionally, I don’t believe passkey’s are exportable at all.
Lack of actual functioning backup options is the primary reason I’m not using iCloud Keychain, so I would love to have these issues fixed.
I have been looking to move away from 1Password and did look into this. The thing that prevented me from doing so is that if someone got access to your AppleID (through phishing or social engineering), it allows them to essentially take control of your entire online presence. Right now, I try to keep the single point failures to a minimum (ie don't keep Apple ID in password manager). Is this a concern that's worth thinking about or am I just shifting the problem from one place to another?
Understood that you are not native english speaker and use AI to enhance the content.
I would advise to ask AI to share some ways to make the content more concise and incorporate learnings from those suggestions rather than copying them directly. That would keep the human element still around.
These days, I personally find articles with minor grammatical errors more interesting than AI assisted/enhanced/corrected content, because AI generated content often comes off bland and loses the rawness of author's intentions. Just personal opinion of course. :)
It's ' -- the reviews show how' in the title instead of summarising how or even just not saying that that does it for me, I won't click something like that.
Not sure if you are actually developing the emails or not, but from a front-end developer's perspective, I hate to touch my email templates codebase because it has to be coded in certain way that works with the email provider.
I cannot see what the end result is going to look like until I actually send out a test email and see it in my email clients. This DX indeed feels like 2010 if you compare it with today's DX for developing websites.
Not really "a lot". When you think about providing absolutely best user experience, you gotta leave the engineering efficiencies out at the doors and live with the redundant API calls. The over optimization often comes with sacrificing the UX.
It’s possible to make fewer requests without negatively impacting the user experience. For example, batching requests would result in a more responsive app.
He specifically cited situations where the opposite is true - for example when first opening a subreddit, he requests only 25 posts so the UI can render something quickly, then requests a further 100 posts to prepare for the user scrolling.
He could just request 100 posts first, halving the API requests, but the app would be less responsive.
Your comments seem to have a confidence level that their content doesn't justify.
That’s a great example of something that could be optimized without impacting the user experience. For example, just request the next page of posts when the user starts to reach the bottom. The reason for my confidence is that I’ve worked with Reddit’s API before and I know exactly where the pitfalls are.
That’s too late to be sending the request if you want the premium feeling of no loading times while scrolling, especially if you also want to do rich thumbnails of media.
Speaking from a mobile dev's perspective, the native UI design in 2010s was done by XML based files (storybooks in iOS/macOS, XML layout files in Android) and native code would "connect" with the XML files in various ways. Now the development is moving towards declarative approach using frameworks such as SwiftUI and Compose.
This builder pattern resembles quite a bit of how you would declare UI in SwiftUI and Compose.
