L’Education nationale sous le chochttps://www.liberation.fr/debats/2020/08/26/l-education-nationale-sous-le-choc_1797689

Pew Research Center : https://www.journalism.org/2020/07/30/americans-who-mainly-get-their-news-on-social-media-are-less-engaged-less-knowledgeable

https://www.thisworddoesnotexist.com/

#IA #langage

https://dia.so/4sz

Le gouvernement renonce une fois de plus à sa souveraineté et stocke nos données sur des serveurs accessibles par un gouvernement tiers et à disposition des GAFAM...

#signez #healthdatahub #data

Pourtant quand on est enfermé chez soi et que la médiathèque est fermée, quelques livres ça aurait pu être pas mal... Vous pourrez toujours lié des classiques libres de droit sur vous écrans :-/

J’en ai marre des mecs, mais marre, marre, marre…

Here are release highlights:

• Tools are now grouped in the toolbox by default
• Sliders now use a compact style with improved user interaction
• Vastly improved user experience for the transformation preview
• Dockable areas now highlighted when a dockable dialog is being dragged
• New 3D Transform tool to rotate and pan items
• Much smoother brush outline preview motion on the canvas
• Symmetry painting enhancements
• Faster loading of ABR brushes
• PSD support improvements
• Consolidated user interface for merging down and anchoring layers
• Update check to notify users of new releases available
• 28 bug fixes, 15 translation updates

Tools now grouped by default¶

Tools can now be grouped in the toolbox, and this option is enabled by default.

You can customize groups by creating new ones and dragging tools between them. The changes will take effect immediately. Or you can disable the grouping entirely. You’ll find configuration options on the Interface/Toolbox page of the Preferences dialog.

Please note that the default order of tools in the toolbox is now different. You can customize it as well.

Compact sliders¶

Sliders typically used in GEGL-based filters and tools’ options now have a compact style by default: they take a lot less space vertically and have a vastly improved interaction model.

You can use multiple modifiers with either left-click or mouse wheel scrolling:

• Left-click + drag changes a value with a default increment
• Shift + left-click + drag (or right-click + drag) changes a value with a smaller step
• Ctrl + left-click + drag change a value with a larger step

Here is the full reference:

Docking UX improvements¶

The ‘You can drop dockable dialogs here’ message is now gone from the toolbox, and other empty dockable areas. This used to annoy quite a few users who used a single/double-column layout for the left panel.

But since we still need to hint where you can dock dialogs, whenever you drag a dialog, all dockable areas will be highlighted.

High-contrast symbolic theme now available¶

Since releasing 2.10 in 2018, we received a lot of feedback that the symbolic icon theme used by default doesn’t have enough contrast. We recently did a quick poll on Twitter showing people a variation of the theme with more foreground/background color contrast, and that certainly clicked with users.

Some of the feedback suggested, however, that a part of the demographic likes the current contrast. So instead of pushing changes for everyone, we introduced a new high-contrast symbolic theme. You can choose it in the Preferences dialog, just like any other icon theme.

The contrast is a compile-time variable that you can change prior to building GIMP from source code. We see this as more of a dirty temporary solution.

With GTK3, it’s going to be a lot easier to make things configurable. In particular, upcoming Inkscape 1.0 is featuring a new icon theme called ‘multicolor’ that makes a great use of CSS in GTK3 and, while staying symbolic, uses some color where it matters. We will be definitely looking closer at that approach.

To complement the new high-contrast variation of the symbolic theme, GIMP now also draws a double black/white border around FG/BG indicator in the toolbox to make that border more legible, especially in dark themes.

Transformation preview improvements¶

A new option called Composited Preview is now available for most transformation tools. It enables the rendering of the transform preview with the right position of the modified layer in the layers stack, as well as with the correct blending mode.

It comes with two sub-options.

Preview linked items enables previewing changes to all linked items like layers rather than just the currently selected item.

Synchronous preview render the preview as you move the mouse/stylus pointer to change the transform instead of waiting for the movement to stop. This provides instant feedback when GIMP can update the display fast enough, which is usually not the case with large layers.

GIMP now also automatically previews the clipping of transformed layers. This allows reducing the amount of trial and error when e.g. rotating.

New 3D Transform tool¶

A new transform tool helps changing the perspective of a layer or panning it in 3D space. You can set a vanishing point, then rotate the layer in X, Y, and Z axes.

Multiple modifiers are available to constrain rotation and panning to just one axis. The Unified interaction checkbox allows shifting the vanishing, as well as panning and rotating without switching between tabs on the on-canvas settings dialog. Finally, the Local frame option allows controlling the transformation in the layer’s local frame of reference, instead of the global one.

Brush outline and quality improvements¶

The brush outline motion now feels smoother thanks to raising the refresh rate from 20 FPS to a maximum of 120 FPS, as well as disabling the snapping to dabs (new option, off by default). The former became a sensible idea thanks to painting parallelization introduced by Ell several releases ago. The snapping to brush dabs can be re-enabled on the Image Windows page of the Preferences dialog.

Additionally, the paint rate of the Airbrush tool was increased from 15 to a maximum of 60 stamps per second, making paint buildup smoother. Note that, as a result, the relation between the tool’s Rate parameter and the actual paint buildup rate is now different, which may affect existing tool presets.

It’s also worth mentioning that the Warp Transform tool now respects mouse pointer settings defined on the Image Windows page of the Preferences dialog.

Furthermore, in order to improve the quality of downscaled brushes, paint tools now use mipmaps for downscaling bitmap brushes. Instead of resampling downscaled brushes directly from their original size, GIMP now creates a box-filtered mipmap hierarchy for the original brush on demand, and uses the closest mipmap level as the resampling source for downscaled brushes. This significantly reduces aliasing in downscaled brushes, producing smoother results.

Symmetry painting enhancements¶

The Mandala symmetry painting mode now has a Kaleidoscope option, which combines both rotation and reflection.

When the Kaleidoscope option is enabled, subsequent strokes are mirrored across the symmetry slice edges.

Faster loading of ABR brushes¶

GIMP now spends a lot less time loading Photoshop’s brushes (ABR). So if you use a lot of those, the startup time will become pleasantly smaller, by order of a magnitude.

The technical explanation is that GIMP used to read the stream of ABR data byte by byte, and now it uses scanline reading instead.

PSD support improvements¶

PSD files now load faster mostly by eliminating excessive copies between the original file and the project representation inside GIMP. For large PSD files, the loading is now ~1.5 to ~2 times faster.

Moreover, GIMP is now capable of loading CMYK(A) PSD files (only 8-bit per channel for now). It does so by converting pixels to RGB(A) float using sRGB as the profile which, we know, is not good enough for serious work.

However, the plug-in is already using babl formats to specify and communicate CMYK pixel format encodings with GIMP. This is a good first step towards better CMYK support. It can be improved both on its own as well as integrate with the ongoing work enabling general color-space support for babl formats in the development branch.

Layers dock improvements¶

The Layers dialog finally consolidates the UI for merging layers and attaching floating selections.

The bottom toolbar will now display a button for anchoring a floating selection only when there is one. Otherwise, it will display a button for merging layers.

You can also use several modifiers:

• Shift will merge a layer group
• Ctrl will merge all visible layers
• Ctrl + Shift will merge all visible layers with last used values

Update check to notify users of new releases available¶

GIMP will now check every time on the start up if the version of GIMP you have is the latest one available. It will do so by pinging GIMP’s server for the version of the latest release, then comparing it to the one installed on your computer.

GIMP will also compare revisions of the installers so that users would be aware of updated installers available. This is typically useful when we update installers to provide fixes in 3rd party components that we use.

Finally, this feature is used when constructing a crash report. If you experience a crash while using an outdated version of the program, GIMP will now tell you so.

You can disable this feature on the System Resources page of the Preferences dialog, and manually use the Check for updates button in the About dialog.

It is also possible to build GIMP without this feature by passing the --disable-check-update argument to the configure script.

Continuous Integration¶

Work on our continuous integration goes forward. We now implemented automatic compilation of the main development branch both with the legacy autotools build system and the new meson one. We also produce an alternative build with the Clang compiler (additionally to the GNU compiler gcc).

Moreover, for cross-platform development, we now produce Windows builds, both for 32-bit and 64-bit, cross-compiled with the crossroad/Mingw-w64 tools.

All these automatic builds allow us to catch early on specific bugs which may affect only certain configurations or platforms.

We hope it could also attract new developers wishing to dabble in contributing. Looking at compilation warnings and trying to fix them may be a very good first step into GIMP code. It would be much less overwhelming than actually trying to dive into our huge code from scratch.

If you are interested, look into our CI pipelines and look at the last ones (preferably the master branch), then into one of the various compilation jobs. We will be waiting for your patches!

GEGL and babl changes¶

There have been several improvements in GEGL since the release that accompanied GIMP 2.10.14:

• Fixed potential data-corruption/crash in the tile-swap back-end on Windows (the fix has already been made available in an updated installer for 2.10.14), and improved tile-queuing speed.
• The GEGL core now avoids running more thread jobs than there are pixels to process.
• The teardown of buffer caches is now faster when bounding box shrinks.
• In-place processing now only happens if region of interest fits in input abyss.
• Edge handling was improved for gegl:distance-transform operation

The babl library got build fixes, improved host CPU detection, macOS-specific fixes, and Clang warning squelches.

Contributors¶

Code contributors to this release are: Alex Samorukov, Anders Jonsson, band-a-prend, Cyril Richard, Elad Shahar, Ell, Elle Stone, Félix Piédallu, Jehan Pagès, Jernej Simončič, lillolollo, Massimo Valentini, Michael Natterer, Nikc, Øyvind Kolås, Pascal Terjan, woob.

Translators: Alan Mortensen, Alexandre Prokoudine, Anders Jonsson, Asier Sarasua Garmendia, Balázs Meskó, Balázs Úr, Bruce Cowan, Daniel Korostil, Jordi Mas, Julien Hardelin, Marco Ciampa, Piotr Drąg, Rodrigo Lledó Milanca, Ryuta Fujii, Sabri Ünal, sicklylife, Sveinn í Felli, Tim Sabsch, Zander Brown.

As usual, we thank lillolollo, nmat, and Michael Schumacher for triaging bug reports, and Julien Hardelin for keeping the user manual up to date.

What’s next¶

Our main objective is still completing the GTK3 port and releasing GIMP 3.0. This will take a while.

One of the ideas we are also exploring is improving the default single-window layout and introducing named workspaces streamlined for common use cases such as general editing, web design, digital photography, painting etc.

If you customized your default GIMP layout, we encourage you to post a screenshot and tell us about your use cases for GIMP that affected this customization. You can do that either on Twitter or in the mailing list for users.

Once we have a representative amount of samples for each common use case, we will analyze the data and see if we can create default workspaces that you can further tweak to your liking.

For the time being, don’t forget you can donate to the project and personally fund several GIMP developers, as a way to give back, and to accelerate the development of GIMP.

Changes to the Census Could Make Small Towns Disappear

Illustration avec cet article du Monde Diplomatique

https://dia.so/4eh . Des faits sont rapportés sur le comportement des forces de l'ordre, certains étayés par des preuves. Le pouvoir démentira formellement, parlera de manipulation, d'images tronquées, sorties de leur contexte. Pour autant, les faits sont là : parmi les force de l'ordre aujourd'hui, certains se lachent totalement, assurés de leur impunité. Jusqu'au moment où le vent tournera et quelques lampistes paieront. Le tout au détriment de la relation citoyens / forces de l'ordre / justice. Dans quelque sens qu'on la prenne. Et à terme (dès maintenant aussi) tout le monde est perdant dans l'affaire...

Pour autant, il est absolument faux dire que tout le monde déteste la police comme cela apparait dans l'article. Sans doute grâce à l'efficacité des écrans de fumée et des dissimulations diverses. Les faits ne sont pas appropriés. Et sondage après sondage, les forces de l'ordre caracolent en tête des institution ayant la plus grande confiance des français : https://www.ifop.com/publication/le-regard-des-francais-sur-la-police/

Du coup, l'article tombe à l'eau. Mais pas poussé par la police. Il s'y jette tout seul...

#humanité #astrophysique

Les données de 4 milliards de comptes personnels sont stockées sur ce serveur (futura science)

Et elles ont fuité bien sûr. Le plus génial c'est que c'est comme ça. Vous ne pouvez rien y faire. Vous avez sans doute consenti un jour par un click rapide et agacé à des conditions illisibles... Rendez vous sur have I been pwned si vous voulez en savoir le cœur net.

Nucléaire : comment le gouvernement travaille en catimini à la construction de six nouveaux EPR

Le développement personnel, c'est l'idéologie rêvée du néolibéralisme

#société #politique

Thé Economist (en)

Fixing the ‘impeach this’ map with a transition to a cartogram

Diaspora + Signal ?

En vertu d'un nouvel accord signé avec les États-Unis, Facebook et WhatsApp seront obligés de divulguer le contenu des messages chiffrés de leurs utilisateurs à la police britannique

#Facebook #vieprivee #encore

Chers amis sur framasphere, cherchez votre nouveau pod.

Déframasoftisons Internet !

https://www.bloomberg.com/graphics/2019-why-amazon-rainforest-is-on-fire/

#globalwarming #nomorewords #actions

En Islande, Okjökull n’est plus un glacier. Et « tous nos glaciers suivront la même voie »

N'oublions pas que #github est désormais propriété de #Microsoft, grand #colabo avec les services de renseignement US. Avez vous essayé gitlab ou une de ses instances ? Vous devriez...

GitHub confirme avoir bloqué les développeurs en Iran, en Syrie et en Crimée le blocage s'étend désormais au Cuba et à la Corée du Nord

#environnement #politique

See the drastic toll climate change is taking on our oceans https://www.nationalgeographic.com/environment/2019/06/see-the-drastic-toll-climate-change-is-taking-on-our-oceans/

Qu'est ce que Twitter Follow Helper?

Twitter Follow Helper est un script Greasemonkey (ou une extension Chrome) destiné à faciliter la décision de suivre ou non quelqu'un sur Twitter. Sur chaque page de profil, le script ajoute des informations sur l'activité de la personne :

• Est-ce que la personne te suit? > oui ou non
  obtenu par l'interrogation de DoesFollow (malheureusement la nouvelle interface twitter utilise déjà l'API et m'empêche donc de poser la question)
  
• Convergence du Graphe Social? > en % et combiens de followers, de following (friends) et de connecteurs vous avez en commun
  obtenu par interrogation de twtrfrnd. Le % est un indicateur forgé de toute pièce à partir des amis et followers en commun. J'expliquerai mieux quand j'aurais du temps. On peut considérer que moins de 1% est peu, que moins de 5% est un début de relation, et que plus de 10% est beaucoup.
• Taux de @réponses? > en %
  obtenu par l'interrogation de l'API FollowCost.
• Est-ce que la personne met des étoiles? > nombre d'item étoilés par la personne ou pour elle
  obtenu par l'interrogation de FavStar. A noter que si la personne n'utilise pas FavStar (c'est dommage) on ne peut connaitre le nombre de ses items qui ont reçu une étoile. supprimé à partir de la version 0.6 : information jugée non pertinente.
• Quelle quantité de tweets produit la personne? > nombre de tweets par jour récemment et valeur en mΣ. et valeur en mΣ depuis la création du compte.
  obtenu par l'interrogation de l'API FollowCost (oui à nouveau. Mais je le fais en même temps en fait ;-). Pour la valeur en milliscoble on peut considérer que moins de 100 est peu, plus de 500 déjà pas mal et plus de mille beaucoup (trop?). mais chacun a sa propre résistance et capacité de lecture...
  
• Grader score de la personne? > en %.
  obtenu par l'interrogation de Twitter Grader. supprimé à partir de la version 0.6 : tout le monde est à au moins 80%...
• Klout score de la personne ? > en % et avec (un type). Il s'agit d'un indicateur d'influence.
  obtenu par l'interrogation de Klout. On peut considérer que au delà de 25 le score est moyen et au dessus de 40 fort. Mais le type (Activist, Broadcaster, Taste Maker,... 16 types) est aussi important.
• score de recherche de la personne? > en mentions par jour.
  obtenu par l'interrogation de l'API Twitter par comptage nombre de fois où la personne est mentionnées dans les derniers tweets. La valeur est assez volatile...
• Quelles sont les twittos/as qu'elle aime ? > une liste de twittos/as qui sont retweetées, qui ont des réponses de la par de la personne. Très pratique pour trouver de nouveaux amis...
  obtenu par l'interrogation de l'API AutoFF. 10 twittos/as ou moins, les 3 premiers sont affichés par défaut, les autres par survol de la liste...

Installation

Merci de noter que c'est un bricolage permanent. Il y a sans doute des bugs. N'hésitez pas à m'en faire part et soyez patients : j'ai une famille des amis et un travail qui sont plus importants pour moi que ce bout de code.

Firefox 

Ce script s'installe comme n'importe quel script Greasemonkey. Cliques sur ce lien et accepte l'installation (je jure qu'il n'y pas de code malicieux). Tu peux aussi parcourir le code sur userscript.org... Le script sera sans doute mis à jour de temps en temps. Mais grâce à la magie de GM Script Update Control vous serez toujours informé...

Chrome

Dans le temps, le script marchait bien avec l'extension TamperMonkey. Mais il était devenu trop lourd de maintenir une version qui soit compatible avec les deux. Du coup, je vous ai mitonné  l'extension Twitter Follow Helper qui donne (normalement) le même résultat que le userscript.

Contribuer

Laisses vos commentaires (ça me changera des spams), suggestions, rapports de bugs ci dessous ou sur la page du script. Les compliments et autres sont aussi bienvenus...

Si tu as quelques pièces poussiéreuses au fond d'une poche, n'hésite pas à m'encourager à faire mieux, j'irais boire une bière à ta santé.

A propos de ce script

En tant qu'être humain utilisant Twitter n'utilisant aucun robot pour lire mes tweets et essayant de rester un peu sociable, j'avais des difficultés pour décider si je devais suivre quelqu'un ou pas. Suivre tout le monde et n'importe qui est le meilleur moyen de crouler bêtement sous les tweets.

Il y a plein d'outils partout sur internet qui donnent des statistiques sur les comptes twitter. Mais c'est un peu lourd de tous les visiter à chaque fois.

Twitter Follow Helper était né.

Historique des modifications

• version 0.6 [20120530]
  • mise en compatibilité avec le nouveau nouveau twitter
  • suppression des informations favstar et twitter grader jugées sans intérêt
  • mise en place de l'extension Chrome
• version 0.5b [20110428] corrections suite à des modifications dans les pages de profil de Twitter et Favstar
• version 0.5 [20101028] intégration du nouveau Twitter (+ quelques bugs)
• version 0.3 [20100625] corrections mineures et ajouts
  • influence de la personne et type d'influence? (score et type Klout)
  • qui la personne aime-t-elle? (via autoFF)
• version 0.2b [20100420] corrections mineures
• version 0.2 [20100420] première version publique
  
  • la personne te suit-elle?
  • fait-elle partie de ton réseau? (convergence du Graphe Social via twtrfrnd)
  • est-elle sociable (taux de @replies)? (via FollowCost)
  • aime-t-elle les étoiles? (via FavStar)
  • poste-t-elle beaucoup? (via FollowCost)
  • fait-elle partie des stars? (via Twitter Grader)
  • est-elle mentionnée souvent? (via Twitter API)

What is Twitter Follow Helper?

Twitter Follow Helper is a Greasemonkey userscript / Chrome extension tool designed to help you to decide wether or not you should follow someone on Twitter. On any profile page, the script will add some informations about the activity of the person you're looking at :

• Does the tweepl follows you? > yes or no
  provided by asking to the DoesFollow (unfortunately new twitter already uses API for telling if you follow the tweepl so can't use again)
• Social Graph Convergence? > in % and how many common followers, friends and connectors you have.
  provided by asking twtrfrnd. The % is a forged indicator from common followers and friend. Consider that under 1% is low, under 5% is emerging, and more than 10% is much. I will post about the method when i got time...
• What's the @replies rate? > in %
  provided by asking to FollowCost API.
• Does the tweepl like to star items? > items s/he starred and was starred
  provided by asking FavStar. Note that if the tweepl doesn't use Favstar, you wont be able to know how many times their tweet were starred. not more maintained since it was not accurate...
• How many tweets does the tweepl post? > recent tweets a day and mΣ value. All time mΣ value also.
  provided by asking to FollowCost API (yes again. But in the same time you know ;-). Value is displayed in milliscoble. Consider that under 100 is low, over 500 is enough and over 1000 is (too?) much
• What's the tweepl Grader score? > in %.
  provided by asking to Twitter Grader. not more maintained (everybody has a 80% score, so it's not signifiant)
• What's the tweepl Klout score? > in % an influence indicator and a type class for the tweepl
  provided by asking to Klout. Consider that over 25 is average and over 40 is strong. Type is suspended since Klout API doesn't throw it...
  
• What's the tweepl Search score? > in mentions a day.
  provided by asking to Twitter API. Counting how often @tweepl is mentionned in recent tweets.
• Who does the tweepl like? > a list of tweeples that are replied, retweeted by the tweepl. Useful to find other friends...
  provided by asking to AutoFF API. 10 or less tweeples, first 3 are displayed, and others when you hover...
  

Download and install

Please note this script will always be under "developement". It might be a bit buggy. Feel free to tell me behind and be patient, i have a family, some friends and a job that are more important than this script for me.

Firefox

You can install this script as any Greasemonkey userscript : click on this script link and agree with install terms. The script is hosted on userscripts which is a huge script repository for Greasemonkey. You can also browse the code there... the script will probably be updated from time to time. But with the magic of GM Script Update Control the script should prompt you about any update.

Chrome

The script used to work through tampermonkey. However, it has become more and more tricky to maintain dual compatibility with firefox. So you can know access all functionality with Twitter Follow Helper extension

Contribute

Leave your requests, comments or bugs report on just here down or on the userscripts.org page. You can also post anything else...

If you have some old dusty coins, you can put them in my moneybox. It's a good way to tell me you like this.

About this script

As I'm using Twitter like a human being, not using any bot to parse my timeline or follow anybody and trying to keep conversational, it was very difficult for me to decide whether or not i should follow someone : Following anybody is the best way to collapse under timeline stupid overload.

There are lot of tools all over the internet giving you some good stats on any account. But you can't visit them each time you are about following someone.

Twitter Follow Helper was born.

History

• version 0.6 [20120530]
  • adapted to new new twitter style and code (many bug fix and code rewrite)
  • removed favstar and twitter grader as they were pointless
  • first chrome extension version released
• version 0.5b [20110428] bug fixes after updates on Twitter and Favstar profile pages
• version 0.5 [20101028] integrating new twitter ui and minor fixes
• version 0.3 [20100625] minor fixes and added
  • is the tweepl influent and how? (Klout score and type)
  • who does the tweepl like? (via autoFF)
• version 0.2b [20100420] minor fixes
• version 0.2 [20100420] first release
  
  • is the tweepl following you?
  • is s/he in your current network? (Social Graph Score via twtrfrnd)
  • is s/he conversationale (@replies rate)? (via FollowCost)
  • does s/he like to star items? (via FavStar)
  • is s/he a big poster? (via FollowCost)
  • is s/he a graduated tweepl? (via Twitter Grader)
  • is s/he mentioned in tweets? (via Twitter API)

Allez, ne boudons pas notre plaisir, d'autant que je ne poursuis pas la gloire. J'ai quand même droit dans l'annonce à un lien vers la page du script sur le AirCarnet, qui m'a valu près de 400 visiteurs, ainsi qu'à mon nom dans l'extension. Et surtout, le plaisir de savoir que mon travail va être utilisé par beaucoup plus de monde...

• Userscript developpers can include the script in their own to help their users to keep up-to-date.
• Userscript users can include the script in any of their userscript coming from userscript.org to keep up-to-date. It's very easy to do with any text-editor...

How to use it?

Good old method : Copy and Paste

1. Copy part of the source script between

   /* COPY ALL THIS -> END  */

   and

   /* END OF COPY ZONE */

2. Paste it in your own script just after

   // ==/UserScript==

3. Update the two vars for Id (Id is the ref number of the script in userscripts : http://userscripts.org/scripts/show/yourScriptId) and current version of your script (duplicate of @version yourScriptVersion metadata). Please, remember not to put any space in your version number use _ (underscore) instead.

   var myScriptId=yourScriptId
   var myScriptVersion="yourScriptVersion";

   You can also set control frequency in order to consume less bandwidth set this with this parameter :

   var GMSUCfreq=9;			// frequence of control updates (days)

4. You might like to customize (very little)
   • Delay before alert disapears (set to 0 if you don't want it to disapear) :

     var GMSUCtime=16;		// delay before alert disapears. 

   • Choose your color palette :

     var GMSUCPal=cpUserscript; 	// colorPalette you prefer

     three are proposed : cpChrome, cpUserscript or cpFlickr, but you may ad any you want to create by defining a new one using var yourPalette=new colorPalette(background,highlight,foreground,light);
5. That's all, enjoy...

Brand new method may be not working : @require

I did test this method on this testing script and it seems to work.

There are some limitation of @require usage in GreaseMonkey : The GM Script Update Control used by your script will be the one available at the date of the FIRST install by your users. If you update your script, GM_scriptVersionControl function WILL NOT upgrade to last version. Users will have to uninstall and reinstall your script to have it updated. It may cause some compatibility problems...

1. ad the @require parameter in the header of your script
   

   // @require http://userscripts.org/scripts/source/35611.user.js

2. redefine the mandatory parameters
   

   thisId=yourScriptId;
   thisVersion="yourScriptVersion";

3. customize if you want with any of the other parameters. See above for more details
   

   GMSUCfreq=9;    // control frequency
   GMSUCtime=16;   // disapearing delay
   GMSUCPal=cpUserscript;  // color palette

4. Launch the script in yours
   

   GM_scriptVersionControl();

Do i need to install it?

Definitely not. You may only copy-paste the function from the source script.
But you may find useful to be informed of future updates. If installed, the GmScript will prompt you about this...

Contribute

Translations

the alert message is displayed in French or in English (default) using the navigator.language property. If you put any translation in comment here or there, i will be pleased to implement it. Use the following models please :

// français
Txt[1]["fr"]="Vous utilisez la version";
Txt[2]["fr"]="du script";
Txt[3]["fr"]="La version officielle est différente";
Txt[4]["fr"]="installer";
Txt[5]["fr"]="voir le code";
Txt[6]["fr"]="propulsé par";
// english
Txt[1]["en"]="You're using";
Txt[2]["en"]="version of";
Txt[3]["en"]="script. Official release version is different";
Txt[4]["en"]="install";
Txt[5]["en"]="view code";
Txt[6]["en"]="powered by";

Color palette

If you think you're a color genius and defined a pretty nicest of the world colorPalette, post it here or there...

Anything else

As you can see through Revisions history, i'm very pleased about any comment you can do about this script and its functionalities. And I manage to take care of your idea when i got time for this. Please, don't wait and put anything you brain has in about this script here or there...

Licence

as I had no idea about licensing this work, i putted it under the creative-commons by-nc-sa one.

Revisions history

• version 0.5 (2009 06 01)
  • testing enabling @require usage in order to please IzzySoft. Please note :
    • it may not work. I can't test it since none of the script containing @require can be installed on my computer and I don't know why,
    • your GM Script Update Control version will not be updated for your users each time your script is. Users will have to de-install and re-install to have last GM Script Update Control version.
  • added colorPalette management developped for Google Smart Subscriber and made some minor cosmetics "improvements".
• version 0.4 (2009 04 17)
  • you may now set control frequency for your script in order to avoid too much bandwidth consumption. However, all users connected on release date will be proposed for an update... Special thanks to NOrack who gave me this idea.
• version 0.3 (2009 04 12)
  • now finding script version using meta.js instead of show page. Many thanks to sizzlemctwizzle for this enhancement.
• version 0.2 (2009 04 06)
  • fixed bug in Firefox 3.1b/3.5b : new way to handle characters by the DOM causing bad interpretation of version id. Script now cleaning version number for any space, null, return or any "strange" character.
  • fix userscript homepage bug when not logged in (google ad javascript comment marked with <!-- * */--> instead of /* */
  • version only verified in main window
• version 0.1 (2008 11 26)
  • version 0.1.b (2009 01 21) : updated script to include new userscript.org script page layout (it's very versatile isn't it?)
  • modified display : three button to go to homepage, source code or install and a link to this page
  • minor bugs removed
• version 0.0.4 (2008 11 14)
  • moved styling, alert text to avoid loading when not needed
  • added auto-hide of alert message to make script less obstrusive. You might disable it by editing parameters (see above)
  • some customization now (colors) ;-)
• version 0.0.3 (2008 10 21)
  • gave up remote calling (for the moment)
  • inverted id and version vars (it's way more logical now ;-)
  • rewrited code to embed all parameters (lang, style...) in function
• version 0.0.2
  • added en/fr language support
  • testing script without @include meta
• version 0.0.1
  • a : bugs correction
  • added scriptId
• version 0.0.0 : initial release