Recherche avancée

Médias (91)

Autres articles (69)

  • Websites made ​​with MediaSPIP

    2 mai 2011, par

    This page lists some websites based on MediaSPIP.

  • Creating farms of unique websites

    13 avril 2011, par

    MediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
    This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...)

  • Ecrire une actualité

    21 juin 2013, par

    Présentez les changements dans votre MédiaSPIP ou les actualités de vos projets sur votre MédiaSPIP grâce à la rubrique actualités.
    Dans le thème par défaut spipeo de MédiaSPIP, les actualités sont affichées en bas de la page principale sous les éditoriaux.
    Vous pouvez personnaliser le formulaire de création d’une actualité.
    Formulaire de création d’une actualité Dans le cas d’un document de type actualité, les champs proposés par défaut sont : Date de publication ( personnaliser la date de publication ) (...)

Sur d’autres sites (7119)

  • Secure and track every change to your Matomo installation with the Activity Log plugin

    14 novembre 2017, par InnoCraft — Plugins

    Are you wondering how your colleagues are using Matomo (Piwik) ? Would you like to know if an unauthorized user got an access to your installation ? Would you like to remember the last actions you performed in Matomo some weeks ago ? At InnoCraft, we developed a plugin called “Activity Log”. With this feature you can easily track and check all major changes to your Matomo websites, for example : user permissions, goals, and funnels. In this article we will show you the different ways you can use it and explain why it is an invaluable plugin.

    Activity log for better security

    The activity log feature has been designed for security. Also referred to as “audit logging” or “audit trail”, with this plugin you will be able to :

    1. detect any suspicious actions
    2. detect hacker attacks
    3. help identify performance problems
    4. see clearly who did what, and when
    5. find out how people are using Matomo (Piwik) within your company

    1 – detect any suspicious actions

    With audit trail you can easily identify if a former employee still has access to your Matomo (Piwik) installation. You will then be able to know when he accessed it for the last time, and what changes she or he performed. If you got hacked, you will be able to find out if the user created, changed, or deleted any website, goals, or did anything else suspicious.

    2 – detect hacker attacks

    When an unregistered user is trying to access your Matomo (Piwik), each failed login attempt is registered within the Activity Log report.

    3 – help identify performance problems

    Activity Log can help you identify performance problems by registering the sequence of each major action a user performed. For example, if a user updated or installed a third party plugin, and suddenly Matomo (Piwik) is getting performance problems, then it is likely that the plugin update caused it.

    4 – see clearly who did what, and when

    It is always challenging in an organization to know who did what and when. With Activity Log, you will know who were the employee(s) that accessed Matomo (Piwik), created, updated, or deleted a goal, a funnel, a scheduled report, and much more.

    5- find out how people are using Matomo within your company

    By having a look at how people are using Matomo (Piwik) you will have an overview of how your colleagues use Matomo. For example, you can see who is creating Custom segments to analyse the audience in more details, who is creating funnels to learn where your users drop off. You will then be able to identify who has the knowledge and who needs training.

    Did you know ?

    You can help the Matomo (Piwik) core team make Matomo even better by sharing anonymously how you use Matomo on a day to day basis. You just need to install the following plugin : http://plugins.matomo.org/AnonymousPiwikUsageMeasurement

    What’s in it ?

    Once downloaded and installed from the marketplace, you will be able to access the activity log from the admin panel within the diagnostic section :

    Activity log admin panel

    If you are logged as a super user administrator, you will get an overview and a detailed report about who accessed Matomo (Piwik) and which actions they performed.

    Those reports are critical as they allow the super user to :

    • ensure users are following all documented procedures within your organization such as naming conventions for reports, using the right settings when adding measurables…
    • identify suspicious behavior. As those reports are gathering all major Matomo (Piwik) users activities it is easy to identify non conventional behavior.
    • replay the sequence some users went through in order to fix any potential issues.

    Activity log view report you can access through the admin panel

    So you will see in a second if an unusual user got access to Matomo (Piwik) and the different actions the user performed.
    It is also a good way to see the features that your users are using and identify potential misuse.

    As a regular user or admin, activity log is providing only the historical actions that this user performed :

    Activity log report for non super user

    Actions listed in the log include any changes (add, edit, delete) to the following features (this is a non exhaustive list) :

    • Annotation
    • Custom Alert
    • Custom Dimension
    • Goal
    • Privacy settings
    • Scheduled report
    • Segment
    • User
    • Website

    This is a ideal to remember the actions they previously performed some weeks/months ago.

    Where can I start from here ?

    Activity log is a premium feature you can acquire through the Matomo (Piwik) marketplace. If you want to experience it before purchasing it, you can try it for free on our cloud infrastructure.

    Activity log is just one out of the many great premium features developed by InnoCraft, the company founded by the creators of Matomo. Discover all their special plugins through the premium marketplace.

     

  • Secure and track every change to your Piwik installation with the Activity Log plugin

    14 novembre 2017, par InnoCraft — Plugins

    Are you wondering how your colleagues are using Piwik ? Would you like to know if an unauthorized user got an access to your installation ? Would you like to remember the last actions you performed in Piwik some weeks ago ? At InnoCraft, we developed a plugin called “Activity Log”. With this feature you can easily track and check all major changes to your Piwik websites, for example : user permissions, goals, and funnels. In this article we will show you the different ways you can use it and explain why it is an invaluable plugin.

    Activity log for better security

    The activity log feature has been designed for security. Also referred to as “audit logging” or “audit trail”, with this plugin you will be able to :

    1. detect any suspicious actions
    2. detect hacker attacks
    3. help identify performance problems
    4. see clearly who did what, and when
    5. find out how people are using Piwik within your company

    1 – detect any suspicious actions

    With audit trail you can easily identify if a former employee still has access to your Piwik installation. You will then be able to know when he accessed it for the last time, and what changes she or he performed. If you got hacked, you will be able to find out if the user created, changed, or deleted any website, goals, or did anything else suspicious.

    2 – detect hacker attacks

    When an unregistered user is trying to access your Piwik, each failed login attempt is registered within the Activity Log report.

    3 – help identify performance problems

    Activity Log can help you identify performance problems by registering the sequence of each major action a user performed. For example, if a user updated or installed a third party plugin, and suddenly Piwik is getting performance problems, then it is likely that the plugin update caused it.

    4 – see clearly who did what, and when

    It is always challenging in an organization to know who did what and when. With Activity Log, you will know who were the employee(s) that accessed Piwik, created, updated, or deleted a goal, a funnel, a scheduled report, and much more.

    5- find out how people are using Piwik within your company

    By having a look at how people are using Piwik you will have an overview of how your colleagues use Piwik. For example, you can see who is creating Custom segments to analyse the audience in more details, who is creating funnels to learn where your users drop off. You will then be able to identify who has the knowledge and who needs training.

    Did you know ?

    You can help the Piwik core team make Piwik even better by sharing anonymously how you use Piwik on a day to day basis. You just need to install the following plugin : http://plugins.piwik.org/AnonymousPiwikUsageMeasurement

    What’s in it ?

    Once downloaded and installed from the marketplace, you will be able to access the activity log from the admin panel within the diagnostic section :

    Activity log admin panel

    If you are logged as a super user administrator, you will get an overview and a detailed report about who accessed Piwik and which actions they performed.

    Those reports are critical as they allow the super user to :

    • ensure users are following all documented procedures within your organization such as naming conventions for reports, using the right settings when adding measurables…
    • identify suspicious behavior. As those reports are gathering all major Piwik users activities it is easy to identify non conventional behavior.
    • replay the sequence some users went through in order to fix any potential issues.

    Activity log view report you can access through the admin panel

    So you will see in a second if an unusual user got access to Piwik and the different actions the user performed.
    It is also a good way to see the features that your users are using and identify potential misuse.

    As a regular user or admin, activity log is providing only the historical actions that this user performed :

    Activity log report for non super user

    Actions listed in the log include any changes (add, edit, delete) to the following features (this is a non exhaustive list) :

    • Annotation
    • Custom Alert
    • Custom Dimension
    • Goal
    • Privacy settings
    • Scheduled report
    • Segment
    • User
    • Website

    This is a ideal to remember the actions they previously performed some weeks/months ago.

    Where can I start from here ?

    Activity log is a premium feature you can acquire through the Piwik marketplace. If you want to experience it before purchasing it, you can try it for free on our cloud infrastructure.

    Activity log is just one out of the many great premium features developed by InnoCraft, the company founded by the creators of Piwik. Discover all their special plugins through the premium marketplace.

     

  • Discord bot transmitting audio not working

    24 avril 2024, par R5B3NBB

    this discord bot is supposed to join the users voice channel and play music, everything works except for it not transmitting audio. from what I can gather the error is happening somewhere between it playing the audio file and it being transmitted. any helps appreciated and I'm sure it's not on the discord bot side since I gave it admin permissions and it still didn't work.
should also be mentioned that im not a veteran when it comes to JavaScript so if the error s obvious sorry.

    


    const { Client, GatewayIntentBits, SlashCommandBuilder, MessageEmbed } = require("discord.js");
const { joinVoiceChannel, createAudioPlayer, NoSubscriberBehavior, createAudioResource } = require('@discordjs/voice');
const { token } = require("./config.json");
const fs = require('fs');

const client = new Client({ intents: [GatewayIntentBits.Guilds, GatewayIntentBits.GuildMessages, GatewayIntentBits.GuildMessageReactions] });

client.once("ready", () => {
    console.log("Bot active.");

    const ping = new SlashCommandBuilder()
        .setName('ping')
        .setDescription('Replies with pong!');

    const hello = new SlashCommandBuilder()
        .setName('hello')
        .setDescription('Says hello!')
        .addUserOption(option =>
            option
                .setName('user')
                .setDescription('The user to say hi to')
                .setRequired(false)
        );

    const echo = new SlashCommandBuilder()
        .setName('echo')
        .setDescription("Echo's a message")
        .addStringOption(option =>
            option
                .setName('text')
                .setDescription('The text to repeat')
                .setRequired(true)
        );

    const mata = new SlashCommandBuilder()
        .setName('mata')
        .setDescription('Green, ma-ta is here!');

    const eddy = new SlashCommandBuilder()
        .setName('eddy')
        .setDescription('Original reggae music!')
        .addStringOption(option =>
            option
                .setName('local_audio')
                .setDescription('Provide the name of the local audio file')
                .setRequired(true)
        );

    const disconnect = new SlashCommandBuilder()
        .setName('disconnect')
        .setDescription('Disconnects the bot from the voice channel');

    const commands = [ping, hello, echo, mata, eddy, disconnect];

    commands.forEach(command => client.guilds.cache.forEach(guild => guild.commands.create(command)));


});

client.on('interactionCreate', async interaction => {
    console.log("Interaction received.");
    
    if (!interaction.isCommand()) {
        console.log("Not a command interaction.");
        return;
    }

    const { commandName, options, member, guild } = interaction;
    console.log("Command name:", commandName);

    if (commandName === 'ping') {
        console.log("Ping command executed.");
        await interaction.reply("Pong!");
    } else if (commandName === 'hello') {
        console.log("Hello command executed.");
        let user = options.getUser('user') || member.user;
        await interaction.reply(`Hello ${user.username}!`);
    } else if (commandName === 'echo') {
        console.log("Echo command executed.");
        const text = options.getString('text');
        await interaction.reply(text);
    } else if (commandName === 'mata') {
        console.log("Mata command executed.");
        const embed = new MessageEmbed()
            .setColor('#00FF00')
            .setTitle('This is mata!')
            .setDescription('She is very ugly!')
            .setImage('https://scottbarrykaufman.com/wp-content/uploads/2011/08/pig-ugly-woman-fat-face.jpg');

        await interaction.reply({ embeds: [embed] });
    } else if (commandName === 'eddy') {
        console.log("Eddy command executed.");

        const voiceChannel = member.voice.channel;
        if (!voiceChannel) {
            await interaction.reply("You need to be in a voice channel to use this command.");
            return;
        }

        const connection = joinVoiceChannel({
            channelId: voiceChannel.id,
            guildId: guild.id,
            adapterCreator: guild.voiceAdapterCreator,
        });

        connection.on('stateChange', (state) => {
            console.log(`Connection state changed to ${state.status}`);
        });

        connection.on('error', (error) => {
            console.error('Connection error:', error);
        });

        const localAudioFile = options.getString('local_audio');
        const filePath = `./audio/Gorillaz.mp3`;

        console.log("File path:", filePath);

        if (!fs.existsSync(filePath)) {
            console.log("File does not exist.");
            await interaction.reply("The specified local audio file does not exist.");
            return;
        }

        const audioPlayer = createAudioPlayer({
            behaviors: {
                noSubscriber: NoSubscriberBehavior.Pause,
            },
        });

        const stream = fs.createReadStream(filePath);
        const resource = createAudioResource(stream);
        audioPlayer.play(resource);

        connection.subscribe(audioPlayer);

        console.log("Audio playback started.");
        await interaction.reply("Now playing audio in your voice channel!");
    } else if (commandName === 'disconnect') {
        console.log("Disconnect command executed.");
        const voiceChannel = member.voice.channel;

        if (!voiceChannel) {
            await interaction.reply("The bot is not in a voice channel.");
            return;
        }

        const connection = joinVoiceChannel({
            channelId: voiceChannel.id,
            guildId: guild.id,
            adapterCreator: guild.voiceAdapterCreator,
        });

        connection.on('stateChange', (state) => {
            console.log(`Connection state changed to ${state.status}`);
        });

        connection.on('error', (error) => {
            console.error('Connection error:', error);
        });

        if (connection) {
            connection.destroy();
            console.log("Disconnected from the voice channel.");
        }
    }
});

client.login(token);