Submitted!

Just added to my todo list. Hopefully I’ll get around to this today! Thanks!!

Thanks so much! 🎉 Native is the only way to go imo 😝. I’ll make a PR this weekend.

Might also have some comments on the Lemmy API eventually, but I’ll save those for a later date haha.

Thanks for all you do for Lemmy.

Check back in 24 hours or so. If it still isn’t available, please let me know.

What is your region?

Just posted there. Thanks!

For Mastodon there is something called Tootpick which allows you to enter your server’s domain and share any content by redirecting the user. For example: https://tootpick.org/#text=https://eventfrontier.com/post/37808. So I’m not quite sure the federated nature argument makes sense. Sure it’s more complicated that a centralized system, but possible regardless.

Apple M1 Max, Ventura 13.4.1 (22F82), Safari Version 16.5.1 (18615.2.9.11.7).

https://lemmy.world/post/1293336

Good feedback. This is meant to be extremely initial. I absolutely understand the hesitation to collecting PII. TestFlight does capture a lot of this data automatically when you sign up using a link anyways. Once it gets into beta (or even later alpha stages) I plan on releasing a public link that doesn’t require an application. I really appreciate your honest feedback tho, and I’ll definitely take it into consideration and consider alternatives in the coming days. Thanks again!

@[email protected] Thanks for the information here and all the hard work you have put into this release.

Gotta say tho, as the maintainer of Lemmy-Swift-Client, breaking API changes like this without an API version bump, make API development within the community incredibly difficult.

So my question to you would be, what is the purpose of having v3 in the API path, if the true test of API compatibility is the GetServerResponse version field? And breaking changes will occur in GetServerResponse version changes as opposed to the version in the API path? That doesn’t quite make sense to me.

Would love your perspective so I can figure out how to best design the package API to accommodate client developers who might have to contend with multiple server versions.