Ti saluto!
Ho brutte notizie per te.
10/11/2019 - Quel giorno, ho violato il tuo sistema operativo e ho ottenuto pieno accesso al tuo account.
Non è necessario modificare la password, il mio malware la intercetta ogni volta.
Come è stato:
Il software del router a cui eri connesso quel giorno aveva una vulnerabilità.
Ho hackerato per la prima volta questo router e lì ho inserito il mio codice dannoso.
Quando sei entrato in Internet, il mio Trojan era installato sul sistema operativo del tuo dispositivo.
Successivamente, ho eseguito un backup completo del tuo disco (ho tutta la tua rubrica,
cronologia di visualizzazione di siti, tutti i file, numeri di telefono e indirizzi di tutti i tuoi contatti).
Un mese fa, volevo bloccare il tuo dispositivo e chiedere un po 'di soldi per sbloccarlo.
Ma ho dato un'occhiata ai siti che visiti regolarmente ed è stato bello vedere le tue risorse preferite.
Sto parlando di siti per adulti.
Voglio dire, sei un grande pervertito. Hai una fantasia sfrenata!
Successivamente, mi è venuta in mente un'idea.
Ho fatto uno screenshot del sito intimo Where Do You Settle It (capisci cosa intendo?).
Successivamente, ho realizzato un video del tuo divertimento (usando la fotocamera del tuo dispositivo). Si è rivelato bellissimo!
Sono fermamente convinto che non vorresti mostrare queste foto ai tuoi parenti, amici o colleghi.
Penso che 499 € sia una somma molto piccola per il mio silenzio.
Inoltre, ho trascorso molto tempo con te!
Accetto denaro solo in Bitcoin.
Il mio portafoglio BTC: 1BGo1VfZzHRG2yYh3TPXJyRTiLpGaXyJGy
Non sei sicuro di come ricostruire un portafoglio Bitcoin?
In qualsiasi motore di ricerca, scrivi "Wie kaufe ich Bitcoin?".
È più facile che inviare denaro a una carta di credito!
Per il pagamento, è necessario farlo lo stesso giorno di ricezione di questa e-mail.
Non preoccuparti, il timer inizierà nel momento in cui apri questa lettera. Sì, sì .. è già iniziato!
Dopo il pagamento, il mio virus e le tue foto sporche con te si autodistruggono.
Se non ricevo la quantità specificata da te, il tuo dispositivo verrà bloccato e tutti i tuoi contatti riceveranno una foto con le tue "gioie".
Voglio che tu stia attento.
- Non tentare di trovare e distruggere il mio virus! (Tutti i tuoi dati sono già caricati su un server remoto)
- Non tentare di contattarmi (non è possibile, ti ho inviato un'e-mail dal tuo account)
- Vari servizi di sicurezza non ti aiuteranno. Anche la formattazione di un disco o la distruzione di un dispositivo non ti aiuteranno, poiché i tuoi dati sono già su un server remoto.
P.S. garantisco che non ti darò più fastidio dopo il pagamento, perché non sei la mia unica vittima.
È un codice d'onore per gli hacker.
Da ora in poi, ti consiglio di usare buoni antivirus e aggiornarli regolarmente (più volte al giorno)!
Non essere arrabbiato con me, ognuno ha il proprio lavoro.
Addio.
Hi everyone,
We received multiple demands to postpone the IWST deadline. To increase
papers quality and number, we decided to postpone the deadline to the
28th of July (https://esug.github.io/2020-Conference/cfpIWST2020.html).
We hope this new deadline will give all the authors more time to polish
their papers!
Thanks to all for your submissions and contributions, let's keep the
great spirit and legacy of IWST a reality!
Vincent Aranega
Hi everyone,
In light of the continued uncertainty surrounding the Covid-19
situation, to guarantee the safety and well-being of all, the IWST
Steering Committee has decided to move to a virtual event format for
this year to be held Sept. 29th and 30th. The 2020 paper review, WiP
submission and acceptance processes will proceed normally with a
modification of the upcoming deadlines:
- Submission deadline: July 15th, 2020
- Notification deadline: September 8th, 2020
- Workshop: September 29-30th, 2020.
Like last year, we are very proud to announce a Best Paper Award. We
thank the Lam Research Corporation for its financial contribution which
makes it possible for prizes for the three best papers. We are also
happy to announce that accepted papers will be published in the ACM
Digital Library.
We will follow up with further details on conference organization,
presentation formats, and howto guides.
The global idea is to collect all required material a week ahead of
schedule to prevent any live technical issue: slides, but also video.
Only the post presentation Q&A sessions will be interactive.
IWST has now a significant history and has served for years as a smart
playground for young researchers to practice writing articles &
presenting results.
In parallel, senior researchers take benefit from IWST to expose mature
work and propose some retrospective or draw future directions.
Mixing these two kinds of contributors makes IWST that attractive.
Let’s do the 2020 edition conformed to this legacy
https://esug.github.io/2020-Conference/cfpIWST2020.html
Vincent Aranega
Loïc Lagadec
This may interest some of you.
I’m PC chair of the following conference.
S.
FIRST CALL FOR PAPERS - ICSR 2020, November 9-11, 2020, Hammamet - TUNISIA
19 th INTERNATIONAL CONFERENCE ON SOFTWARE AND SYSTEMS REUSE
www.icsr2020.org
The International Conference on Software and Systems Reuse (ICSR) is the premier event in the field of software reuse research and technology. The main goal of ICSR is to present the most recent advances and breakthroughs in the area of software reuse and to promote an intensive and continuous exchange among researchers and practitioners.
The 19th International Conference on Software and Systems Reuse (ICSR-2020) will be held on November 9-11 2020, in Hammamet, Tunisia. The guiding theme of this edition is:
*Reuse in emerging software engineering practices*
We invite submissions on new and innovative research results and industrial experience reports dealing with all aspects of software reuse within the context of the modern software development landscape, characterized by: 1) Large ecosystems of reusable, open-source components and service-oriented, containerized cloud-hosted applications; 2) Context-aware (IoT) applications, which combine a complex and heterogeneous mix of ever more powerful hardware and evolving software frameworks and containers; and 3) The resurgence of AI as both, (i) an enabling technology for reuse for domain engineering (e.g. domain ontologies, identification of reusable assets) and application engineering (e.g. component retrieval), and (ii) an object of reuse that addresses the full lifecycle and scope of “intelligent” software components, i.e. well beyond the simple (re)use of machine learning libraries. These developments have had important—and sometimes contradictory—effects on reuse theory and practice.
We welcome papers dealing with : 1) Reuse organizational, managerial, economic, and legal issues, in general, and as they pertain to the new development landscape, 2) Technical aspects of reuse, in general (see full CFP at www.icsr2020.org), and as they pertain to large ecosystems of open-source libraries (npm, pip, etc), IoT frameworks, and machine learning artefacts (business components, models, libraries, training data, etc.), and 3) Software reuse in industry (success & failure stories; success factors and lessons learned; ROI studies).
As with previous editions, accepted papers will appear in the conference proceedings, to be published by Springer’s Lecture Notes in Computer Science. New this edition, the program committee will award a Best Paper Award to the best paper in terms of, 1) originality, 2) presentation, and 3) impact. The finalists will be submitted to a special issue of a refereed journal.
*Research paper abstracts due June 19th, 2020, full papers due July 3rd, 2020*.
*Please check the conference site for more information: www.icsr2020.org*
--------------------------------------------
Stéphane Ducasse
http://stephane.ducasse.free.fr / http://www.pharo.org
03 59 35 87 52
Assistant: Julie Jonas
FAX 03 59 57 78 50
TEL 03 59 35 86 16
S. Ducasse - Inria
40, avenue Halley,
Parc Scientifique de la Haute Borne, Bât.A, Park Plaza
Villeneuve d'Ascq 59650
France
--------------------------------------------
Stéphane Ducasse
http://stephane.ducasse.free.fr / http://www.pharo.org
03 59 35 87 52
Assistant: Julie Jonas
FAX 03 59 57 78 50
TEL 03 59 35 86 16
S. Ducasse - Inria
40, avenue Halley,
Parc Scientifique de la Haute Borne, Bât.A, Park Plaza
Villeneuve d'Ascq 59650
France
hello,
I am trying to achieve something like
RTInteractionExample>>exampleExpandable but with several levels of
expansion: a node with nodes inside with nodes inside
and each container node can be "opened" (expanded) or closed.
Not sure how to do it and mainly how to resize all the ancestors of a
node when an inner node is expanded
imagine for example representing the pharo class hierarchy as a single
Object node, clicking on the node expand it and shows all its
subclasses inside, clicking on a subclass expands it, ...
Any suggestion ?
nicolas
--
Nicolas Anquetil
RMod team -- Inria Lille
TL;DR: Reviewing form for Roassal3: https://docs.google.com/forms/d/1-8CJM5_TDu3HBE2d_2dPjqq1pTLZRuauMtPcZZYZXI…
Longer version:
Dear Community,
Right after ESUG 2019 we released a beta version of Roassal3, and we got many very constructive feedbacks from all over the World. We thank you for this. We really tried to improve Roassal3 and specially to provide a smooth and intuitive API to lower the entrance bar for Roassal3.
Now is time to enter a new reviewing phase. Our ultimate goal is to provide the visualization engine that the Pharo and Smalltalk communities deserve.
The GiHub page contains some information, including a small tutorial:
https://github.com/ObjectProfile/Roassal3
Additional tutorials will soon come.
You can install Roassal3 either from the catalog (just look for Roassal3), or execute the following instruction:
Metacello new
baseline: ‘Roassal3’;
repository: ‘github://ObjectProfile/Roassal3’;
load.
Roassal3 comes with many examples. You should look for the package: Roassal3-Examples
We would like to end the reviewing page at the end of March 2020. A second edition of Agile Visualization will begin after March 31. Your comment will definitely have an impact on this new book.
Reviewers of Roassal3 will:
- Have their name listed in Roassal3's website
- Have their name listed in the new edition of Agile Visualization
- Have a beer next time we meet at ESUG or at Annual Smalltalk meetup in Palo Alto
- Make the Pharo community stronger, really.
Here is the google form to gather your feedback: https://docs.google.com/forms/d/1-8CJM5_TDu3HBE2d_2dPjqq1pTLZRuauMtPcZZYZXI…
Thanks!
The Roassal3 development team
Hi!
In Moose there is a project call "Hashtable". The goal of this project
is to provide faster collections when they have a big number of
elements.
I think this is something that can be useful for more than just Moose
so I extracted it to pharo-contributions so that we can use it and
improve it more.
https://github.com/pharo-contributions/Hashtable
Have a nice day.
--
Cyril Ferlicot
https://ferlicot.fr
Ich grüße dich!
Ich habe schlechte Nachrichten für dich.
30.12.2018 - An diesem Tag habe ich mich in Ihr Betriebssystem gehackt und vollen Zugriff auf Ihr Konto erhalten moose-dev(a)iam.unibe.ch . Das Kennwort muss nicht geändert werden, meine Malware fängt es jedes Mal ab.
Wie es war:
Die Routersoftware, mit der Sie an diesem Tag verbunden waren, wies eine Sicherheitsanfälligkeit auf.
Ich habe diesen Router zum ersten Mal gehackt und meinen bösartigen Code darin abgelegt.
Als Sie ins Internet gingen, war mein Trojaner auf dem Betriebssystem Ihres Geräts installiert.
Danach habe ich eine vollständige Sicherung Ihrer Festplatte erstellt (ich habe Ihr gesamtes Adressbuch,
Anzeigen des Verlaufs, aller Dateien, Telefonnummern und Adressen für alle Ihre Kontakte).
Vor einem Monat wollte ich Ihr Gerät sperren und um etwas Geld bitten, um es zu entsperren.
Aber ich habe mir die Websites angesehen, die Sie regelmäßig besuchen, und es war großartig, Ihre Lieblingsressourcen zu sehen.
Ich spreche von Websites für Erwachsene.
Ich meine - du bist ein großer Perversling. Sie haben eine ungezügelte Fantasie!
Danach kam mir eine Idee.
Ich habe einen Screenshot von der intimen Website gemacht, auf der Sie zufrieden sind (Verstehen Sie, was ich meine?).
Danach habe ich ein Video von deinem Spaß gemacht (mit der Kamera deines Geräts). Es stellte sich heraus, schön!
Ich bin der festen Überzeugung, dass Sie diese Fotos nicht Ihren Eltern, Freunden oder Kollegen zeigen möchten.
Ich denke 900 € Pisse sind eine sehr kleine Summe für mein Schweigen.
Außerdem habe ich viel Zeit mit dir verbracht!
Ich akzeptiere Geld nur in Bitcoins.
Mein BTC-Portfolio: 15rTvVeAv89rtWh5c228X1KUznipbcsCn6
Sie sind sich nicht sicher, wie Sie eine Bitcoin-Brieftasche wiederherstellen sollen?
Schreiben Sie in jede Suchmaschine, wie Sie Geld an eine BTC-Brieftasche senden.
Es ist einfacher als Geld an eine Kreditkarte zu senden!
Für die Bezahlung haben Sie etwas mehr als zwei Tage Zeit (genau 50 Stunden).
Keine Sorge, der Timer startet, sobald Sie diesen Brief öffnen. Ja, ja ... es hat schon begonnen!
Nach der Bezahlung zerstören sich mein Virus und Ihre schmutzigen Fotos mit Ihnen selbst.
Wenn ich nicht den angegebenen Betrag von Ihnen erhalte, wird Ihr Gerät blockiert und alle Ihre Kontakte erhalten ein Foto mit Ihren "Freuden".
Ich möchte, dass du vorsichtig bist.
- Versuchen Sie nicht, meinen Virus zu finden und zu zerstören! (Alle Ihre Daten wurden bereits auf einen Remote-Server hochgeladen.)
- Versuchen Sie nicht, mich zu kontaktieren (es ist nicht möglich, ich habe Ihnen eine E-Mail von Ihrem Konto gesendet)
- Verschiedene Sicherheitsdienste helfen Ihnen nicht. Das Formatieren einer Festplatte oder das Zerstören eines Geräts hilft Ihnen auch nicht, da sich Ihre Daten bereits auf einem Remote-Server befinden.
PS: Ich garantiere, dass ich Sie nach der Zahlung nicht störe, weil Sie nicht mein einziges Opfer sind.
Es ist ein Ehrenkodex für Hacker.
Ab sofort rate ich Ihnen, gute Antivirenprogramme zu verwenden und diese regelmäßig (mehrmals täglich) zu aktualisieren!
Sei mir nicht böse, jeder hat seinen eigenen Job.
Auf Wiedersehen.
Le mar. 3 déc. 2019 à 12:34, Nour Jihene Agouf <a.n.djihan(a)gmail.com> a
écrit :
>
>
> Le mar. 3 déc. 2019 à 12:09, Stéphane Ducasse <stephane.ducasse(a)inria.fr>
> a écrit :
>
>>
>>
>> On 3 Dec 2019, at 11:46, Nour Jihene Agouf <a.n.djihan(a)gmail.com> wrote:
>>
>> Hello,
>>
>> The ClassNames Blueprint is based on packages (package models). There is
>> no package model in the moose panel when generating an mse file of a
>> certain project.
>>
>>
>> How do you import it.
>>
> "Import model from MSE file"
>
>> let us move this discussion to the moose mailing0-list
>>
>> However, if we import FAMIX smalltalk model from the current image we get
>> "all package models" in the moose panel which shows a FAMIXPackageGoup of
>> the selected packages which we can later on visualize.
>> This way the FeatureSelector (first layer) from my thesis project will be
>> replaced by: directly selecting the packages we want to visualize from the
>> moose panel and calling the new visualize method.
>>
>> Basically these will be the steps:
>> 1- Import FAMIX smalltalk model from the current image,
>> 2- click on all package models,
>> 3- "self visualiseCNB" => this method will visualize the ClassNames
>> Blueprint of the selected packages.
>>
>>
>> No click we should be able to program that.
>>
> Do you mean a ClassNames Blueprint option in the navigation panel?
>
>> Then and only then we can have an action in the menu.
>>
>
>> Stef
>>
>>
>> Nour
>>
>>
>> Le lun. 25 nov. 2019 à 21:57, Nour Jihene Agouf <a.n.djihan(a)gmail.com> a
>> écrit :
>>
>>> Okey I'm on it :)
>>>
>>> Le lun. 25 nov. 2019 à 21:32, Stéphane Ducasse <
>>> stephane.ducasse(a)inria.fr> a écrit :
>>>
>>>> here is what I suggest.
>>>>
>>>> You create a separate package that should be the only one manipulating
>>>> Moose metamodel.
>>>> This way your project will work without Moose and when you load this
>>>> extra package, it will work with Moose.
>>>>
>>>> S.
>>>>
>>>> On 25 Nov 2019, at 21:13, Nour Jihene Agouf <a.n.djihan(a)gmail.com>
>>>> wrote:
>>>>
>>>> Okey, I will :)
>>>>
>>>> Le lun. 25 nov. 2019 à 21:09, Stéphane Ducasse <
>>>> stephane.ducasse(a)inria.fr> a écrit :
>>>>
>>>>>
>>>>>
>>>>> Hello,
>>>>>
>>>>> Yes that would be great!
>>>>>
>>>>>
>>>>> Ok we will come back with a list
>>>>> The first one is to make sure that your visualsiation (class name
>>>>> blueprint can run on top of Moose)
>>>>> you should ask for help on discord about Moose).
>>>>>
>>>>>
>>>>> And about the visa, unfortunately there is no available dates to
>>>>> submit my visa application;, the closest date is in January 2020. Taking
>>>>> under consideration the time for the file processing which is about 2 to 3
>>>>> months, should I ask Alexia for an other promise of employment starting
>>>>> from 01/03/2020? I hope I receive the hosting agreement before January,
>>>>> However, I don't know if this delay has other complications, if so let me
>>>>> know please.
>>>>>
>>>>>
>>>>> no ask again
>>>>>
>>>>>
>>>>> Nour
>>>>>
>>>>>
>>>>> Le lun. 25 nov. 2019 à 17:19, Stéphane Ducasse <
>>>>> stephane.ducasse(a)inria.fr> a écrit :
>>>>>
>>>>>> Hi nour
>>>>>>
>>>>>> We are discussing with Oleksandr and we were thinking if we should
>>>>>> propose you some small objectives
>>>>>> so that you can learn more waiting for your visa.
>>>>>>
>>>>>> So let me know.
>>>>>>
>>>>>> Stef
>>>>>> --------------------------------------------
>>>>>> Stéphane Ducasse
>>>>>> http://stephane.ducasse.free.fr / http://www.pharo.org
>>>>>> 03 59 35 87 52
>>>>>> Assistant: Julie Jonas
>>>>>> FAX 03 59 57 78 50
>>>>>> TEL 03 59 35 86 16
>>>>>> S. Ducasse - Inria
>>>>>> 40, avenue Halley,
>>>>>> Parc Scientifique de la Haute Borne, Bât.A, Park Plaza
>>>>>> Villeneuve d'Ascq 59650
>>>>>> France
>>>>>>
>>>>>>
>>>>> --------------------------------------------
>>>>> Stéphane Ducasse
>>>>> http://stephane.ducasse.free.fr / http://www.pharo.org
>>>>> 03 59 35 87 52
>>>>> Assistant: Julie Jonas
>>>>> FAX 03 59 57 78 50
>>>>> TEL 03 59 35 86 16
>>>>> S. Ducasse - Inria
>>>>> 40, avenue Halley,
>>>>> Parc Scientifique de la Haute Borne, Bât.A, Park Plaza
>>>>> Villeneuve d'Ascq 59650
>>>>> France
>>>>>
>>>>>
>>>> --------------------------------------------
>>>> Stéphane Ducasse
>>>> http://stephane.ducasse.free.fr / http://www.pharo.org
>>>> 03 59 35 87 52
>>>> Assistant: Julie Jonas
>>>> FAX 03 59 57 78 50
>>>> TEL 03 59 35 86 16
>>>> S. Ducasse - Inria
>>>> 40, avenue Halley,
>>>> Parc Scientifique de la Haute Borne, Bât.A, Park Plaza
>>>> Villeneuve d'Ascq 59650
>>>> France
>>>>
>>>>
>> --------------------------------------------
>> Stéphane Ducasse
>> http://stephane.ducasse.free.fr / http://www.pharo.org
>> 03 59 35 87 52
>> Assistant: Julie Jonas
>> FAX 03 59 57 78 50
>> TEL 03 59 35 86 16
>> S. Ducasse - Inria
>> 40, avenue Halley,
>> Parc Scientifique de la Haute Borne, Bât.A, Park Plaza
>> Villeneuve d'Ascq 59650
>> France
>>
>>
I could present TaskIT of course, but i don't feel it matching in the
proposed categories. There is not debugging, nor emerging minimalist
language nor research tools. I will check on the other rooms to see if i
find a place where i can do it.
El lun., 28 oct. 2019 a las 21:00, ducasse (<stepharo(a)netcourrier.com>)
escribió:
>
>
> On 28 Oct 2019, at 18:15, Santiago Bragagnolo <
> santiagobragagnolo(a)gmail.com> wrote:
>
> That is great. We should post in all of them if possible.
> I think that Steven could show object centric debugging, someone (anne
> maybe? ) present moose. and for minimalistic experimental emerging
> languages carolina could propose candle and the bootstrap processes.
> I think that Steven and Carolina talks are mature enough after all the
> trials, and a moose talk could be really cool. Maybe Julien's SQL or
> Benoit's translations should be really good for catching potential students
> and specially some investment capital for the team :).
>
> Sadly me i don't have much to show :(.
> But if we have the stand i plan to be there.
>
>
> TaskIt?
> I could do a presentation of Pharo in the minimalist…. and carolina a talk
> showing how to bootstrap.
>
>
>
>
>
> El lun., 28 oct. 2019 a las 16:41, ducasse (<stepharo(a)netcourrier.com>)
> escribió:
>
>>
>> https://fosdem.org/2020/news/2019-10-01-accepted-developer-rooms/
>> I do not know in which one we want to participate
>>
>> Debugging Tools
>> Minimalistic, Experimental and Emerging Languages
>> Open Research Tools and Technologies
>>
>> How do we coordinate?
>>
>> S.
>>
>
>