Recherche avancée

Sur d’autres sites (4234)

• About Soundcloud scraping for uploading music to telegram group

  16 juin 2021, par so sa

  I am trying to automatically download the new uploaded file from the below soundcloud link and upload it to a telegram group :

  


  https://soundcloud.com/radio-hamrah-1

  


  so I have googled the :

  


  


  python script to download from soundcloud and import to telegram
group

  


  


  and tried the scdl python module by its instruction, but when I have tried its on this colab page I get this error :

  


  !pip3 install git+https://github.com/flyingrub/scdl
!scdl -l https://soundcloud.com/pandadub/sets/the-lost-ship --download-archive archive.txt -c

Collecting git+https://github.com/flyingrub/scdl
  Cloning https://github.com/flyingrub/scdl to /tmp/pip-req-build-0g64ql2f
  Running command git clone -q https://github.com/flyingrub/scdl /tmp/pip-req-build-0g64ql2f
Requirement already satisfied (use --upgrade to upgrade): scdl==1.6.12 from git+https://github.com/flyingrub/scdl in /usr/local/lib/python3.7/dist-packages
Requirement already satisfied: docopt in /usr/local/lib/python3.7/dist-packages (from scdl==1.6.12) (0.6.2)
Requirement already satisfied: mutagen in /usr/local/lib/python3.7/dist-packages (from scdl==1.6.12) (1.45.1)
Requirement already satisfied: termcolor in /usr/local/lib/python3.7/dist-packages (from scdl==1.6.12) (1.1.0)
Requirement already satisfied: requests in /usr/local/lib/python3.7/dist-packages (from scdl==1.6.12) (2.23.0)
Requirement already satisfied: clint in /usr/local/lib/python3.7/dist-packages (from scdl==1.6.12) (0.5.1)
Requirement already satisfied: chardet<4,>=3.0.2 in /usr/local/lib/python3.7/dist-packages (from requests->scdl==1.6.12) (3.0.4)
Requirement already satisfied: urllib3!=1.25.0,!=1.25.1,<1.26,>=1.21.1 in /usr/local/lib/python3.7/dist-packages (from requests->scdl==1.6.12) (1.24.3)
Requirement already satisfied: idna<3,>=2.5 in /usr/local/lib/python3.7/dist-packages (from requests->scdl==1.6.12) (2.10)
Requirement already satisfied: certifi>=2017.4.17 in /usr/local/lib/python3.7/dist-packages (from requests->scdl==1.6.12) (2021.5.30)
Requirement already satisfied: args in /usr/local/lib/python3.7/dist-packages (from clint->scdl==1.6.12) (0.1.0)
Building wheels for collected packages: scdl
  Building wheel for scdl (setup.py) ... done
  Created wheel for scdl: filename=scdl-1.6.12-cp37-none-any.whl size=19143 sha256=27ca560a7f3947830289d0df167db84137d1554fe1ab740c2afab3db0abedd74
  Stored in directory: /tmp/pip-ephem-wheel-cache-agspvyq5/wheels/49/44/6e/a5f6f709e7b231f3639ea9f9fc48a4699b958850715556e7f6
Successfully built scdl
Soundcloud Downloader
Failed to get item...


  


  

  


  and when I try by the Docker VPS by this commands :

  


  pip3 install git+https://github.com/flyingrub/scdl
pip3 install ffmpeg
scdl -l https://soundcloud.com/pandadub/sets/the-lost-ship --download-archive archive.txt -c


  


  pip3 install git+https://github.com/flyingrub/scdl pip3 install ffmpeg
scdl -l https://soundcloud.com/pandadub/sets/the-lost-ship —download-archive archive.txt -c

  


  I get this error :

  


  FileNotFoundError: [Errno 2] No such file or directory: 'ffmpeg'


  


  

  


  So I asked abut how could i do it by scdl and soundcloude python module.

  


  Update :

  


  Based of my two comment on this question I get different result by using the scdl python module via the above colab page, sometimes it is working and sometimes not, which i guess it is because of soudncloud server setting for preventing huge scraping and needs some delay during the music scraping form the soundcloud.

  


  Thanks.

  


• How to measure the performance of a newsletter (or any email) with Piwik

  19 décembre 2017, par InnoCraft — Community

  To be able to grow your business, it is crucial to track all your marketing efforts. This includes all newsletters and emails that you share with people outside of your business. Otherwise, you won’t be able to know which of your daily efforts are yielding results.

  Are you wondering if it is possible to track the performance of an emailing campaign in Piwik efficiently ? Would you like to know if it is technically easy ? No worries, here is a “How to” tutorial showing you how easily you can track an emailing in Piwik properly.

  Different tracking levels for different needs

  There are many things that you may be interested to track, for example :

  

  1. How many users opened your email
  2. How many users interacted with the links in your email
  3. How many users interacted on your website through your email

  Let’s have a look at each of these levels.

  Step 1 – Tracking email and newsletter openings in Piwik

  Tracking email openings requires to add an HTML code to your newsletter. It works through what we call a tracking pixel, a tiny image of 1×1 that is transparent so the user will not be able to see it.
  In order to install it, here is an example of what this code looks like :

  <img src="https://piwik.example.com/piwik.php?idsite=YOUR_PIWIK_WEBSITE_ID&rec=1&bots=1&url=https%3A%2F%2Fexample.com%2Femail-opened%2Fnewsletter_XYZ&action_name=Email%20opened&_rcn=internal%20email%20name&_rck=newsletter_XYZ" style="border:0;” alt="" />

  The Piwik tracking pixel explained

  The above URL is composed of the following URL parameters which are part of our Tracking API :

  • idsite : Corresponds to the ID of the website you would like to track.
  • rec : You need to have rec=1 in order for the request to be actually recorded.
  • bots : Set it to 1 to include all the connections made to this request, bots included.
  • url : corresponds to the URL you would like to display in Piwik every time the email is opened.
  • action_name : This is the page name you would like to be tracked when the email is opened.
  • _rcn : The name you would like to give to your campaign.
  • _rck : The keyword you may like to use in order to summarize the content of your newsletter.

  You may have noticed some special characters here such as “%20”, “%2F”. That’s because the URL is encoded. We strongly recommend you to do so in order for your tracking not to break. Many tools are available on the web in order to encode your URLs such as https://www.urlencoder.org/.

  If you would like to access the previous tracking code easily, keep in mind that you can always find the tracking code generator within the “Piwik admin panel → Tracking code” :

  

  You can find more information about it on our guide at : How do I track how many users open and read my newsletter emails (using a pixel / beacon) ?

  As a result, the information will be pushed as following for any user who opens your email :

  

  To not bias your regular page views on your website with newsletter openings, we recommend tracking newsletter openings into a new website.

  Tracking even more data : the user ID example

  You can go deeper in your URL tracking by inserting other parameters such as the user id if you have this information within your emailing database. One of the main benefit of tracking the User ID is to connect data across multiple devices and browsers for a given user.

  You only need to add the following parameter &uid=XXX where XXX equals the dynamic value of the user ID :

  

  Make sure that UID from your emailing provider is the same as the one used on your website in order for your data to be consistent.

  Important note : some email providers are loading email messages by default which results in an opening even if the user did not actually open the email.

  Step 2 – Measure the clicks within your emailing

  Tracking clicks within an email lets you know with which content readers interacted the most. We recommend tracking all links in all your emails as a campaign, whether it is a newsletter, a custom support email, an email invoice, etc. You might be surprised to see which of your emails lead to conversions and if they don’t, try to tweak those emails, so they might in the future.

  Tracking clicks This works thanks to URL campaign tracking. In order to perform this action, you will need to add Piwik URL parameters to all your existing link URLs :

  • Website URL : for example “www.your-website.com”.
  • Campaign name : for example “pk_campaign=emailing”. Represents the name you would like to give to your campaign.
  • Campaign keyword : for example “pk_keyword=name-of-your-article”. Represents the name you would like to give to your content.
  • Campaign source : for example “pk_source=newsletter”. Represents the name of the referrer.
  • Campaign medium : for example “pk_medium=email”. Represents the type of referrer you are using.
  • Campaign content : for example “pk_content=title”. Represents the type of content.

  You can find more information about campaign url tracking in our “Tracking marketing campaigns with Piwik” guide.

  Here is a sample showing you how you can differentiate some links in a newsletter, all pointing to the same URL :

  

  Once you have added these URL parameters to each of your link, Piwik will clearly indicate the referrer of this specific campaign when a user clicks on a link in the newsletter and visits your website.

  Important note : if you do not track your campaigns, it will result in a bad interpretation of your data within Piwik as you will get webmail services or direct entries as referrer instead of your newsletter campaign.

  Step 3 – Measure emailing performances on your website

  Thanks to Piwik URL campaign parameters, you can now clearly identify the traffic brought through your emailing. You can now specifically isolate users who come from emails by creating a segment :

  

  Once done, you can either have a look at each user specifically through the visitor log report or analyze it as a whole within the rest of the reports.

  You can even measure your return on investment directly if goals have been defined. In order to know more about how to track goals within Piwik.

  Did you like this article ?

  If you enjoyed reading this article, do not hesitate to share it around you. Moreover, if there are any topics you would like to write us about in particular, just drop us an email and we will be more than happy to write about it.

• Anomalie #4230 : Limite à la longueur des paramètres d’un modèle

  10 février 2021, par b b

  Si tout le monde est d’accord et que SPIP 3.3 est compatible PHP 7.3, on peut fermer non ? Sinon on attend la version de SPIP qui nécessitera PHP 7.3 mini et zou :p

  PS : j’ai bien ri avec le coup de guerre & paix en argument, merci :D