Author Topic: NANY 2018 Release (preliminary alpha-or-so): ymarks (Read 51883 times)

rgdot · « **Reply #50 on:** June 16, 2018, 10:47 AM »

https://venturebeat....r-chrome-extensions/

Google today announced that Chrome will no longer support inline installation of extensions. New extensions lose inline installation starting today, existing extensions will lose the ability in three months, and in early December the inline install API will be removed from the browser with the release of Chrome 71.

wraith808 · « **Reply #51 on:** June 16, 2018, 11:14 AM »

Wait. What? Why?
-Tuxman (June 16, 2018, 10:01 AM)

I was surprised I hadn't seen anyone raging about this:

https://venturebeat....r-chrome-extensions/

Tuxman · « **Reply #52 on:** June 16, 2018, 01:31 PM »

Ha, nice. So I'll have to release an official Chrome version by Autumn.

Tuxman · « **Reply #53 on:** June 29, 2018, 03:03 PM »

I uploaded a Chrome version to the Web Store. I'll update the website once Google is blind enough to accept it.

edit:
https://chrome.googl...gfjfbjjobmegihhaacfi

skwire · « **Reply #54 on:** August 21, 2018, 12:24 AM »

I finally got around to trying this out. Apologies for the delay and nice work so far.

The server component is running on my server box.
I installed the Chrome extension in Vivaldi, configured the endpoint and PIN, and uploaded Vivaldi's bookmarks with no issue. A ymarks.db.backup.1 file was created.
I installed the Chrome extension in Chrome, configured the endpoint and PIN, and chose the "download bookmarks" option. Chrome successfully pulled the bookmarks.
I installed the Firefox add-on in Firefox v61.0.2, configured the endpoint and PIN, and tried the "download bookmarks" option. Unfortunately, it simply wiped out all the Firefox bookmarks (which were easily restored with a backup ).

I'm happy to help debug or whatever you need. If there are IE and Opera plugins, I'd be happy to test those, too.

Tuxman · « **Reply #55 on:** August 21, 2018, 01:29 AM »

Hmm, that's not good. I received a similar report yesterday. Something must have changed. It had worked in the past.

I'll be out of town until tomorrow, but what I need for a reasonable fix is, at least, a useful error message. Does the server print anything while you're using Firefox? Does Firefox's error console (F12...) tell you anything after clicking Download? Is there a pop-up from the extension?

Tuxman · « **Reply #56 on:** August 21, 2018, 01:42 AM »

I suspect that Firefox 61+ has made changes... do you happen to have that version? Because nobody with Firefox 60 has complained yet.

skwire · « **Reply #57 on:** August 21, 2018, 09:37 AM »

I'll be out of town until tomorrow, but what I need for a reasonable fix is, at least, a useful error message.
-Tuxman (August 21, 2018, 01:29 AM)

Unfortunately, there does not appear to be one.

Does the server print anything while you're using Firefox?
-Tuxman (August 21, 2018, 01:29 AM)

I don't see anything, but I might not be looking in the right place.

Does Firefox's error console (F12...) tell you anything after clicking Download?
-Tuxman (August 21, 2018, 01:29 AM)

I looked through all the tabs of the dev console but didn't see anything pertaining to ymarks. Again, though, I might be looking in the wrong place.

Is there a pop-up from the extension?
-Tuxman (August 21, 2018, 01:29 AM)

No.

I suspect that Firefox 61+ has made changes... do you happen to have that version?
-Tuxman (August 21, 2018, 01:42 AM)

Yes, as above, I'm running Firefox v61.0.2.

Tuxman · « **Reply #58 on:** August 21, 2018, 09:41 AM »

I don't see anything, but I might not be looking in the right place.
-skwire (August 21, 2018, 09:37 AM)

It's in the server window or nowhere.

So if there is nothing, the server does not even get the request properly.

I looked through all the tabs of the dev console but didn't see anything pertaining to ymarks. Again, though, I might be looking in the wrong place.
-skwire (August 21, 2018, 09:37 AM)

Usually, the second tab with everything "enabled" and no filter set should be enough ...

Yes, as above, I'm running Firefox v61.0.2.
-skwire (August 21, 2018, 09:37 AM)

Argh. Sorry, I started typing without reading properly.

I will look into it in 28 hours!

Thank you.

skwire · « **Reply #59 on:** August 21, 2018, 10:49 AM »

I will look into it in 28 hours!
-Tuxman (August 21, 2018, 09:41 AM)

No worries. Cheers.

Tuxman · « **Reply #60 on:** August 22, 2018, 03:25 PM »

I found and confirmed the problem. Pushing 1.1.0b4 to AMO. Still considered experimental.

skwire · « **Reply #61 on:** August 22, 2018, 04:07 PM »

I found and confirmed the problem. Pushing 1.1.0b4 to AMO. Still considered experimental.
-Tuxman (August 22, 2018, 03:25 PM)

I grabbed 1.1.0b5 from the extension page and it seems to have fixed the issue. I didn't check every bookmark but spot checks here and there looked good.

Thank you for the fix.

Tuxman · « **Reply #62 on:** August 22, 2018, 04:13 PM »

I'm not perfectly sure if it is a fix yet - I actually just worked around the problem (by ignoring one more error state).

Let's wait for more feedback to intrude from AMO.

Thank you for testing!

Tuxman · « **Reply #63 on:** September 05, 2018, 08:29 AM »

Firefox will drop support for bookmark descriptions "soon". I'll probably update the add-on around that time.
edit: If that will break ymarks, that is.

skwire · « **Reply #64 on:** September 10, 2018, 01:03 PM »

Tuxman, can you explain how the PIN option works? Please and thank you.

Tuxman · « **Reply #65 on:** September 10, 2018, 01:07 PM »

It is not an option. It is more like a mandatory password protection so only you can access your server unless anyone wants to try up to INT_MAX numbers.

I recommend to change the default PIN to a different number. Create a file named PIN.txt and write a number into it. Done.

skwire · « **Reply #66 on:** September 10, 2018, 01:45 PM »

Create a file named PIN.txt and write a number into it.
-Tuxman (September 10, 2018, 01:07 PM)

That's the part I needed to know, thanks. Did I miss that in the docs somewhere?

Tuxman · « **Reply #67 on:** September 10, 2018, 01:57 PM »

Yup:

If you run the server locally and you haven't changed the port and PIN, the server runs on http://localhost:8888 and the PIN is 12345. The README mentioned above tells you how to change them if you feel like you should.

From: https://ymarks.org/about

The linked README is here:

https://bitbucket.or...-server/src/default/

It says:

(Optional) Place a file named PIN.txt in the same folder as the compiled binary is in order to change your PIN from "12345" to something else. It will have to be a number though.

I should probably write a more obvious documentation, but I'm lazy. Mind to help me out?

Tuxman · « **Reply #68 on:** November 10, 2020, 05:31 AM »

In a relatively large update published today, I changed the license and I introduced a new build system. No more dependency hunting!

1. Install Conan and CMake.
2. mkdir build ; cd build ; cmake ..

Also, I fixed some links on the website and the repository is here now:

https://code.rosaelefanten.org/ymarks
Mirror: https://github.com/d...rtuxmalwieder/ymarks

Enjoy.

Tuxman · « **Reply #69 on:** February 23, 2021, 11:08 AM »

I was notified that Chrome seems to scramble my server messages. Can anyone confirm/deny that?