Comment by ~mlb on ~mlb/linkhut
Made a fix for this in: https://git.sr.ht/~mlb/linkhut/commit/80a3433319166a866d2129f8e1cae242ec5b436e
This is now deployed in the flagship instance, feel free to test it out and let me know if it's still not what you expected.
Comment by ~mlb on ~mlb/linkhut
Nice catch, the implementation only tracks insertion date. Will put together a fix shortly.
Comment by ~mlb on ~mlb/linkhut
It's interesting that it cut just before the single quote (
'
), depending on how you invoked the API it could have been the result of not escaping appropriately the string payload.As for the size, it seems to be below 500 chars, so well within the limit of the notes field.
$ wc -c << EOF “I’m sorry that I long ago coined the term “objects” for this topic because it gets many people to focus on the lesser idea. The big idea is “messaging”.“ I dunno—I think everyone who survived SICP will run up to the limits of message-passing dispatch sooner rather than later. I’d rather have multimethods (which is why I implemented pattern-matching generics that can dispatch on any predicate, not just interned strings). But, standing on the shoulders of etc. EOF 482
Comment by ~mlb on ~mlb/linkhut
Marking this as duplicate of #11 so we keep the conversation about this topic in a single ticket.
REPORTED
RESOLVED DUPLICATEComment by ~mlb on ~mlb/linkhut
Could you share some examples? There are hard limits in the schema for the title and the notes of a link, but I'm surprised that the request succeeds with a truncated string instead of simply failing.
Comment by ~mlb on ~mlb/linkhut
The way to do this (at the moment) is to first call
posts/get
and follow it with aposts/add
with the new tag andreplace=yes
.I'll be the first to agree that this isn't the most ergonomic API, but I think there's value in offering the same semantics as the delicious and pinboard APIs to leverage the wide variety of open source clients available that implement it.
Comment by ~mlb on ~mlb/linkhut
Thanks!
I was planning on adding support for showing the user's most recent and most used tags as well as any public tags already associated with the entry being added. I had this fairly low in my list of features, but I think I'll pick it up right after the next release which is a refactoring of the schema for user settings.
I'll update the ticket when I start working on it, so I can get your input on how you would like it to work.