Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

One-Click Postage: Don't use outdated API endpoint #2137

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

marcustyphoon
Copy link

One-Click Postage is relatively similar to Quick Reblog in XKit Rewritten, so doing this instead of just breaking it doesn't preserve much functionality (sure, autotagger, multiline captions, yeah, yeah, whatever). I don't see this as as important like I do #2106.


This migrates One-Click Postage to use the modernized backend code that XKit Rewritten's Quick Reblog does instead of the legacy and presumably-someday-removed SVC endpoint when possible (i.e. on React pages).

It removes the share to Twitter/share to Facebook and caption replace options as well as an old option to use a different notification style. Off the top of my head, social media sharing is gone, caption replacing is not a thing post-NPF, and the other notification style didn't work on most pages anyway.

@nightpool
Copy link
Member

Is this currently broken? I use OCP pretty often and I haven't noticed anything

@marcustyphoon
Copy link
Author

It converts threads to legacy, presumably breaking interoperability with Trim Reblogs. I don't think we want to be doing that.

@nightpool
Copy link
Member

nightpool commented Sep 28, 2023 via email

@marcustyphoon
Copy link
Author

I don't think we should regress in features

Are we regressing in features?

I don't think we should be taking half-joking speculation from two staff members on one potential path for
the SVC migration as gospel. I agree we should move to a NPF endpoint for this code eventually

I guess I don't understand how these two points mesh together :D If we are going to migrate at some point, why not now? If we aren't going to migrate at all, then sure.

It seems to me like I'm viewing the creation of legacy posts as a regression and you're viewing it as a feature; is that accurate?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants