Recherche avancée

Sur d’autres sites (8579)

• Trolls in trouble

  6 juin 2013, par Mans — Law and liberty

  Life as a patent troll is hopefully set to get more difficult. In a memo describing patent trolls as a “drain on the American economy,” the White House this week outlined a number of steps it is taking to stem this evil tide. Chiming in, the Chief Judge of the Court of Appeals for the Federal Circuit (where patent cases are heard) in a New York Times op-ed laments the toll patent trolling is taking on the industry, and urges judges to use powers already at their disposal to make the practice less attractive. However, while certainly a step in the right direction, these measures all fail to address the more fundamental properties of the patent system allowing trolls to exist in the first place.

  System and method for patent trolling

  Most patent trolling operations comprise the same basic elements :

  1. One or more patents with broad claims.
  2. The patents of (1) acquired by an otherwise non-practising entity (troll).
  3. The entity of (2) filing numerous lawsuits alleging infringement of the patents of (1).
  4. The lawsuits of (3) targeting end users or retailers.
  5. The lawsuits of (3) listing as plaintiffs difficult to trace shell companies.

  The recent legislative actions all take aim at the latter entries in this list. In so doing, they will no doubt cripple the trolls, but the trolls will remain alive, ready to resume their wicked ways once a new loophole is found in the system.

  To kill a patent troll

  As Judge Rader and his co-authors point out in the New York Times, “the problem stems largely from the fact that, [...] trolls have an important strategic advantage over their adversaries : they don’t make anything.” This is the heart of the troll, and this is where the blow should be struck. Our weapon shall be the mightiest judicial sword of all, the Constitution.

  The United States Constitution contains (in Article I, Section 8) the foundation for the patent system (emphasis mine) :

  The Congress shall have Power [...] To promote the Progress of Science and useful Arts, by securing for limited Times to Authors and Inventors the exclusive Right to their respective Writings and Discoveries.

  Patent trolls are typically not inventors. They are merely hoarders of other people’s discarded inventions, and that allowing others to reap the benefits of an inventor’s work would somehow promote progress should be a tough argument. Indeed, it is the dissociation between investment and reward which has allowed the patent trolls to rise and prosper.

  In light of the above, the solution to the troll menace is actually strikingly simple : make patents non-transferable.

  Having the inventor retain the rights to his or her inventions (works for hire still being recognised), would render the establishment of non-practising entities, which most trolls are, virtually impossible. The original purpose of patents, to protect the investment of inventors, would remain unaffected, if not strengthened, by such a change.

  Links

  • Taking on Patent Trolls to Protect American Innovation
  • Fact Sheet : White House Task Force on High-Tech Patent Issues
  • Make Patent Trolls Pay in Court
  • Constitution of the United States

• Firebase function to convert YouTube to mp3

  9 octobre 2023, par satchel

  I want to deploy to Firebase cloud functions.

  


  However, I get a vague error : “Cannot analyze code” after it goes through the initial pre deploy checks successfully.

  


  But I cannot figure out the problem given the vagueness of the error.

  


  It looks right with these requirements :

  


  

  • receive a POST with JSON body of YouTube videoID as a string

  


  • Download locally using the YouTube download package

  


  • Pipe to the ffmpeg package and save mp3 to the local temp

  


  • Store in default bucket on firestore storage

  


  • Apply make public method to make public

  


  


  const functions = require('firebase-functions');
const admin = require('firebase-admin');
const ytdl = require('ytdl-core');
const ffmpeg = require('fluent-ffmpeg');
const fs = require('fs');
const path = require('path');
const os = require('os');

admin.initializeApp();

// Set the path to the FFmpeg binary
const ffmpegPath = path.join(__dirname, 'bin', 'ffmpeg');
ffmpeg.setFfmpegPath(ffmpegPath);

exports.audioUrl = functions.https.onRequest(async (req, res) => {
    if (req.method !== 'POST') {
        res.status(405).send('Method Not Allowed');
        return;
    }

    const videoId = req.body.videoID;
    const videoUrl = `https://www.youtube.com/watch?v=${videoId}`;
    const audioPath = path.join(os.tmpdir(), `${videoId}.mp3`);

    try {
        await new Promise((resolve, reject) => {
            ytdl(videoUrl, { filter: format => format.container === 'mp4' })
                .pipe(ffmpeg())
                .audioCodec('libmp3lame')
                .save(audioPath)
                .on('end', resolve)
                .on('error', reject);
        });

        const bucket = admin.storage().bucket();
        const file = bucket.file(`${videoId}.mp3`);
        await bucket.upload(audioPath, {
            destination: file.name,
            metadata: {
                contentType: 'audio/mp3',
            },
        });

        // Make the file publicly accessible
        await file.makePublic();

        const publicUrl = file.publicUrl();
        res.status(200).send({ url: publicUrl });
    } catch (error) {
        console.error('Error processing video:', error);
        res.status(500).send('Internal Server Error');
    }
});


  


  The following is the package.json file which is used to reference the dependencies for the function, as well as the entry point, which I believe just needs to be the name of the filename with the code :

  


  {
  "name": "firebase-functions",
  "description": "Firebase Cloud Functions",
  "main": "audioUrl.js", 
  "dependencies": {
    "firebase-admin": "^10.0.0",
    "firebase-functions": "^4.0.0",
    "ytdl-core": "^4.9.1",
    "fluent-ffmpeg": "^2.1.2"
  },
  "engines": {
    "node": "18"
  },
  "private": true
}


  


  (Edit) Here is the error :

  


   deploying functions
✔  functions: Finished running predeploy script.
i  functions: preparing codebase default for deployment
i  functions: ensuring required API cloudfunctions.googleapis.com is enabled...
i  functions: ensuring required API cloudbuild.googleapis.com is enabled...
i  artifactregistry: ensuring required API artifactregistry.googleapis.com is enabled...
✔  functions: required API cloudbuild.googleapis.com is enabled
✔  artifactregistry: required API artifactregistry.googleapis.com is enabled
✔  functions: required API cloudfunctions.googleapis.com is enabled
i  functions: Loading and analyzing source code for codebase default to determine what to deploy
Serving at port 8171

shutdown requested via /__/quitquitquit


Error: Functions codebase could not be analyzed successfully. It may have a syntax or runtime error


  


  Failed to load function definition from source: FirebaseError: Functions codebase could not be analyzed successfully. It may have a syntax or runtime error


  


  I get the same error when running the following :

  


  firebase deploy --only functions:audioUrl


  


  And I thought I might get more detailed errors using the emulator :

  


  firebase emulators:start


  


  Under the emulator I had this additional error initially :

  


  Your requested "node" version "18" doesn't match your global version "16". Using node@16 from host.


  


• avformat/hlsenc : Fix leak of child AVFormatContext

  16 décembre 2019, par Andreas Rheinhardt

  avformat/hlsenc : Fix leak of child AVFormatContext
  Before ed897633, the hls muxer would free its child AVFormatContexts
  
  and reset the pointer to these contexts to NULL immediately afterwards ;
  
  ed897633 moved the former to later (into a separate function), but kept
  
  the resetting, ensuring that the child context leaks.
  Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>
  
  Reviewed-by : Steven Liu <lq@onvideo.cn>
  

  • [DH] libavformat/hlsenc.c