fidzu : computers

Blue Origin, the rocket and space tourism company founded by Jeff Bezos, is proposing a massive new commercial space station called "Orbital Reef" that could be used to host science experiments, vacation getaways, and potentially even in-space manufacturing. CNN reports: The company plans to work alongside startup Sierra Space to bring the space station to fruition, and Boeing plans to design a research module on the station, though there are no guarantees the companies can make it happen. Such projects are still exorbitantly expensive and risky, likely costing in the tens of billions of dollars and requiring multiple safe launches before a human ever even floats aboard. Blue Origin and Sierra Space plan to co-finance the space station, though executives declined to give an all-in cost estimate during a press conference Monday. They did add that they are expecting to sign on NASA as an anchor tenant, though it's not exactly clear how such a partnership could take shape. Blue Origin hopes Orbital Reef could be operational in the late 2020s, though it will have to get quite a bit done to make that happen. The company has only managed a few crewed suborbital flights so far, much like NASA first achieved back in the early 1960s, and it has yet to put a spacecraft in orbit, let alone a person. A space station would take a major leap. New Glenn, the Blue Origin-built rocket that is expected to be powerful and large enough to haul the biggest portions of the space station to orbit, is not yet operational, and its maiden flight was recently delayed to at least late 2022. The orbital reef will be able to host up to 10 people and will have roughly the same internal volume as the ISS.

Read more of this story at Slashdot.

27 Oct 2021 7:00am GMT

An anonymous reader quotes a report from The Conversation: On October 23, 2001, Apple released the iPod -- a portable media player that promised to overshadow the clunky design and low storage capacity of MP3 players introduced in the mid-1990s. The iPod boasted the ability to "hold 1,000 songs in your pocket". Its personalized listening format revolutionized the way we consume music. And with more than 400 million units sold since its release, there's no doubt it was a success. Yet, two decades later, the digital music landscape continues to rapidly evolve. The iPod expanded listening beyond the constraints of the home stereo system, allowing the user to plug into not only their headphones, but also their car radio, their computer at work, or their hi-fi system at home. It made it easier to entwine these disparate spaces into a single personalized soundtrack throughout the day. [...] The rise of touchscreen smartphones ultimately led to the iPod's downfall. Interestingly, the music app on the original iPhone was called "iPod." The iPod's functions were essentially reappropriated and absorbed into the iPhone. The iPhone was a flexible and multifunctional device: an iPod, a phone and an internet communicator all in one -- a computer in your pocket. And by making the development tools for their products freely available, Apple and Google allowed third-party developers to create apps for their new platforms in the thousands. As of this year, mobile devices are responsible for 54.8% of web traffic worldwide. And while music piracy still exists, its influence has been significantly reduced by the arrival of streaming services such as Spotify and YouTube. These platforms have had a profound effect on how we engage with music as active and passive listeners. Spotify supports an online community-based approach to music sharing, with curated playlists. [...] As of February this year, more than 60,000 tracks were being uploaded to Spotify each day. The experience of listening to music will become increasingly immersive with time, and we'll only find more ways to seamlessly integrate it into our lives.

Read more of this story at Slashdot.

27 Oct 2021 3:30am GMT

"If the cops and the bounty hunters don't get you, the Syndicate will."

27 Oct 2021 2:12am GMT

A top U.S. bank regulator said U.S. officials are looking to provide a clearer path for banks and their clients that are looking to hold cryptocurrencies, in order to keep control over the fast-developing asset. Reuters reports: Jelena McWilliams, who chairs the Federal Deposit Insurance Corporation, told Reuters in an interview on Monday that a team of U.S. bank regulators is trying to provide a roadmap for banks to engage with crypto assets. That could include clearer rules over holding cryptocurrency in custody to facilitate client trading, using them as collateral for loans, or even holding them on their balance sheets like more traditional assets. "I think that we need to allow banks in this space, while appropriately managing and mitigating risk," she said in an interview on the sidelines of a fintech conference. "If we don't bring this activity inside the banks, it is going to develop outside of the banks. ... The federal regulators won't be able to regulate it." McWilliams' comments provide the fullest picture yet of what regulators are exploring as part of a cryptocurrency "sprint" team first announced in May. The goal of the team was to ensure cryptocurrency policy coordination among the three main U.S. bank regulators - FDIC, Federal Reserve and Office of the Comptroller of the Currency.

Read more of this story at Slashdot.

27 Oct 2021 1:40am GMT

"Better than Wii U" is faint praise for underwhelming emulation performance.

27 Oct 2021 12:08am GMT

Space junk may look like a supernova as SETI researchers struggle with a signal.

26 Oct 2021 11:14pm GMT

It's Wednesday, which means another Deck of Cards workout, the fun yet challenging segment of our group exercise program, The Lifehacker Workout. More »

10 Nov 2011 1:15am GMT

Readers offer their best tips for previewing your iPad home screen from another app, troubleshooting your friends and family's computers from far away, and accessing Google Tasks in the new Gmail layout. More »

10 Nov 2011 1:00am GMT

Facebook recently changed its layout, no longer allowing you to choose between "top stories" and "most recent" stories. Due to user outcry, however, they announced today that they'll be changing it back, though you might not notice it at first. Here's how it works. More »

10 Nov 2011 12:30am GMT

To anyone who has been reading anything on the web over the past few months, this shouldn't come as a surprise. Barnes & Noble is currently embroiled in a patent lawsuit started by Microsoft, after the bookseller/tablet maker refused to pay protection money to Redmond. Barnes & Noble has now openly said what we already knew, and has filed an official complaint at the US Department of Justice: Microsoft is engaging in anticompetitive practices.

09 Nov 2011 4:13pm GMT

Android, iOS good. BlackBerry and Windows out of luck

Lookout Mobile Security is going international with localised versions of its mobile security software and a partnership to pre-embed its technology in Android phones supplied by Telstra Australia, its first mobile telco partner outside the US.…

09 Nov 2011 4:01pm GMT

Thunar rather than later...

GNOME 3 has become something of a polarising moment for the popular Linux desktop. In chasing visions of tablets, touchscreens and the mythical "everyday user", the GNOME 3 Shell has left many Linux power users scratching their heads, wondering why the GNOME developers decided to fix a desktop that wasn't broken.…

09 Nov 2011 11:00am GMT

No permanent fix for TrueType strike gripe

November marked a light Patch Tuesday with just four bulletins, only one of which tackles a critical flaw.…

09 Nov 2011 10:41am GMT

http://gkppondokmelati.org defaced by Arakloverz

09 Nov 2011 7:01am GMT

http://www.gentapublishing.com defaced by Arakloverz

09 Nov 2011 6:42am GMT

http://gagap.net defaced by Arakloverz

09 Nov 2011 6:42am GMT

"Sources close to Adobe that have been briefed on the company's future development plans have revealed this forthcoming announcement to ZDNet: Our future work with Flash on mobile devices will be focused on enabling Flash developers to package native apps with Adobe AIR for all the major app stores. We will no longer adapt Flash Player for mobile devices to new browser, OS version or device configurations.. . ."

09 Nov 2011 6:34am GMT

"The following are major features for Fedora 16: enhanced cloud support including Aeolus Conductor, Condor Cloud, HekaFS, OpenStack and pacemaker-cloud; KDE Plasma workspaces 4.7; GNOME 3.2; a number of core system improvements including GRUB 2 and the removal of HAL; an updated libvirtd, trusted boot, guest inspection, virtual lock manager and a pvops based kernel for Xen all improve virtualization support."

08 Nov 2011 10:45pm GMT

Tyrs is a microblogging client, supporting Twitter and Status.net (identi.ca), it's based on console using the NCurses module from Python. The release of the 0.5.0 version is a good excuse to introduce Tyrs. Tyrs aims to get a good interaction with a fairly intuitive interface that can provide support ncurses. Tyrs tries also not to [...]

06 Nov 2011 9:43pm GMT

After one year of managing a network of 10 servers with Cfengine I'm currently building two clusters of 50 servers with Puppet (which I'm using for the first time), and have various notes to share. With my experience I had a feeling Cfengine just isn't right for this project, and didn't consider it seriously. These servers are all running Debian GNU/Linux and Puppet felt natural because of the good Debian integration, and the number of users whom also produced a lot of resources. Chef was out of the picture soon because of the scary architecture; CouchDB, Solr and RabbitMQ... coming from Cfengine this seemed like a bad joke. You probably need to hire a Ruby developer when it breaks. Puppet is somewhat better in this regard.

Puppet master needs Ruby, and has a built-in file server using WEBrick. My first disappointment with Puppet was WEBrick. Though PuppetLabs claim you can scale it up to 20 servers, that proved way off, the built-in server has problems serving as little as 5 agents/servers, and you get to see many dropped connections and failed catalog transfers. I was forced to switch to Mongrel and Nginx as frontend very early in the project, on both clusters. This method works much better (even though Apache+Passenger is the recommended method now from PuppetLabs), and it's not a huge complication compared to WEBrick (and Cfengine which doesn't make you jump through any hoops). Part of the reason for this failure is my pull interval, which is 5 minutes with a random sleep time of up to 3 minutes to avoid harmonics (which is still a high occurrence with these intervals and WEBrick fails miserably). In production a customer can not wait on 30/45 minute pull intervals to get his IP address whitelisted for a service, or some other mundane task, it must happen within 10 minutes... but I'll come to these kind of unrealistic ideas a little later.

Unlike the Cfengine article I have no bootstrapping notes, and no code/modules to share. By default the fresh started puppet agent will look for a host called "puppet" and pull in what ever you defined to bootstrap servers in your manifests. As for modules, I wrote a ton of code and though I'd like to share it, my employer owns it. But unlike Cfengine v3 there's a lot of resources out there for Puppet which can teach you everything you need to know, so I don't feel obligated to even ask.

Interesting enough, published modules would not help you get your job done. You will have to write your own, and your team members will have to learn how to use your modules, which also means writing a lot of documentation. Maybe my biggest disappointment is getting disillusioned by most Puppet advocates and DevOps prophets. I found articles and modules most of them write, and experiences they share have nothing to do with the real world. It's like they host servers in a magical land where everything is done in one way and all servers are identical. Hosting big websites and their apps is a much, much different affair.

Every customer does things differently, and I had to write custom modules for each of them. Just between these two clusters a module managing Apache is different, and you can abstract your code a lot but you reach a point where you simply can't push it any more. Or if you can, you create a mess that is unusable by your team members, and I'm trying to make their jobs better not make them miserable. One customer uses an Isilon NAS, the other has a content distribution network, one uses Nginx as a frontend, other has chrooted web servers, one writes logs to a NFS, other to a Syslog cluster... Now imagine this on a scale with 2,000 customers and 3 times the servers and most of the published infrastructure design guidelines become laughable. Instead you find your self implementing custom solutions, and inventing your own rules, best that you can...

I'm ultimately here to tell you that the projects are in a better state then they would be with the usual cluster management policy. My best moment was an e-mail from a team member saying "I read the code, I now understand it [Puppet]. This is fucking awesome!". I knew at that moment I managed to build something good (or good enough), despite the shortcomings I found, and with nothing more than using PuppetLabs resources. Actually, that is not completely honest. Because I did buy and read the book Pro Puppet which contains an excellent chapter on using Git for collaboration on modules between sysadmins and developers, with proper implementation of development, testing and production (Puppet)environments.

05 Nov 2011 11:17pm GMT

Creating json is now ten times easier.

05 Nov 2011 3:10am GMT