#ui · textlog

wrote:

cool new for ! autotag action will enrich your post with relevant hashtags so you don’t have to do it manually. It uses an to do it so it is quite good. Try it!

…

replied to:

I will try it out, but it wasn’t super-easy to find. Maybe it’s just me, but I was looking in the first, and later I hit “more” and only saw all the other . Until I suddenly saw “” in fine print at the top of the “more” for the . Probably it’s just I who need sharper glasses:)

replied to:

Cool. If you run every post via this auto tag feature, then the process is vulnerable to prompt injection attack. Isn’t it? Do you have any special protection in place? I guess yes. Curious.

replied to:

It doesn’t run on every post, you run it yourself via more → autotag, and it’s safe, it doesn’t have access to anything other than the post content and we simply use its response. Or do you have any other case in mind?

replied to:

I just tried and i do believe it is possible to craft malicious prompts. I can share an example. How do i DM you?

replied to:

Check the IRC at the footer or you can send to ‘abuse@textlog.cc’ so I find it.

replied to:

Sent email. .

…

replied to:

Thanks! Fixed it by passing it through OpenAI’s moderation endpoint first, so it now blocks at least the problematic/illicit ones now before reaching autotag.

replied to:

Makes sense. Cool.

wrote:

Major on the / for desktop users, all handles and hashtags are now showing a popover on hover so you can quickly see the profile and hashtag information and follow them.

continued:

Also, tag pages now have a tab followers so you can see the people following a tag you like and follow them.

wrote:

I’m running out of ideas what else to do and asking to suggest me / improvements. A lot of its suggestions are good but a lot are banal as well.

…

continued:

and I thought the site was finished and I had nothing else to add when I 'ed it. How naive. I've done so much work since then and every day is full of issues to work on.

continued:

Ran out of issues to work on, again. I hate it when this happens. Moving too fast with has this disadvantage, no time to think ahead. Any ideas?

replied to:

Something that came up recently was a css only implementation of showing when we have hit the character max count before you click submit. Unlike the JavaScript implementation which can show you a dynamic count, this cannot but it is cool and is lightweight

replied to:

It’s impossible with css I’ve investigated.

replied to:

Here is a demo I put together with Claude kus1987.neocities.org/nojsdemo

…

replied to:

Thanks! I used the auto-grow field-sizing trick! Works well. The other trick has issues with prefilled textareas, so it fails in bio textarea and when editing a post/preview/draft. Also I was talking about counting the characters or showing some sort of progress bar, that’s impossible as well. The <textarea> maxlength hard limit is fine. With the new 500 char limit you’d hardly notice it as well.

replied to:

🎉

wrote:

y'all!

replied to:

Morning! What's on the docket today?

replied to:

Improving textlog of course. There are a ton of tiny and some not so tiny / improvements waiting tbd. Question is which ones now?

replied to:

Minor bug in docs: I noticed in the API docs the feed url says ../users/name... but it's actually ../u/name... by the way.

replied to:

It's not a bug. Under the API base URL it works, /api/v1/users/stagas/posts.rss, but those are aliases they work too. Thanks however!

…

replied to:

In the middle of migrating very old, homegrown tomfoolery into a more modern stack. Fun and vexing at the same time. This codebase has all of the bad decisions. All of them.

wrote:

I love fixing all those tiny / details that nobody notices but me.