Submitted!
Software Engineer (iOS - ForeFlight) 🖥📱, student pilot ✈️, HUGE Colorado Avalanche fan 🥅, entrepreneur (rrainn, Inc.) ⭐️ https://charlie.fish
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.
At this point it’s like, why not use Ethernet?
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!
Feels like this would just be adding on a centralized feature to a system designed to be decentralized. If anything, it should be based on a decentralized system like Bitcoin or something.
The craziest thing is that Elon’s tweets are still completely visible.
So if you were moving to another home or apartment, is it a reasonable strategy to stop paying rent at your current home while you’re looking for a new place? Of course not. Same idea here.
Ads too 😉
@dessalines@lemmy.ml 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.
I know I’m not necessarily the target audience for this. But it feels too expensive. 6x the price of Cloudflare R2, almost 13x the price of Wasabi. Even iCloud storage is $0.99 for 50 GB with a 5 GB free tier. But again, I know I’m not necessarily the target audience as I have a lot of technical skills that maybe average users don’t have.
If you ever get around to building an API, and are interested in partnerships, let me know. Maybe there is a possibility for integration into !echo@eventfrontier.com 😉.