62 stories

This is What a Standalone Apple Camera Might Look Like

1 Comment

Apple ProCam Concept Design

Concept designer Antonio De Rosa of ADR Studio has created what he believes is a route Apple might take if it were to design a standalone camera.

The fictional camera is called the “Apple ProCam,” and De Rosa tells PetaPixel that his design isn’t based on leaks or rumors because those don’t interest him. Instead, he says he likes to explore how Apple’s Technology Language could be applied to different objects.

“Apple has demonstrated with Apple Silicon that they gained the ‘Midas Touch’ lately and they are potentially able to outcome the problems in any market and I think that photography (also with AR/VR) and mobility, it’s something they will innovate on really soon,” he says.

What an Apple Camera Might Feature

Apple ProCam Concept Design

His design features 8K video capture capability, what he calls an “innovative” lens design thanks to what would be Apple’s own proprietary mount, Siri on-board, a touch and tiltable rear display, a “Magic Wheel” touchable command dial, and inkless-printing built-in, all powered by its M1 chip.

Apple ProCam Concept Design

Apple ProCam Concept Design

The built-in printing system would bridge digital and analog and allow for immediate enjoyment of photos taken with the ProCam.

“I had an experience designing the Polaroid Socialmatic a few years ago and I always thought the printed photography is not only a nostalgic operation,” he says. “Pictures resonate when you print them and to have a device that merges high-level optics and tech with a fast printing system could be something cool.”

Apple ProCam Concept Design

The shutter button is located on the front of the camera while the main command dial actually features a tiny circular touchable display. In use, it would show different camera modes but would also function as a way to activate Siri.

Apple ProCam Concept Design

Apple ProCam Concept Design

The idea that the camera would use a proprietary mount for its lenses, as well as printer packs for the photos, actually does sound like something Apple would do in order to support what would very likely be a closed system (which is typical for Apple products). The camera would also serve as the core of many accessories that both Apple and third parties could support, just as is the case with the iPhone.

A Unique Lens and Sensor System

Apple ProCam Concept Design

De Rosa shows two possible designs for the lens and sensor system. One is a much larger take on Apple’s current triple-camera rear system currently found on its smartphones, while the other is more akin to what is found on all other interchangeable lens cameras currently on the market. His design seems to indicate that these two front plates would be interchangeable, but it doesn’t seem particularly practical given the need for a different sensor arrangement for each.

Apple ProCam Concept Design

Based in History, but Probably Never to Be

Apple has dabbled in standalone photography equipment in the past. As noted by Cult of Mac, Apple actually worked with Fujifilm to produce the QuickTake 100 back in 1994. The 0.3-megapixel camera was a commercial flop and Apple hasn’t revisited the standalone camera market since making it very unlikely that Apple would go down this route since it already makes a camera it considers a professional shooter (it’s called the iPhone).

More from De Rosa can be found on the ADR Studio website and Instagram.

Image credits: All renders by Antonio De Rosa of ADR Studio.

Read the whole story
10 days ago
I don’t under this fetish
Share this story

An interview with 100 rabbits

1 Comment

Hundred Rabbits is an artistic duo hacking their way around the Pacific on their sailboat. I invited them to sit down for an interview to talk about about their lifestyle, art, philosophy, and their SourceHut projects. This interview was conducted live in the #sr.ht.watercooler IRC channel on Libera Chat.

Drew: Hi Devine! Happy birthday, Rek!

Rekka: Haha, thanks!

Devine waves

Drew: Would you two introduce yourselves?

Rekka: We are two artists who live and work on a sailboat named Pino. We traveled around the Pacific Ocean for 5 years, learning about technological resilience. I am an illustrator, but I also write, and Devine is a programmer that also makes music.

Drew: Why live at sea?

Devine: We don’t live at sea: we live on the water, near the coasts, and sometimes we traverse large spans of ocean. We chose to live on a boat so we could go where the wind would take us. We quickly look for shelter when we can and try to limit the time we spend at sea to a minimum.

Drew: That makes sense. The sea intimidates me, to be honest.

Devine: Us, too.

Drew: Have you found your boating lifestyle to be a good platform for the art projects you build?

Rekka: Yes, definitely. We find that we work really well with constraints.

Devine: A lot of our projects are advised by the extreme position in which we find ourselves, away from internet connectivity and one-day delivery networks.

Drew: Projects like?

Rekka: We’re always working on our wiki, it’s the project we update the most. We document everything we learn like food preservation, boat repairs, places we’ve been, etc.

Drew: I like that community-building mindset very much, Rek.

Devine: The energy we collect from the sun dictates the number of cycles our software can use to run, and how much time we can dedicate on working on the computer to build them. This has ruled out a lot of modern technologies, it’s also what brought us here, to be using SourceHut in the first place.

Drew: I imagine that the energy constraints are also why many of your projects involve stepping away from the computer, like food preservation and log-keeping.

Devine: If we can use less technology to solve any one task, we will. Our ideal amount of technologies is as little technology as possible.

Drew: You’ve led me to another question I wanted to ask: how does SourceHut fit into your workflow?

Devine: Our work is done almost entirely offline, but when we do have connectivity, we’re looking for building mirrors of our work for redundancy. As much as people like to throw the words “why don’t you self-host” at us, having someone making sure that our repos are available while we’re days or weeks away from shore is what keeps our projects alive and gives us peace of mind.

Drew: I cannot imagine a boat in the middle of the Pacific making for a good place to host a server. Did you try any other platforms before settling on SourceHut?

Rekka: We were on GitHub for a few years.

Drew: How does it compare?

Devine: It’s hard to put into words, there’s a general trend in software right now to compete for attention and skew people’s behavior to act in favor of large ecosystems. GitHub is heavily afflicted by that sickness. SourceHut, less so.

Drew: Sick of manipulative corporate behavior?

Devine: Yep, that’s the word I was looking for.

Drew: I admire the Rabbits for similar reasons: you have this down-to-earthness that I can connect with.

Drew: In more practical terms, do you find the lightweight approach to SourceHut’s UI design to be easier on your power and bandwidth constraints?

Devine: It’s worlds apart. Because we work entirely from donated second-hand devices, backward compatibility is more important to us at this point. In our eyes, better software is software that gets smaller over time, that sheds the superfluous, and that reaches further backward in time for that onto which it can run. SourceHut appealed to us instantly because there are so few examples of this willingness to reduce consumption in the wild.

Drew: I use a 12 year old laptop myself. I think it’s also important to recognize that the ability to recklessly consume is a privilege that not everyone has, and you’re locking out a lot of users by only designing for the latest and greatest. Even in FOSS, it can be a challenge to get people on board with that philosophy.

Devine: That’s definitely a big part of this. You can only call yourself anti-capitalistic for so long while also catering only to people with the latest gizmos.

Drew: On the subject of FOSS, why did you choose to release your software works as free (as in freedom) software, and your artistic works with Creative Commons?

Rekka: We don’t want our projects to die with us.

Devine: We can’t be there for people, we’re at sea for months at a time. The code has to speak for itself, be inspectable and repairable without our being there. We cannot sell our works as services, because we’re never there for people who might need our help fixing it.

Rekka: And things can happen at sea… as grim as it is to say that.

Devine: During every long passage we consider that we might have pushed our last commit, and is that the final state of this idea, possibly not. We like to think that someone might pick up our work where it was left.

Drew: That speaks to an admirable level of attentiveness to the needs of your users. And FOSS is a good way to cement your legacy.

Drew: May I ask what motivates your work? Why these projects? Why software as art? Why illustrations?

Rekka: The two of us like to create worlds. And art is a way is a way to do that.

Devine: Software is a way to make that world-building interactive and invite people into these worlds.

Drew: Do you view your work as having more of a performative or collaborative nature?

Devine: We obviously don’t share the same limitations as most. While I think people like our general philosophy, we will not convince Ubisoft to start making Dreamcast games. To most people, we’re exploring a fork in the road. The emulation scene constantly offers a reminder of what-if… what if Plan 9 had been picked up, what if Genera, what if… Art does this sort of exploration better than anything else. Our work is advised by our immediate limitations, but it’s visiting that fork in the road where 4K television did not actually made people happier. And watching Terry Davis work on TempleOS, that was performance to me, because there was no place in my reality to make any use of it.

Drew: Do you hope to offer the world something like that?

Devine: We work on small systems that people emulate on their M1.

Drew: For any readers who want to check out your work, or get involved themselves, where should I direct them?

Rekka: To our wiki, Dev’s website, or mine, or to git.sr.ht, where we host our projects.

Devine: We’ve been meaning to migrate to the new sourcehut pages, that’s what’s next.

Drew: Cool! Thanks for taking some time to chat with me. I’m very proud to host you on SourceHut, I’m a big fan myself.

Drew: Is there anything you wish I had asked or that we had discussed today?

Devine: Are you familiar with permacomputing? It’s a holistic approach to computing and sustainability inspired from permaculture.

Drew: No, tell me more.

Devine: Well, one thing that we’ve been thinking about is like… Fahrenheit 451 is a book about the world ending, and a handful of people take it upon themselves to preserve books they think have meaning. We often see folks echoing that computing causes more problems than it solves, and that what was once a tool of emancipation has been warped into a tool of control.

Devine: Are computers something we’d like to preserve going forward? How much is worth keeping? And so forth. This is what people consider when thinking about permacomputing. I don’t know the answer but it’s something interesting to explore. There isn’t a critical mass of folks thinking about these ideas right now, but we’re seeing more and more folks joining in the discussion.

You can read more about permacomputing here, and here.

Drew: I would like to see more thoughts on these lines, too. Hopefully we can signal boost that together and get some more brains involved.

Drew: Speaking of which: let’s open the floor to the rest of the channel?

Following the interview, we opened the IRC channel back up to general discussion for a while. Here are a few choice quotes from the ensuing chat:

alderwick: One thing I specifically wanted to say about 100r and SourceHut is that I wouldn’t have been able to contribute to Uxn if the repo was on GitHub. Like ddevault, I’m on old hardware. My laptop won’t load more than a few GitHub pages without crashing, but SourceHut is never a problem.

Devine: And without alderwick there would be no Uxn, I’m endlessly thankful that it made our meeting possible.

sigrid: Echoing alderwick here. GitHub doesn’t work on Plan 9 in Mothra. SourceHut does with no issues.

nihilazo: I like permacomputing as an idea but I struggle with it in a way because I’m required to use cloud services and such. I had to start using a more powerful laptop just to run MS Teams. Is there some way to reconcile trying to do permacomputing-y stuff with also working within a world that (currently) requires I use garbage?

Devine: There is no way to reconcile using MS Teams and permacomputing.

AWildThorp (later): What are your thoughts on cloud services with respect to permacomputing? I have mixed feelings about them in general. I kind of view them as buses vs cars, but on the other hand they can enable wastefulness

nihilazo: I understand that you can’t reconcile the two is there any way to contribute to permacomputing while still being trapped in systems antithetical to it?

Devine: Cloud services abstracts the waste from its users, I think until there’s more transparency they are antithetical to permacomputing, otherwise they could be an efficient tool to create some sort of permeance of information.

eletrotupi: nihilazo: I think you can and should contribute to permacomputing regardless of being trapped. Unless you are deliberating picking up antithetical services.

Devine agrees with eletrotupi

Drew: I think that most people aren’t trapped even if they feel so, too. You usually have a choice. For instance, you could seek out a different employer, or save up and start your own business. Positive steps in the right direction are almost always possible.

nihilazo: I am trapped by having to use Teams for college work, and I can’t really just switch colleges, given that they are the only college in the area.

Drew: You could start grassroots student organizations which try to tackle these issues. Throwing up your hands and saying it’s out of your control is not the best option. It takes people taking deliberate action to make changes in our society.

nihilazo: I agree on that point, I guess.

Anonymous: Was sailing a transformational experience led to permacomputing as a goal? And if so - can the lifestyle change required to avoid “MS Teams” be achieved without such a strong transformational experience?

Devine: We had to be put in an extreme situation to make that drastic a change. As an example, we were making iOS development when we cast off, thinking that we could do it along the way. Now it seems to naive to believe that modern technology can even survive being 15 nautical miles from the coast without it totally breaking down. But, we don’t think people have to be sailing to explore that space.

Rekka: Working from an older computer or from a shitty off-grid connection can help ;)

nihilazo: I’ve been very conscious of the potential power consumption of my computer use and trying to cut down but I am finding it difficult. I’m an internet addict, I guess. Especially things like video games, which are almost the very definition of pointless energy consumption.

Rekka: It’s difficult without actual constraints. If you are limited to the power in your batteries, say. You know your limits and it’s easy to limit usage.

kfx: I think it’s possible to separate those worlds. I use all kinds of unfortunate technology at work, and I don’t let it intrude on what I do for myself. Keeping those dividing lines sharp makes it easier to walk away from the gross stuff when the opportunity presents itself. Teams in fact was busily crashing my work computer about twenty minutes ago, but I kept reading this IRC discussion on my personal machine.

AWildThorp: On a similar note, if I go above my data limit on my smart phone, I have no bandwidth issues browsing the gemini space.

HamAdams: I’m really glad you all did this interview. I think this is putty some words to some general feelings I’ve been having recently regarding using technology more consciously.

Devine: Glad to hear :) The ComputingWithinLimit crew released a bunch of papers last year about this way of thinking about computers. The LIMITS2021 papers are excellent; I recommend having a look. They will put even more words to these thoughts.

Big thanks to the Rabbits for joining us for this interview! Please check out their cool projects. Orca is my personal favorite.

Read the whole story
38 days ago
Interesting interview with a group I knew nothing about.
Share this story

Why 'Eternals' Was The Worst-Reviewed Marvel Film

1 Comment
By Archie Grimm Published: December 05th, 2021
Read the whole story
41 days ago
Finally someone I can agree with.
Share this story

Dwayne Johnson Talks About Joining 007 Movies, Says He’s “Gotta Be Bond”

1 Comment

Dwayne Johnson is no stranger to action films. He’s starred in many, including Fast & Furious Presents: Hobbs & Shaw, the Jumanji series, and most recently, Red Notice. But he’s ready to step into one of the genre's most iconic roles: James Bond. In a recent interview with Esquire, the actor talked a bit about his grandfather’s role in You Only Live Twice and stepped forward to claim his own spot in the hit franchise.

Read the whole story
60 days ago
That would be one of the shittiest casting decisions ever, just saying
Share this story

SourceHut's third year

1 Share

Three years ago today, I announced that SourceHut would be making its alpha open to the general public after two years of development in private. Since then, in addition to moving across the Atlantic ocean, I have overseen the development of a service, and a business, which has grown to exceed all of my expectations. Today, SourceHut is home to 25,000 users, 5,000 projects, 42,000 git repos and 5,000 Mercurial repos. 153,000 emails have made their way to the 3,000 mailing lists hosted here, and 26,000 tickets have been filed across 5,000 bug trackers. Our CI system has completed 625,000 builds totalling 2½ years of continuous build time.

And so, despite its persistent “alpha” status, SourceHut has been a comfortable home to thousands of projects productively going about the business of building free software. I couldn’t be more proud of our work, or more thankful for the trust and support this community has offered us.

In return, what have we offered the FOSS community? Earlier this week, I asked the sr.ht-discuss mailing list to share some of their favorite projects on SourceHut. The favorites include a mobile client for itch.io, a multi-track audio editor reclaimed from the hostile takeover of Audacity, a hacker-first OpenStreetMap viewer, a user-first Medium frontend, and official mirrors of SourceWare projects like GCC and glibc, all of which are new to SourceHut this year. I also recently discovered that the French government’s new site for discovering French FOSS projects uses SourceHut as well. Check out the thread for more, or reply to add some of your own favorites!

SourceHut staff have also been hard at work contributing directly to free software again this year. As part of our free software consultancy, we have taken on projects like expanding OpenXR support on Linux, contributing to projects like the Linux kernel, Monado, Mesa, Xwayland, and more. We’re also responsible for the free software Wayland technology at the heart of Valve’s Steam Deck. We are also the release managers for Wayland and Weston, and maintainers for parts of the freedesktop and Alpine Linux infrastructure, and we became a Bronze supporter of OpenStreetMap this year.

Many new free software projects have also been developed and organized by our staff, including an IRC bouncer and webchat, a documentation site for Go, a new web browser based on NetSurf, and a project to develop a new programming language. Our forgeperf initiative has also turned our industry-leading focus on performance and accessibility into tangible improvements in GitLab and Codeberg. We will also be hiring a third engineer in February who will help us expand this work even more. In keeping with our tradition of transparency, the onboarding documents we prepared for them are available to the public.

And what of the forge itself? Our main focus this year has been on implementing our GraphQL API, which is now about halfway done. This is the main blocker for the SourceHut beta, and we have by now solved most of the unknowns and are working our way through the rote work of building out the remainder of the services. I’ll predict, for the third time, that we’ll complete the alpha and start the beta next year.

We’re comfortable taking our time to do this right, especially given that we’re quite able to provide a great deal of value to the FOSS community even during the alpha. Our definition of “alpha” has a specific meaning which differs from many other projects, specifically boiling down to meeting four important criteria:

  • Support for user groups/organizations
  • The development of a high-quality API which we can support indefinitely
  • Complete data autonomy, including import and export and account deletion
  • Comprehensive documentation for both hosted and self-hosting users

When we meet these criteria, we will have reached the necessary level of quality to ship a product we can be confident in for the long-term. However, we have already reached many important milestones which are uncharacteristic of many alpha-quality products. We’re committed to the longevity of user data, and we have many levels of redundant backups and monitoring. Our services are also extremely reliable, sporting better uptime than any of our competitors, including big fish like GitHub. Thousands of projects are already enjoying productive use of our services, and our goal is to provide them with a best-in-class product which far exceeds their expectations and industry norms.

In addition to this work in advancing the GraphQL APIs towards our ultimate ambitions of completing the alpha, we have also taken some time to develop additional products and foster a culture of shared community ownership over our services. We shipped pages.sr.ht this year, and we’re expecting to ship our hosted IRC services, chat.sr.ht, very soon. We’ve also continued to enjoy a great relationship with the Mercurial community, who are directly responsible for the maintenance of hg.sr.ht, in addition to the many volunteers representing their operating systems on builds.sr.ht. Members of our community are also working independently to develop names.sr.ht, which will eventually become a domain name registrar which uses git to store zone files and supports cool ideas like OpenNIC. We’re looking forward to involving the community even more in the coming years, as this is a key advantage of SourceHut’s FOSS design that many of our competitors lack — and works to the mutual benefit of SourceHut and the communities which rely on us. If you have a cool idea for SourceHut and you’re willing to write the code, we’re willing to provide you with support and resources to deploy it to.

With that, another year goes by, and the year ahead is full of work to do. I hope you’ll join our public Mumble meeting tomorrow to look back on our accomplishments, and look forward to the future. We’re meeting in the usual place, voice.mnus.de in the SourceHut room, at 10:00 UTC tomorrow, November 16th. Thank you for using SourceHut, and I hope we continue to serve you into the future.

What’s cooking on SourceHut?

Let’s quickly address the usual “what’s cooking” items before parting ways.


Write support for the todo.sr.ht GraphQL API was my main focus this month, but it has turned out to be pretty complicated. todo.sr.ht is one of the most complex sourcehut services — submitting a ticket requires parsing user mentions, fetching subscribers, creating ticket and event rows, fetching or referencing new participants, sending email notifications, and more. I hope to complete this next month.


Legacy Fedora images are being deprecated and removed next week. You will receive an email if this affects you. Thanks to Haowen Liu for taking over maintenance of the Fedora images, and to Timothée Floure for all of their hard work up to now.

apt-key has been deprecated in Debian upstream, and builds.sr.ht has been updated according to upstream recommendations. This is not expected to impact users.

We have stopped allocating a PTY for build logs. This may cause your build results to look less colorful, but should cause few problems otherwise.


  • openbsd/7.0 is now available
  • ubuntu/jammy is now available


pages.sr.ht now supports partially updating only a subdirectory of your sites, which makes it easier to do things like manage different subdirectories for different projects without having all of them necessarily being aware of the content of the entire site.

Read the whole story
61 days ago
Share this story

Microsoft to ‘sunset’ LinkedIn for China, and replace it with an app lacking social media features

1 Comment

Microsoft announced this morning that it’s shutting down the localized version of LinkedIn it offers in China. The move comes after increasing claims from academics and reporters that they’ve received notifications stating their profiles on the service are blocked in China, as reported recently by The Wall Street Journal.

In its blog post announcing the move and a plan to launch a new China-only standalone product called InJobs, Microsoft did not directly reference those reports. Instead, it says:

While we’ve found success in helping Chinese members find jobs and economic opportunity, we have not found that same level of success in the more social aspects of sharing and staying informed. We’re also facing a significantly more challenging...

Continue reading…

Read the whole story
94 days ago
I would like that very much
Share this story
Next Page of Stories