fidzu : geeks

"The torrent they got the music from was just called like 123456.mp3."

19 Jan 2021 2:00pm GMT

Ankara has imposed advertising bans on Twitter, Periscope and Pinterest after they failed to appoint local representatives in Turkey under a new social media law, according to decisions published on Tuesday. From a report: Under the law, which critics say stifles dissent, social media companies that do not appoint such representatives are liable for a series of penalties, including the latest move by the Information and Communication Technologies Authority (BTK). The law allows authorities to remove content from platforms, rather than blocking access as they did in the past. It has caused concern as people turn more to online platforms after Ankara tightened its grip on mainstream media. The latest decisions in the country's Official Gazette said the advertising bans went into effect from Tuesday. Twitter, its live-streaming app Periscope, and image sharing app Pinterest were not immediately available to comment.

Read more of this story at Slashdot.

19 Jan 2021 2:00pm GMT

This sequel's lack of ambition will likely reinforce your murderous bias.

19 Jan 2021 1:00pm GMT

The Intercept's Nikita Mazurov warns that Zoom has digital watermarks that could expose sources working with journalists or government officials. An anonymous reader shares an excerpt from the report: Many users may not realize it, but Zoom has the capability to insert both video and audio watermarks into a meeting. The video watermarks are readily perceptible to meeting participants. When enabled, the video watermarking feature superimposes the username portion of each participant's email address over the content they are viewing when another participant shares their screen and places the same watermark over the current active speaker. Because the video watermark appears across the entirety of the video frame, blurring may adversely impact the visibility of the underlying material. In contrast, the audio watermarks are not readily perceptible to casual listeners, though they are what in watermarking parlance is known as "overt." That means the fact that they are embedded is easily discerned by meeting participants: When a Zoom meeting has the audio watermark, or what Zoom also calls the "audio signature," feature enabled, the meeting will have a green circular icon with a sound wave and a padlock at the top left of the frame next to the encryption icon. It is not immediately apparent at what point Zoom injects its "ultrasonic" audio watermark into the audio stream -- whether this happens only if a meeting attendee presses the Record button in Zoom or if the audio stream is watermarked prior to that point. Nonetheless, when recording a Zoom meeting, it is best to avoid using Zoom's built-in recording option and to capture the meeting using a third-party audio/video recorder. Zoom mentions that in order to identify the participant who recorded the meeting, they need at least two minutes of audio from the meeting, though it stands to reason that shorter snippets may also be identifiable if they happen to contain the audio watermark. Journalists should also be wary of publishing raw audio leaked from Zoom meetings, particularly if the source is not sure whether audio watermarking was enabled or not. Aside from Zoom's own watermarks, a number of elements appearing on an individual's own device may inadvertently give away the identity of the person who is recording. If the meeting video is being recorded either via screen recording software or a camera, there are a number of elements to watch out for...

Read more of this story at Slashdot.

19 Jan 2021 1:00pm GMT

Wine 6.0 has been released today and contains over 8,300 changes, according to its full release notes. Windows Central reports: The new release of version 6.0 has thousands of changes, but Wine's website highlights some of the biggest improvements: Core modules in PE format; Vulkan backend for WineD3D; DirectShow and Media Foundation support; and Text console redesign. The full release notes for Wine 6.0 explain that the core DLLs, which include NTDLL, KERNEL32, GDI32, and USER32 are now built in the Portable Executable (PE) format. As a result, people should see improvements for certain copy protection schemes. The update also includes a new mechanism to associate a Unix library with the PE module. This change makes it so systems can call Unix libraries from PE when trying to perform a function that can't be handled by Win32 APIs. Wine 6.0 also includes an experimental Vulkan rendered that translates Direct3D shaders to SPIR-V shaders. In another change related to Direct3D, the Direct3D graphics card database now recognizes more graphics cards and includes updated driver versions.

Read more of this story at Slashdot.

19 Jan 2021 10:00am GMT

We round up the Wi-FI 6E routers, with Asus' model launching as soon as this month.

18 Jan 2021 11:51pm GMT

Well, it's hanging on in there, but why didn't it conquer the world?

Analysis Does European Commissioner for Competition Margrethe Vestager's team pay close attention to the tech news? If not, perhaps they should.…

19 Oct 2016 10:24am GMT

Linus Torvalds teaches devs a lesson with early rc1 release

Google may have killed off its modular smartphone Project Ara idea, but some of the code that would have made it happen looks like coming to the Linux Kernel.…

17 Oct 2016 6:58am GMT

Your weekly Windows entertainment large and small

This week's worldwide BSOD roundup starts with what looks to your writer like a virtualisation launch bug. Submitter Alexander tells us it came from Peterborough Station, in Cambridgeshire.…

17 Oct 2016 6:28am 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

"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

Many of you have commented that our NewsVac section hasn't been refreshed since the middle of last month. Others have noticed that our story volume has dropped off. Changes are coming to Linux.com, and until they arrive, you won't see any new stories on the site.

01 Jan 2009 2:00pm GMT

The free and open source software community has been waiting for the G1 cell phone since it was first announced in July. Source code for Google's Android mobile platform has been available, but the G1 marks its commercial debut. It's clearly a good device, but is it what Linux boosters and FOSS advocates have long been anticipating?

31 Dec 2008 2:00pm GMT

Many public administrations already use open source Geographic Information Systems (GIS) to let citizens look at public geographic data trough dedicated Web sites. Others use the same software to partially open the data gathering process: they let citizens directly add geographic information to the official, high-quality GIS databases by drawing or clicking on digital maps.

30 Dec 2008 2:00pm GMT