[GH-ISSUE #186] Separators

kerem commented

2026-02-25 22:36:22 +03:00

Owner

Originally created by @marcelklehr on GitHub (Nov 5, 2018).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/186

Taken from @lightdot's comment over at #180

The separator situation in Chromium/Chrome is unfortunate. Users have requested them on several occasions but apparently they won't be added.

There are how-to's online that suggest mitigating the lack of functionality by adding specially crafted bookmarks, using bookmarklets. These seem to be very popular with Chromium/Chrome users.

Bookmark JSON for the horizontal "separator":

            {
               "date_added": "<TIMESTAMPINMS>",
               "id": "<ID>",
               "meta_info": {
                  "last_visited_desktop": "<TIMESTAMPINMS>"
               },
               "name": "───────────",
               "type": "url",
               "url": "https://separator.mayastudios.com/index.php?t=horz"
            }

generated XBEL:

<bookmark href="https://separator.mayastudios.com/index.php?t=horz" id="<FLCID>"><title>───────────</title></bookmark>

In Vivaldi, separators are supported by the browser. Unsurprisingly, their actual format is a hack, similar to the above. From Vivaldi's Bookmark file:

            {
               "date_added": "<TIMESTAMPINMS>",
               "id": "<ID>",
               "meta_info": {
                  "Description": "separator"
               },
               "name": "---",
               "type": "url",
               "url": "http://bookmark.placeholder.url"
            }

generated XBEL:

<bookmark href="http://bookmark.placeholder.url/" id="<FLCID>"><title>---</title></bookmark>

So we have those two, and from Firefox, JSON:

{"guid":"<GUID>","title":"","index":<INDEX>,"dateAdded":<UNIXTIMESTAMP>,"lastModified":<UNIXTIMESTAMP>,"id":<ID>,"typeCode":3,"type":"text/x-moz-place-separator"}

generated XBEL:

<bookmark href="data:" id="<FLCID>"><title/></bookmark>

Translating the above three hackish separators to XBEL's <separator> element and back would IMHO be safe and cover a lot of users.

Originally created by @marcelklehr on GitHub (Nov 5, 2018). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/186 > Taken from @lightdot's comment over at #180 The separator situation in Chromium/Chrome is unfortunate. Users [have requested them](https://bugs.chromium.org/p/chromium/issues/detail?id=7789) on several occasions but apparently they won't be added. There are how-to's online that suggest mitigating the lack of functionality by adding specially crafted bookmarks, using bookmarklets. [These](https://separator.mayastudios.com/?t=horz) seem to be very popular with Chromium/Chrome users. Bookmark JSON for the horizontal "separator": ```` { "date_added": "<TIMESTAMPINMS>", "id": "<ID>", "meta_info": { "last_visited_desktop": "<TIMESTAMPINMS>" }, "name": "───────────", "type": "url", "url": "https://separator.mayastudios.com/index.php?t=horz" } ```` generated XBEL: ```` <bookmark href="https://separator.mayastudios.com/index.php?t=horz" id="<FLCID>"><title>───────────</title></bookmark> ```` In Vivaldi, separators are supported by the browser. Unsurprisingly, their actual format is a hack, similar to the above. From Vivaldi's Bookmark file: ```` { "date_added": "<TIMESTAMPINMS>", "id": "<ID>", "meta_info": { "Description": "separator" }, "name": "---", "type": "url", "url": "http://bookmark.placeholder.url" } ```` generated XBEL: ```` <bookmark href="http://bookmark.placeholder.url/" id="<FLCID>"><title>---</title></bookmark> ```` So we have those two, and from Firefox, JSON: ```` {"guid":"<GUID>","title":"","index":<INDEX>,"dateAdded":<UNIXTIMESTAMP>,"lastModified":<UNIXTIMESTAMP>,"id":<ID>,"typeCode":3,"type":"text/x-moz-place-separator"} ```` generated XBEL: ```` <bookmark href="data:" id="<FLCID>"><title/></bookmark> ```` Translating the above three hackish separators to XBEL's ```<separator>``` element and back would IMHO be safe and cover a lot of users.

kerem

2026-02-25 22:36:22 +03:00

closed this issue
added the
enhancement
label

kerem commented

2026-02-25 22:36:22 +03:00

Author

Owner

@gohrner commented on GitHub (Dec 21, 2018):

Sounds like a nice feature!

@gohrner commented on GitHub (Dec 21, 2018): Sounds like a nice feature!

kerem commented

2026-02-25 22:36:22 +03:00

Author

Owner

@jantheodor commented on GitHub (Jul 1, 2021):

I've been using https://separator.mayastudios.com/index.php to seperate my bm-folders. Floccus seems to missjudge them as duplicate entries, and therefore deletes them all the time. Any ideas how I can fix this?

@jantheodor commented on GitHub (Jul 1, 2021): I've been using https://separator.mayastudios.com/index.php to seperate my bm-folders. Floccus seems to missjudge them as duplicate entries, and therefore deletes them all the time. Any ideas how I can fix this?

kerem commented

2026-02-25 22:36:22 +03:00

Author

Owner

@marcelklehr commented on GitHub (Jul 3, 2021):

Any ideas how I can fix this?

Until separators are supported there is no way for you to fix this, I'm afraid. I'll take a look at this when I'm done with my current project in August.

@marcelklehr commented on GitHub (Jul 3, 2021): > Any ideas how I can fix this? Until separators are supported there is no way for you to fix this, I'm afraid. I'll take a look at this when I'm done with my current project in August.

kerem commented

2026-02-25 22:36:22 +03:00

Author

Owner

@jantheodor commented on GitHub (Jul 4, 2021):

Until separators are supported there is no way for you to fix this, I'm afraid. I'll take a look at this when I'm done with my current project in August.

As far as I understand it, the "seperators" I am using, are simply urls, I can bookmark, that have a "favicon" which gives the impression of an actual seperator, right? Floccus, for some reason, can't differ or doesn't allow, muitliple entries, with the same url (and name, which is a blank "" in my case)? I guess it checks for possible duplicates and removes them (per entity or each layer so to say)?*

*which maybe, makes sense for many users, and from a programmers perspective, but, in my case, needs to be an option I can choose from.

@jantheodor commented on GitHub (Jul 4, 2021): > Until separators are supported there is no way for you to fix this, I'm afraid. I'll take a look at this when I'm done with my current project in August. As far as I understand it, the "seperators" I am using, are simply urls, I can bookmark, that have a "favicon" which gives the impression of an actual seperator, right? Floccus, for some reason, can't differ or doesn't allow, muitliple entries, with the same url (and name, which is a blank "" in my case)? I guess it checks for possible duplicates and removes them (per entity or each layer so to say)?* *which maybe, makes sense for many users, and from a programmers perspective, but, in my case, needs to be an option I can choose from.

kerem commented

2026-02-25 22:36:22 +03:00

Author

Owner

@marcelklehr commented on GitHub (Mar 15, 2022):

Floccus, for some reason, can't differ or doesn't allow, muitliple entries, with the same url

This is a limitation of the bookmarks app and does not apply when using WebDAV or GDrive for syncing.

@marcelklehr commented on GitHub (Mar 15, 2022): > Floccus, for some reason, can't differ or doesn't allow, muitliple entries, with the same url This is a limitation of the bookmarks app and does not apply when using WebDAV or GDrive for syncing.

kerem commented

2026-02-25 22:36:22 +03:00

Author

Owner

@tessus commented on GitHub (Mar 15, 2022):

This is a limitation of the bookmarks app

Isn't there a way to workaround that, like adding a ?random_string. Or maybe you can use a different primary key.

e.g. I might have bookmorks with the same URL but a different title on my system. Does this mean the sync will fail, or just not sync the duplicate? But I think this should be mentioned in the README either way.

@tessus commented on GitHub (Mar 15, 2022): > This is a limitation of the bookmarks app Isn't there a way to workaround that, like adding a `?random_string`. Or maybe you can use a different primary key. e.g. I might have bookmorks with the same URL but a different title on my system. Does this mean the sync will fail, or just not sync the duplicate? But I think this should be mentioned in the README either way.

kerem commented

2026-02-25 22:36:22 +03:00

Author

Owner

@marcelklehr commented on GitHub (Mar 15, 2022):

Isn't there a way to workaround that, like adding a ?random_string.

Yes, workarounds are possible. The content model of the bookmarks app makes a point of only allowing one ID per URL.

Does this mean the sync will fail, or just not sync the duplicate?

Floccus currently removes duplicate bookmarks per folder, which I will change to leaving them alone in the next release.

@marcelklehr commented on GitHub (Mar 15, 2022): > Isn't there a way to workaround that, like adding a ?random_string. Yes, workarounds are possible. The content model of the bookmarks app makes a point of only allowing one ID per URL. > Does this mean the sync will fail, or just not sync the duplicate? Floccus currently removes duplicate bookmarks per folder, which I will change to leaving them alone in the next release.

kerem commented

2026-02-25 22:36:22 +03:00

Author

Owner

@tessus commented on GitHub (Mar 15, 2022):

Thanks for the info!

@tessus commented on GitHub (Mar 15, 2022): Thanks for the info!

kerem commented

2026-02-25 22:36:22 +03:00

Author

Owner

@marcelklehr commented on GitHub (Mar 15, 2022):

The next release will have support for Firefox separators by emulating them with http://separator.floccus.org bookmarks on other platforms. Syncing with Nextcloud Bookmarks will only support one separator per folder for now, but unsynced separators will stay where you left them.

@marcelklehr commented on GitHub (Mar 15, 2022): The next release will have support for Firefox separators by emulating them with http://separator.floccus.org bookmarks on other platforms. Syncing with Nextcloud Bookmarks will only support one separator per folder for now, but unsynced separators will stay where you left them.

kerem commented

2026-02-25 22:36:22 +03:00

Author

Owner

@godfuture commented on GitHub (Apr 23, 2022):

I am also interested in Nextcloud bookmarks app in combination with floccus, but this issue with separators holds me back.

Is there a ticket in the nc bookmarks app repository?

Thanks for this nice piece of software.

@godfuture commented on GitHub (Apr 23, 2022): I am also interested in Nextcloud bookmarks app in combination with floccus, but this issue with separators holds me back. Is there a ticket in the nc bookmarks app repository? Thanks for this nice piece of software.

kerem commented

2026-02-25 22:36:22 +03:00

Author

Owner

@marcelklehr commented on GitHub (Apr 23, 2022):

Thanks for this nice piece of software.

You're welcome :)

Is there a ticket in the nc bookmarks app repository?

There is not, I can reopen this ticket to track the remaining task of allowing multiple separators per folder with Nextcloud Bookmarks, there's a hack I have in mind to make this work, despite the Bookmarks app's limitations.

@marcelklehr commented on GitHub (Apr 23, 2022): > Thanks for this nice piece of software. You're welcome :) > Is there a ticket in the nc bookmarks app repository? There is not, I can reopen this ticket to track the remaining task of allowing multiple separators per folder with Nextcloud Bookmarks, there's a hack I have in mind to make this work, despite the Bookmarks app's limitations.

kerem commented

2026-02-25 22:36:22 +03:00

Author

Owner

@godfuture commented on GitHub (Aug 5, 2022):

Now that I have all separators in place, I replaced Fireofox sync for bookmarks with floccus. Currently working just fine.

Thanks a lot!

@godfuture commented on GitHub (Aug 5, 2022): Now that I have all separators in place, I replaced Fireofox sync for bookmarks with floccus. Currently working just fine. Thanks a lot!

kerem commented

2026-02-25 22:36:23 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Aug 6, 2023):

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions[bot] commented on GitHub (Aug 6, 2023): This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

kerem referenced this issue

2026-02-25 22:38:26 +03:00

[GH-ISSUE #1377] Floccus creating hundreds of .lock files #909

Rows
Columns

[GH-ISSUE #186] Separators #176