rxlim

Yes, precisely like Facebook "Internet" is worse than nothing. Things like these will bite us in the ass in the future, better to stop it as soon as possible.

After some research I'm now able to provide an answer to my own question.

The canvas was partitoned into blocks of 10x10 pixels that was white until sold. You would make a payment for X number of blocks through 2Checkout or PayPal. After transferring the money, you would send an e-mail to Alex Tew with the image, coordinates of wanted blocks, URL and TITLE/ALT text. He would then confirm the payment and upload your banner within 48 hours.

So the entire operation was manual with orders placed by e-mail.

So it was like buying tickets online? if multiple people were interested in the same region, the one which payment went through first got the region? However, this must still have been chaotic once the interest started to rise as space would seem empty until the payment was confirmed, and others would try to buy in the meantime. I guess you would also just have to make a rough estimate on the design of your banner and just buy the space, no time to design it first.

I wonder how he got everything to fit as more and more space was sold and if it was a manual process? It must have been like playing Tetris on expert mode.

> I love the idea of an nearly always on and connected device.

My desktop computer is exactly that.

If this is really true, I might have to eat my own words.

The amount of work that goes into Devuan for pulling out systemd of Debian Jessie is clear evidence that what you are saying is not easily possible.

> Debian is already one of the few distributions that goes out of its way to provide support for non-systemd init systems.

How does this manifest itself in practice? I don't want to use systemd in Debian 9, what has been done so I can easily change to another init like runit?

In practice it's not possible because of so many (unecessary) dependencies on systemd.

systemd was just a symptom. Multiple developers that had been working on Debian for many years, left the project in that period for various of reasons.

Congratulations. The return of Firefox branding makes me feel nostalgic. I remember using Firefox 1.04 on Debian in the early 00's. This was in the golden age of Firefox, when every new release was an improvement and it was a lean non-bloated alternative to other browsers.

In the past Debian was considered to be one of the most stable Linux distributions available. Stability and quality was a priority above anything else. However, around 2014 something changed when systemd was forced into Debian in a way that would never have happened before the new generation of developers took over the project.

Maybe this is just something we have to get used to, young developers seems to value ease above quality and stability, this also explains the current flood of Electron apps.

I did run an older version of binwalk on the firmware image, but it was unable to unpack anything and only printed false positives. I have now tried the newest version and it's able to unpack everything and display a lot of information. The PE modules in UEFI seems to be signed as these signatures are found many times:

  Certificate in DER format (x509 v3)
  SHA256 hash constants, little endian

Very interesting to dig around in the firmware, I even found the boot splash image. Definitely a time sink, but fun.

Good points. I must admit that I have not contacted Gigabyte as my experience with such large companies tells me that I will only get elevated blood pressure and absolutely no usable answer.

My main concern is not if the BIOS is secure, I'm very sure it's full of security vulnerabilities like most other software I use, but I have decided to trust Gigabyte like I have decided to trust the developers who build the Linux distro I'm using in that they are not malicious and trying to steal my information. The packages in my Linux distro are signed, so I can verify that they have not been modified since they left the developers machine, but I can't do the same thing with the BIOS update and that's what makes me uncomfortable.

This kid has a bright future as a human fuzzer. After a few days something like this would probably happen:

Kid: OK Google, Could Jesus microwave a burrito so hot that he himself could not eat it?

Google Home: ? ?? ???

Google Home: Segmentation fault (core dumped)

Kid: OK Google, Please initiate bug bounty payout.

In 1998 I installed the NetBus server on computers in the computerlab at my school. I would then run the NetBus client on a computer in a secluded corner, and watch the reaction from people while I messed with their computer. The best reactions I got from randomly opening and closing the CD-tray. Good times.

At least for it to be exploited remotely. It can still be exploited locally.

For a system to be affected, both chipset and CPU have to support vPro. For example, a PC with Core i7-7700 CPU and H270 chipset is not affected because only the CPU has support for vPro, but a PC with Core i7-7700 CPU and Q270 chipset is affected because both CPU and chipset have support for vPro.

This is a post[0] from one of the project leaders:

However, I think we all agree we want the Thunderbird replacement to be a desktop client (plus other platforms like mobile), and based on web technologies, most importantly written in JavaScript.

But the title has now been changed and that is fine with me.

[0]https://mail.mozilla.org/pipermail/tb-planning/2017-April/00...

According to Cambridge Dictionary "in the works" has the following meaning:

  in the process of being planned or done

Thunderbird replacement is currently being planned, so I think it's correct.

I need to make much more research before I will convince anyone, but as a start I like the philosophy of Devuan very much.

I have moved many many servers from Debian to FreeBSD after the announcement of systemd, and this has been great, but I must agree with you that on the desktop it can be a little inadequate.

Just saw the video and must say that it has really sparked my interest in Devuan. I heard of Devuan when the fork was first announced but never gave it much notice, now is the first time I try to understand what it really is. It seems like Devuan is much more organized and well-thought than I imagined. This is music to my ears:

Devuan will do its best to stay minimal and abide to the UNIX philosophy of "doing one thing and doing it well". It will foster diversity and freedom of choice among all its components and will perceive itself not as an end product, but as a a process, a starting point for developers, a viable base for sysadmins and a stable tool for people who have enough experience with computers. Devuan will never compromise for more efficiency at the cost of the freedom of its users, rather than leave that and the responsibility for a secure setup to downstream developers.

I need to do much more research and of course testing, but Devuan could be light at the end of the tunnel.

I would really like to see s6 in Ubuntu, but sysvinit + OpenRC would also be fine.

I want software to be simple, well-engineered and lightweight. In my opinion systemd is the exact opposite of that. I think this page explains it well: http://suckless.org/sucks/systemd

In practice I have had many extremely frustrating problems with systemd including systems that suddenly became unbootable.

My biggest wish is Ubuntu (and Debian) switching from systemd to any other init system. I know that won't happen but I was asked and that's the only thing I want, whenever you like it or not.

I have been browsing the web without Javascript enabled since 2006. The worst is that once in a while you will click on a link to read some text, but arrive at a completely blank page. Many times this can be solved by disabling CSS for that page or using the Google cache, but it's still annoying.

I my view requiring Javascript just to display text or pictures is completely brain-dead, web "designers" that think this is a good idea should probably no be allowed to design anything. It also makes it hard for disabled people that rely on accessibility tools to use the web.

I don't expect "web apps" like a video player to work without Javascript, but basic things like reading text, viewing pictures or clicking on links should never depend on it.

I hope this change will result in fewer sites using Disqus, because I really hate that you have to enable Javascript just for reading comments.