Language Selection

English French German Italian Portuguese Spanish

Open Hardware: Adafruit Feather and Stanford Doggo

Filed under
Hardware
OSS
  • Feather Plus Blackberry Equals Open Source Fauxberry

    The keyboard is a superior means of input, but to date no one has really figured out how to make a keyboard for small, handheld electronics. You could use tact switches, but that’s annoying, or you could use a touch screen. The best option we’ve seen is actually a Blackberry keyboard, and [arturo182] has the best example yet. It’s a small handheld device with a screen, keyboard, and WiFi that’s ready to do anything imaginable. Think of it as an Open Source Fauxberry. In any case, we want it.

    This project is actually a breakout board of sorts for the Adafruit Feather system, and therefore has support for WiFi, cellular, or pretty much any other networking of connectivity. To this blank canvas, [arturo] added an accelerator/magnetometer sensor, a single Neopixel, and of course the beautiful Blackberry keyboard. This keyboard is attached to an ATSAMD20G, a microcontroller with a whole bunch of I/O that translates key presses into I2C for the Feather.

  • Students from Stanford's Robotics Club Releases Open-Source Robo-Dog Online

    Robotics isn't cheap by any means, and no one knows this better than the students of the Extreme Mobility Team of Standford University's Robotics Club (SEMT). The materials used by university robotics clubs can cost upwards of tens of thousands of dollars, making it that much harder for many high schools and less well-funded colleges and universities to invest heavily in this important field of research.

  • Watch this open-source dog robot do backflips [Ed: This is more likely to be used in military rather than in aeronautics and astronautics (luxury of the rich)]

    “We’re hoping to provide a baseline system that anyone could build,” says Patrick Slade, graduate student in aeronautics and astronautics and mentor for Extreme Mobility.

  • Meet Doggo: Stanford’s cute open-source four-legged robot

    Doggo follows similar designs to other small quadrupedal robots, but what makes it unique is its low cost and accessibility. While comparable bots can cost tens of thousands of dollars, the creators of Doggo — Stanford’s Extreme Mobility lab — estimate its total cost to be less than $3,000. What’s more, the design is completely open source, meaning anyone can print off the plans and assemble a Doggo of their very own.

  • Stanford Students Built This Adorable, Bouncy, Open-Source Robot Dog

    Nearly all of the parts used to create Doggo were bought intact through the internet, while the rest can be easily 3D-printed. The total costs involved in building Doggo—including shipping and handling—amounted to less than $3,000, Kau and his team claim. Via the website Github, the team has also released all of the relevant information you would need to create your Doggo, including software coding, supply list, and manual instructions. From there, any enterprising roboticist could tweak the design to create an even more capable Doggo.

More in Tux Machines

KDE: Plasma Mobile at Plasma Sprint Valencia and GSoC Work

  • Plasma Mobile at Plasma Sprint Valencia

    In June month we gathered in Slimbook’s offices to work on Plasma. Along with Plasma developers, we were also joined by KDE Usability and Productivity team. During the sprint I mostly worked to create up-to-date image for Plasma Mobile, as from last few weeks Plasma Mobile image was quite out-of-date and needed update.

  • Somewhat Usable

    Adding a feature by yourself is a lot satisfying than requesting someone to add that for you, cause now you are both the producer and the consumer. But to be honest, I never thought I would be the one implementing the Magnetic Lasso for Krita when I requested it 4 years back, leave the fact that I even getting paid for doing so. So here are the first tests being done on it.

  • View and Examples

    This week I began learning about QML to try to fix the View that show the graphs and tools for manipulating graphs.

  • Month 2 in making the Titler – GSoC ’19

    From my understanding so far (forgive me for any mistakes that I might make – it’s a different codebase and different concepts – I wholeheartedly welcome corrections and suggestions) the whole producer boils down to two parts – the actual producer code (which is in C and which is the thing which does the ‘producer stuff’) and the wrapper code (which ‘wraps’, supplements and does the actual rendering part of the QML frames). The wrapper files are responsible for mainly rendering the QML templates that are passed to it and make it available for the actual producer to use. And consequently, most of the work is to be done in the wrapper files, as the producer in itself doesn’t change much as it will still do the same things like the existing XML producer (producer_kdenlivetitle.c) – such as loading a file, generating a frame, calling rendering methods from the wrapper files.

System administrator responsibilities: 9 critical tasks

System administrators are critical to the reliable and successful operation of an organization and its network operations center and data center. A sysadmin must have expertise with the system's underlying platform (i.e., Windows, Linux) as well as be familiar with multiple areas including networking, backup, data restoration, IT security, database operations, middleware basics, load balancing, and more. Sysadmin tasks are not limited to server management, maintenance, and repair, but also any functions that support a smoothly running production environment with minimal (or no) complaints from customers and end users. Although sysadmins have a seemingly endless list of responsibilities, some are more critical than others. If you work in a sysadmin role (or hope to one day), make sure you are ready to follow these best practices. Read more

Fedora, CNCF and IBM-Paid Puff Pieces

  • Changing how we work

    As those of you who read the https://communityblog.fedoraproject.org/state-of-the-community-platform-engineering-team/ blog know, we are looking at changing workflows and organization around in the Community Platform Engineering team (of which, I am a member). So, I thought I would share a few thoughts from my perspective and hopefully enlighten the community more on why we are changing things and what that might look like.

  • Kubernetes policy project takes enterprise IT by storm

    An open source compliance as code project has gained a groundswell of popularity over the last six months among enterprise IT pros, who say it simplifies and standardizes Kubernetes policy management. The Open Policy Agent (OPA), an open source compliance as code project founded by former VMware employees, was used at Netflix as early as 2017 and accepted into the Cloud Native Computing Foundation (CNCF) as a sandbox project in March 2018. Netflix gave an OPA demonstration at KubeCon in December 2017, and Intuit and Capital One followed at KubeCon in December 2018. After the project advanced to the CNCF's incubating stage in April 2019, and was demonstrated a third time at KubeCon EU in May 2019, it began to generate mainstream buzz. [...] As Kubernetes environments grow to encompass Istio service mesh and Knative event-based orchestration in what Google calls the open cloud stack, the fact that OPA lends itself to Kubernetes policy enforcement but can expand to include those adjacent utilities boosts its appeal.

  • The Who, What, Where, When, and Why for Mainframe Security [Ed: IBM pays Ponemon for puff pieces]

    For most people, security is a bit of a nuisance. No-one likes having to keep updating their password and then needing to remember the new one. And then there’s all the different passwords that need to be remembered for different things. It all just seems like an administrative nightmare. It just makes getting a day’s work done harder. That’s what most users think right up until the moment there’s a breach. And suddenly the mood has changed. Now everyone wants to know exactly what’s happened. They want to know who has done what, where they’ve done it, when it occurred, how they got in, and a million other questions. Your phone is ringing off the hook. Your e-mail is filling up faster than usual. What can you do? Where can you access the information you need? How do you respond to the incident?

Some Interesting Features In VLC and Typical FUD From Bogdan Popa

  • Some Interesting Features In VLC!

    VLC is one of the best video and audio player applications that are open source. We can install this application on various existing operating systems such as Linux, MAC, Windows, and also Android.

  • Critical Flaw in VLC Media Player Discovered by German Cybersecurity Agency [Ed: Will dedicated Microsoft propagandists like Bogdan Popa also write about NSA back doors in Windows or always just focus on smearing FOSS security? There are security bugs found every day, but back doors are an actual conspiracy; yet corporate media sponsored by the conspirators likes to deflect all blame to those who find/exploit these back doors.]

    A critical security flaw in VLC Media Player has recently been discovered by German cybersecurity watchdog CERT-Bund, who warns that a successful attack would allow for remote code execution. The vulnerability exists in VLC Media Player version 3.0.7.1, according to the official CVE-2019-13615, which is the latest stable release of the application.