Github messages for voidlinux
 help / color / mirror / Atom feed
From: TeusLollo <TeusLollo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: VLSub not automatically loading subs
Date: Tue, 18 Jul 2023 03:28:04 +0200	[thread overview]
Message-ID: <20230718012804.-dJfu6bWjXfVm_J3Xo9coqNui_mDV8FPy-b58H6Y0BQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45045@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1854 bytes --]

New comment by TeusLollo on void-packages repository

https://github.com/void-linux/void-packages/issues/45045#issuecomment-1639136801

Comment:
> 
> Apologies if I misunderstood, but when you mention "registration," are you referring to the creation of an account? Because as far as I know, I didn't have one.
> 

No. 
In web contexts, an "user agent" is usually a client-embedded UTF-based string, that provides servers with variable information which may be useful. 
For example, a common web browser has an user agent (Ever wondered how some websites know exactly which browser and which version thereof you're using? That's the user agent providing infos), but many other application-layer programs also have those "user agents". 

In this case, it seems to me that VLSub uses an unique "user agent" which is registered upon first usage, and then cached, and which is utilized to have opensubtitles.com provide its services (In this case, downloading subtitles. I guess they set it up like this to prevent abuse). 

Since they have recently stopped registering new user agents, that may be why recently-deployed VLSub plugins don't work anymore, but older ones do (Because those could register themselves before such registering services were terminated).

Or at least I guess that's what's happening.

In every case it won't matter in the long run, because VLSub will need to be rewritten to accommodate what those at opensubtitles.com are doing. 

Basically thus, unless VLC developers rewrite VLSub by the end of the year, VLSub will completely stop functioning by 2023-12-31 as by:

https://code.videolan.org/videolan/vlc/-/issues/27168#note_337034
_OpenSubtitles.org API important dates:
2022-06-15 registration of new user agents is stopped
2023-12-31 end of life, API endpoint will be turned off_

EDIT: Spelling




  parent reply	other threads:[~2023-07-18  1:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-14 21:42 [ISSUE] " gorecki3
2023-07-15  3:18 ` gorecki3
2023-07-15 14:08 ` TeusLollo
2023-07-16 16:09 ` gorecki3
2023-07-16 16:10 ` gorecki3
2023-07-17 20:41 ` TeusLollo
2023-07-18  0:06 ` gorecki3
2023-07-18  1:26 ` TeusLollo
2023-07-18  1:28 ` TeusLollo [this message]
2023-07-18 12:40 ` gorecki3
2023-07-18 12:42 ` gorecki3
2023-07-18 12:47 ` gorecki3
2023-07-18 12:47 ` gorecki3
2023-07-18 13:10 ` TeusLollo
2023-07-18 13:10 ` TeusLollo
2023-07-18 21:37 ` gorecki3
2023-07-18 22:06 ` gorecki3
2023-07-18 23:30 ` TeusLollo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230718012804.-dJfu6bWjXfVm_J3Xo9coqNui_mDV8FPy-b58H6Y0BQ@z \
    --to=teuslollo@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).