That will work as long as EF lenses are still available… But Canon already took some lenses out of production.
So basically, that’s gonna be a dead end path.
Mastodon: @SuitedUpDev@mastodon.online
That will work as long as EF lenses are still available… But Canon already took some lenses out of production.
So basically, that’s gonna be a dead end path.
As a current Canon photographer (700D owner) going mirrorless is definitely the future. Canon and Nikon have basically given up on DSLRs. (https://www.engadget.com/why-nikon-and-canon-have-given-up-on-dsl-rs-133042286.html).
However, I want to highly stress out to avoid Canon for mirrorless. The reason behind it is that Canon has been “defending” their mirrorless mount relentlessly. Meaning, that no other 3rd parties without Canon’s blessing can make lenses for the RF mount. (Source: https://petapixel.com/2022/09/06/canon-confirms-its-going-after-lens-makers-for-patent-infringement/)
So unless you wanna spend big bucks on Canon approved lenses, I’d go with either Nikon, Sony or one of the other mirrorless brands.
Fun fact, Sony is actually quite permissive in the licensing of their E mount. So they will basically let everyone make lenses for the E-mount.
Debian Woody > Red Hat 7.0 > Slackware 9.0 > Slackware 10 > Debian > Ubuntu > Mac OS > Ubuntu > Arch.
At least for desktops and laptops.
For servers I’m still primarily running Debian (and one instance I’m running Arch).
The reason why I settled on Arch is primarily because the combination of bleeding edge and being stable enough for daily driving it. The AUR also adds sooo much, that there is nothing I really don’t need to manually install anymore.
For servers, I basically want a rock stable system. Hence why I’ve chosen Debian Stable.
For all the oldies in the room, Lindows / Linspire (me included)
Trying to merge Wine with Linux into one ““convenient”” package was overselling it at best and worst a lie. Back in '08 / '09 I tried to run it, just to see how good (or bad) it was. It was basically Debian with KDE and their special sauce on top to ““easily”” run Windows binaries. Especially in those day, WINE wasn’t as good as it is today. I think you can fill in the rest ;-)
I wish I could give you more upvotes because you deserve all the upvotes
I’ve tested it with the jellyfish test files, IIRC it can easily transcode the 120Mbits per second 4k video to 1080p!
I have an A380 running in my home server which runs Arch Linux with kernel version 6.4.6. I’ve had the card since since October 2022, so I’ve seen my share of “issues” with it, especially because my Jellyfin server runs inside of Docker and thus adds additional layer of complexity / things that can go wrong.
Having said that, for $120, BUY IT. It’s seriously one of the better cards are out there at that price. Previously I had an RX 550 (for which I paid about €75) and the A380 runs circles around my old RX550.
When I initially got it, I had some issues with is. Not surprising, early adopter and all. But the drivers are pretty rock stable nowadays and new features are being added constantly. The latest release of the Intel Media Driver added support for encoding HEVC 422 and improved performance for HDR tone mapping.
With regards to maximum streams, I am currently able to get a transcoding limit of 4 streams from H265 10bit (1080p) to H264 and still have some horsepower left over.
It’s even so stable and pleasant to use, I am genuinely considering getting an A750 for my desktop.
Edit: typing hard yo.
You mean something like RCS?
As a fellow Dutchy… my current place is the first place I ever lived in that came with a combination oven and microwave.
Previously I’ve always had to supply my own microwave / oven ;-)
Oh this guy is my inner spirit nerd.
Same…
Usually it isn’t hard to implement…but that largely depends on the backend.
Might take a crack at this, this weekend.
Feels like that solves itself then as more people see those tags. Just ban these when it pops up and look for those. Reddits never been had issues with someone confusing u/spez with u/spezz or u/speez day old accounts.
Yeah exactly, it’s definitely something that will solve itself. The moment, more people are familiar with the interface, the less impact it will have.
Make sure to check the issues/PRs, it looks like people already worked on CTRL+Enter.
Oh damn! That’s nice! But that means I have to find another thing to do :P
On the frontend, it’s primarily React and Bootstrap. I do have some experience with React (with TypeScript), so that’s good! And Bootstrap, that has been a few years…
Hahah… Shit, now you got me intrigued… xD
Yesterday I was annoyed at wide code blocks being wrapped, instead of having a horizontal scrollbar, so I took 20 minutes of googling and hacking around with my minimal css skills and wrote a PR, it’s already merged and will probably show up on instances soon.
Very nice!! Congratulations!
Maybe you know more about web or android development, then you could look into contributing to the lemmy-ui or jerboa.
Yes that’s definitely one the things I am leaning towards. On my main “gripes” with Lemmy right now, is the lack of keyboard shortcuts (think of stuff like, CRTL+enter to send a reply for example). So I wanna see if I can add that in the frontend repository.
One of the first things I did when I learned about Lemmy and joined an instance is see if I could contribute in some way, shape or form.
But unfortunately it’s written in Rust, a language in which I have 0 experience and 0 knowledge. :(
I just checked, the admin have a little “admin” text next to their username and moderators in a community have the text “mod” next to their username.
I can’t currently check, but don’t admins already have a shield icon next to their username?
Edit: typo
Theoretically, support for that could be coming… Emby (where Jellyfin is based on) always used their own layer for interacting with a SQLite database. All that custom made logic is currently being swapped out for EF Core. EF Core is a DotNet library for interacting with databases and EFCore that also supports MySQL, PostgreSQL, SQL Server besides SQLite.
So my guess is that, once all that work is completed, support of other database can be added.
For a little bit of context. I am currently running Jellyfin on Btrfs and there is quite a performance impact due to CoW. If 2 clients decide to browse the libraries, both clients grind to a near standstill with regards to being able to see things. So I am following this work with quite some interest.