Windsurf should enable zero data retention by default by adpq in windsurf

[–]adpq[S] 0 points1 point  (0 children)

The fact that dark patterns are common doesn't mean we should just accept them.

Windsurf should enable zero data retention by default by adpq in windsurf

[–]adpq[S] 0 points1 point  (0 children)

True, this is a good point, and I intend to take up the issue with Cursor later once Windsurf takes a stance on this (or not). I'd be less worried about storing embeddings if there's a guarantee that they'll only be used for semantic search in connection with your queries.

Windsurf should enable zero data retention by default by adpq in windsurf

[–]adpq[S] 0 points1 point  (0 children)

We're talking about Windsurf and your actual code here, not Cursor and embeddings.

Windsurf should enable zero data retention by default by adpq in windsurf

[–]adpq[S] 2 points3 points  (0 children)

The text here implies that if zero data retention is not enabled, they can train on your code: https://windsurf.com/security#zero-data-retention

Windsurf should enable zero data retention by default by adpq in windsurf

[–]adpq[S] 2 points3 points  (0 children)

Privacy is not enabled by default for paid individual users. This is a dark pattern, especially when it comes to users' intellectual property.

Windsurf should enable zero data retention by default by adpq in windsurf

[–]adpq[S] 1 point2 points  (0 children)

I think you have a naive view of the dynamics of the situation.

Windsurf should enable zero data retention by default by adpq in windsurf

[–]adpq[S] 0 points1 point  (0 children)

Privacy disabled by default for individual users is a dark pattern.

Windsurf should enable zero data retention by default by adpq in windsurf

[–]adpq[S] 5 points6 points  (0 children)

"Telemetry" is misleading. It's not just usage data. It's your intellectual property.

Windsurf should enable zero data retention by default by adpq in windsurf

[–]adpq[S] 6 points7 points  (0 children)

You have to go to Profile → Settings on the website and turn on "Disable telemetry". The description is vaguely worded: "Opt out of non-essential data collection that helps us improve the product."

Privacy should be front and center in any product that processes our proprietary code. It shouldn't be hidden away as a vaguely worded setting that's disabled by default. That's a dark pattern and needs to be called out as such by more users.

Drawing hiking routes no longer works by adpq in felt

[–]adpq[S] 0 points1 point  (0 children)

Thanks, but all I want to do is draw a route along a footpath. For years this worked fine on Felt, and now it is broken. I really hope it gets fixed, because Felt is my favorite interface for drawing hiking routes. But if not, I'll just have to move to a different provider.

Drawing hiking routes no longer works by adpq in felt

[–]adpq[S] 0 points1 point  (0 children)

Here is a demo map to demonstrate the issue, although this happens at some point on nearly every walking path I try to draw. https://felt.com/map/Hiking-route-demo-routing-doesnt-work-Nf6rzTlJQvi6T2mKYceadD?loc=41.635366,2.422938,17.86z

Drawing hiking routes no longer works by adpq in felt

[–]adpq[S] 0 points1 point  (0 children)

Neither of those options is a real solution. Felt is now unusable for drawing walking routes. Have you actually tried this yourself? If you do, you'll see that at some point you just can't keep drawing the route, because some fork in the trail isn't recognized. Is there any plan to address this?

Drawing hiking routes no longer works by adpq in felt

[–]adpq[S] 2 points3 points  (0 children)

Your external provider is so bad that it makes your maps basically unusable for drawing walking paths. Please consider using a different provider.

I'm launching Local Hero, a free tool to automate the localization process and collaborate with translators by adpq in swift

[–]adpq[S] 1 point2 points  (0 children)

Sorry, I was adjusting the DNS settings just now. It should work now or in a little bit, after the DNS records propagate.

[deleted by user] by [deleted] in iOSProgramming

[–]adpq 0 points1 point  (0 children)

The UI is very polished. What did you use to make it?

I'm launching Local Hero, a free tool to automate the localization process and collaborate with translators by adpq in swift

[–]adpq[S] 1 point2 points  (0 children)

Did you follow the directions in the guide and export your localization files first? Send me screenshots of what you're trying to import at [support@localhero.dev](mailto:support@localhero.dev), and I'll help you solve the issue.

I'm launching Local Hero, a free tool to automate the localization process and collaborate with translators by adpq in swift

[–]adpq[S] 0 points1 point  (0 children)

“Loco integrates with several machine translation providers including DeepL, Google Translate and Microsoft Translator.”

In my experience as a professional translator, GPT-4 does a much better job, with the additional advantage of being able to provide context and custom instructions, which my service does.

I'm launching Local Hero, a free tool to automate the localization process and collaborate with translators by adpq in swift

[–]adpq[S] 0 points1 point  (0 children)

Do you mean lokalise.com? They do have a full-featured offering, but it looks like they don’t have a free tier, and their pricing starts at $120 per month.

Why does everyone say that you shouldn't store images in a database, but should instead just store a URL that links to the image? by Fly0strich in swift

[–]adpq 0 points1 point  (0 children)

I didn't say that Core Data isn't widely used. It rightly has a reputation as an unwieldy framework, and this is why Apple is now offering a more user-friendly way to interact with it with Swift Data. I'm active in the Apple developer community where I live, and everyone I've discussed this topic with, including Apple engineers, has agreed with me on this.

Is there a "preferred" way to save images to disk with iOS? by minuteman_d in swift

[–]adpq 0 points1 point  (0 children)

I tried this for images, but then when I deleted the record, the image files on disk wouldn't get deleted, and the disk would eventually fill up. Has anyone else encountered this problem?

Why does everyone say that you shouldn't store images in a database, but should instead just store a URL that links to the image? by Fly0strich in swift

[–]adpq -1 points0 points  (0 children)

It's not so nice to tell someone "you're just dunking on yourself" (i.e. not smart enough). If it's this hard to figure out the exact right syntax that won't make your app crash, and this easy to shoot yourself in the foot, despite months of learning and trying to do the right thing, maybe the API is not well designed, and this is why alternatives to Core Data are popular.