Je vous propose de m'accompagner dans une séance d'archéologie numérique à la recherche des sites internet les plus étranges.

L’histoire d’un site d’information qui débarque dans le paysage médiatique au moment même où la plupart des grands groupes de presse se font racheter par des milliardaires.

If you want to hide the following overlay message on SlideShare presentations:

You are reading a preview.
Activate your 30 day free trial to continue reading.

...you can use the following custom filter :

www.slideshare.net##DIV[class="limit-overlay"]
fr.slideshare.net##DIV[class="limit-overlay"]

The custom filter I use:

www.artstation.com##SUPPORT-ARTSTATION-BLOCK
www.artstation.com##DIV[class="home-blocks"]
www.artstation.com##SECTION[class="home-featured home-featured-jobs"]
www.artstation.com##DIV[class="home-featured"]
www.artstation.com##DIV[class="gallery-marketplace-inner"]
www.artstation.com##FOOTER[class="community-footer"]
www.artstation.com##PRODUCTS-LIST
www.artstation.com##DIGITAL-PRODUCT-PREVIEW
www.artstation.com##MARKETPLACE-POPULAR-PRODUCT
www.artstation.com##SUPPORT-ARTSTATION

“Le fait pour toute personne de présenter un contenu ou une activité comme étant illicite dans le but d'en obtenir le retrait ou d'en faire cesser la diffusion, alors qu'elle sait cette information inexacte, est puni d'une peine d'un an d'emprisonnement et de 15 000 € d'amende”

Très intéressant ! Une bonne raison de contester une plainte DMCA ?
A voir selon les domaines d'application de ces juridictions j'imagine...

Merci sebsauvage & Alec ن Archambault pour avoir relayé l'info

Interesting thoughts on web3, distributed infrastructure / trust, blockchains, NFTs...

internet’s 90-9-1 rule, which is a simple rule of thumb to approximate the number of contributors in internet societies. It basically says that 90% of users in a system are passive consumers of content and don’t post or write almost at all, 9% are sporadic contributors, while 1% are power users and creators.

Au lieu t’occuper de ton profile sur Twitter, occupe-toi de ton site.
Poste sur ton site plutôt que sur Twitter ou Linkedin.
Capitalise dessus, construis-le jour après jour, semaine après semaine, année après année.
À la fin, je pense que tu seras content de ce que tu auras crées.
En plus de ça, tu ne participeras pas au business d’entreprises peu éthiques.
Le web fonctionne de la même manière qu’il y a 20 ans, tu peux faire un site web de la même manière.
C’est juste que plus personne n’en fait.
La liberté est là. Il suffit de l’utiliser.

Une analyse détaillée de votre connexion Internet, utile pour détecter une coupure ou une baisse de débit du réseau

Rendre la justice est une fonction régalienne. Les fonctions régaliennes sont des tâches que l'État ne doit pas, ou ne peut pas, déléguer à des sociétés privées. La loi Avia fait le contraire. Voilà mon résumé à moi.

Source : le blog de Framasoft

La proposition de loi sur le site de l'assemblée nationale : http://www.assemblee-nationale.fr/dyn/15/dossiers/alt/lutte_contre_haine_internet

L'alerte levée par la Quadrature du Net : https://www.laquadrature.net/2020/05/11/vote-final-de-la-loi-haine/

Let me tell you about the still-not-defunct real-time log processing pipeline we built at my now-defunct last job. It handled logs from a large number of embedded devices that our ISP operated [...] Eventually our team's log processing system evolved to become the primary monitoring and alerting infrastructure for our ISP.

you mostly get told that you shouldn't be using unstructured logs anyway, you should be using event streams.
That advice is not wrong, but it's incomplete.

There's a file called /dev/kmsg which, if you write to it, produces messages into the kernel's buffer. Let's do that! For all our messages!

RAM is even more volatile than disk, and you have to reboot after a kernel panic. So the RAM is gone, right? Well, no. Sort of. Not exactly.

have the client to stream logs to the server. This is possible using HTTP POST and Chunked encoding,

The log uploader uses a backoff timer so that if it's been trying to upload for a while, it uploads less often. However, the backoff timer was limited to no more than the usual inter-upload interval.

Someone probably told you that log messages are too slow, or too big, or too hard to read, or too hard to use, or you should use them while debugging and then delete them. All those people were living in the past and they didn't have a fancy log pipeline. Computers are really, really fast now. Storage is really, really cheap.

How much are you paying for someone to run some bloaty full-text indexer on all your logs, to save a few milliseconds per grep?

EvE online is also home to a expansive world map to hold all of these players. At its peak EvE had 63,000 players online in a single world with 500,000 paying subscriptions on top, and while that number is getting lower by the year the world remains infamously large. Meaning that to get from one side to another is a sizable amount of time (and risk due to player owned factions).

You travel to different areas using warping (within the same system) or jumping to different systems using a jump gate

What would a EvE online internet of systems look like?

Ben je trouve ça super romantique comme histoire :)

A brief run through of using TiddlyWiki with Beaker Browser, the new browser with decentralised, peer-to-peer site hosting.

A very clear explanation of the #uploadfilters & #linktax law proposals, by member of the Pirate Party & the EU parliament Julia Red, who "decipher the legalese"

A big THANK YOU to her and her colleagues for their work on this.
Thanks to them, this law has been sent back to the drawing board: https://twitter.com/Senficon/status/1014814460488413185

Des serveurs d’Amazon jusqu’aux machines rouges installées directement chez les fournisseurs d’accès à internet, la firme a créé au fil des années un système complexe, mais d’une efficacité redoutable, le tout à un prix très raisonnable qui lui donne un avantage concurrentiel évident.

Auditing software is hard! The most-heavily scrutinized smart contract in history had a small bug that nobody noticed — that is, until someone did notice it, and used it to steal fifty million dollars.

you’re trusting in the software (and your ability to defend yourself in a software-driven world), instead of trusting other people.

Another example: the purported advantages for a voting system in a weakly-governed country. [...] is your Afghan villager going to download the blockchain from a broadcast node and decrypt the Merkle root from his Linux command line to independently verify that his vote has been counted? Or will he rely on the mobile app of a trusted third party — like the nonprofit or open-source consortium administering the election or providing the software?

Blockchain systems are supposed to be more trustworthy, but in fact they are the least trustworthy systems in the world. Today, in less than a decade, three successive top bitcoin exchanges have been hacked

you’ll rely on one of four things [...] : either the author of the smart contract is someone you know of and trust, the seller of the e-book has a reputation to uphold, you or friends of yours have bought e-books from this seller in the past successfully, or you’re just willing to hope that this person will deal fairly. In each case, even if the transaction is effectuated via a smart contract, in practice you’re relying on trust of a counterparty or middleman

Projects based on the elimination of trust have failed to capture customers’ interest because trust is actually so damn valuable.

Instead of directing resources to the elimination of trust, we should direct our resources to the creation of trust—whether we use a long series of sequentially hashed files as our storage medium or not.

A week ago, I didn’t even know .dev was a real gTLD. Historically it’s just been the realm of programmers who need a fake domain for testing. The domain never really existed, we just told our computers to pretend it does.
But the .dev gTLD does exist. And guess who owns it?
That’s right.
It’s Google.
Suddenly, it all makes sense. Who can decide to make an entire TLD secure?

Aux USA l’espionnage des citoyens vient de prendre un level (si, si, c'est possible) avec la loi CLOUD

FROM: https://twitter.com/sam_et_max

I found that it was all Indian IPs and blocked half of country at firewall level. All was well. I could go to sleep. But then suddenly someone messaged me and said why don't I let him use WhatsApp. Then 100 users started messaging me. Then 1000s. My Facebook was blowing up. I was now thinking I was under the most sophisticated attack ever on a personal level.

So instead of banning the entire country via firewall or a "fatal error" message I created this message and asked users to follow @browserling and tweet messages about it. TAIWAN NUMBER ONE! COMPETITORS NUMBER NINE!

It turns out users in India can't easily make online USD purchases with credit or debit cards as it requires a special bank permission.

I got to work and over last two weeks I built a "WhatsApp over Browserling for India in an old browser on a $20 Jio Phone".

While I was working on Indian version, the word spread to Cameroon and Nigeria where people also use cheap phones that can't run Whatsapp or other software, because government blocked access to Facebook, Twitter and other websites.

The TDLR: is a bill written under the guise of stopping sex trafficking, has stripped away the protection of section 230 of the Communications act of 1934 which means companies that run web services will soon be responsible for the actions of their users, even if they are unaware of them, to the point of criminal charges that could result in up to 25 years in prison.

Dans la lignée de PIPA/SOPA :(

Apparemment une directive européenne dans la même veine est en train d'être validée "Copyright in the Digital Single Market" : https://blog.github.com/2018-03-14-eu-proposal-upload-filters-code/

Cela a déjà été dénoncé par l'April en 2016: https://www.april.org/europe-une-surcouche-de-regles-retrogrades-en-guise-de-reforme-du-droit-d-auteur

Voici un bilan récent (février 2018) sur le blog de l'EFF : https://www.eff.org/deeplinks/2018/02/how-have-europes-upload-filtering-and-link-tax-plans-changed

Une explication détaillée de l'eurodéputée Julia Reda: https://juliareda.eu/eu-copyright-reform/censorship-machines/