sch/Blasta
sch/Blasta
1
0
Fork 1
Code Issues 13 Pull requests 1 Projects Releases Packages Wiki Activity Actions

Each bookmark should have a "meta" title #12

New issue
Open
opened 2024-10-09 23:58:54 +02:00 by roughnecks · 4 comments
roughnecks commented 2024-10-09 23:58:54 +02:00
Copy link

It would be good if Blasta returned titles for each page with a post/bookmark. ATM it is like this:

image

So, it's always "Blasta / url" for every post, I presume.
Maybe set it to the title the original poster gave to the bookmark.

It would be good if Blasta returned titles for each page with a post/bookmark. ATM it is like this: ![image](/attachments/4cc981bd-874a-4332-9154-8aa4cd875d0a) So, it's always "Blasta / url" for every post, I presume. Maybe set it to the title the original poster gave to the bookmark.
image.png
15 KiB
sch commented 2024-10-10 07:07:53 +02:00
Owner
Copy link

Suppose, that there is a title which is too long for title.

What should be the maximum length of a meta title?

Suppose, that there is a title which is too long for title. What should be the maximum length of a meta title?
roughnecks commented 2024-10-10 07:25:16 +02:00
Author
Copy link

limit length of title upon bookmark submission

limit length of title upon bookmark submission
sch commented 2024-10-10 19:59:35 +02:00
Owner
Copy link
  1. What is the length restriction, that you propose?
  2. This is not possible, because Blasta is an XMPP client.

While it is possible to restrict accounts as long as they operate via Blasta, it is not possible to restrict account from outside of Blasta.

Suppose, someone decides to use XML Console to add bookmarks; this is entirely independent from Blasta.

What Blasta can do, is to ignore entries that exceed limitations that are defined by Blasta.

Currently, no restrictions are implemented, yet restrictions are planned.

1. What is the length restriction, that you propose? 2. This is not possible, because Blasta is an XMPP client. While it is possible to restrict accounts as long as they operate via Blasta, it is not possible to restrict account from outside of Blasta. Suppose, someone decides to use XML Console to add bookmarks; this is entirely independent from Blasta. What Blasta can do, is to ignore entries that exceed limitations that are defined by Blasta. Currently, no restrictions are implemented, yet restrictions are planned.
roughnecks commented 2024-10-10 20:21:04 +02:00
Author
Copy link
  1. What is the length restriction, that you propose?

No idea but in the Title field on Blasta I can input ~80 "o" letters. That seems more than enough to me for a title.

oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo

> 1. What is the length restriction, that you propose? No idea but in the Title field on Blasta I can input ~80 "o" letters. That seems more than enough to me for a title. oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: sch/Blasta#12
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?