Oh, I know (I am a greying wizard), but why should the editor care? In theory, it should assume XCF, with the opened JPEG as the first layer.
Instead, it’s gotchas and RTFM. Which is sadly a very poor approach when developing a tool used by creatives who are vastly less likely to RTFM than the engineers making the tool.
Manually adding alpha channels to layers… I’ve seen so many people knock their heads against GIMP because, for whatever reason, they didn’t just add the channel by default. (Okay, sure it’s probably the default if you’re starting with a blank file but the background layer doesn’t have one and if you start by opening a jpg, then subsequent layers won’t have alpha because… reasons…)
I don’t think it’s because they don’t have UX designers, it’s because they only solicit feedback from existing users rather than researching new user experience and watching how a new user gets on with the program.
I also think very few Adobe or Affinity power users get stuck into GIMP etc because they bounce off it so quickly. So they never get feedback from the very users they want to convince to move over.
Inkscape and GIMP etc are fine tools in their own right (I have had them installed for years) but where things have always broken down is when you’re working in larger teams and working towards a larger goal.
Inkscape, GIMP, Krita, LibreOffice is an awful chain when you compare it to say Affinity where you can shift between vector, pixel, and layout workflows within the same tool (or copy and paste seamlessly across Adobe tools).
Until the FOSS community sits down and works with creatives and end users who don’t use the tools (which Audacity did thanks to Tantacrul and the results speak for themselves), we’ll be stuck with proprietary tools.
The problem is when new users turn up to give feedback to say Inkscape for some of their weirdness like opening a blank doc each time the app opens, different tabs for fill and stroke color, weird behavior with fonts changing when you backspace out to an empty box, blah blah, the community goes “skill issue” or “this isn’t Adobe”.
Yet they fail to understand the design decisions as to why other products have more obvious behaviour patterns - they want the tool to be relatively self explanatory and try and align to user expectations as much as possible.
Tantacrul did a great talk at FOSS Backstage Design conference that is really worth watching if you’re interested in the topic.
I’d say the second one was even harder too.
<
Isn’t 64bit Steam Client due to drop for Windows imminently? They end 32bit support at the start of next year supposedly.
Really well articulated.
Valve have enabled a critical mass of “target platforms” that enables both the community and developers to get things working on Linux, which all other distros are about to benefit from.
I’m likely going to buy all the new Valve hardware out of principle. The Deck is incredible, but I still have my beefy gaming rig. But my living room wouldn’t mind a Steam Machine (and my girlfriend is definitely after both a Steam Frame and Controller 2.
I’m taking time off work in a couple of weeks and I’m moving over to Linux completely - I too have felt the inertia of dual booting and find myself in Windows far too often.
The failure of the Steam Machine is why Valve hosted Khronos group at their office to kick off Vulkan and funded LunarG etc in the early days to get things moving quickly.
Valve took their time but this new hardware range is based on years of learning and solving the problems from their original foray into hardware and Linux for gaming.
And I’m so thankful for it!
And while the Link hardware was cancelled, they still put out updates for it. I think the last update was only a month or two ago.
Steam Controller 1 also got cancelled but they’re still shipping updates and showing that device too.
GCompris or TuxPaint are great for younger kids. They’re free/open source and have versions available for Windows, macOS, and Linux.
Or spin up TES3MP with some friends and experience it together!
Have you had anyone with experience with security look at this thing? There’s a lot of really questionable practices in your schedule shell scripts. I especially find how you’re handling VPN secrets kinda worrying. And the backup_challenge_clients.sh script isn’t robust at all. Your nginx config has a few bad choices like lack of try_files, the regex \.php$. It’s definitely not hardened so I hope people don’t put this Internet facing.
I’ve spent like 5min in the GitHub to get a feel for the project maturity. Personally, I don’t think this is suitable for actual use yet.
If you’ve not done any security assessments on your project yet, you might not want to (a) call it “Safe”box and (b) might not want to start charging money for it until you do.
I worry you’re setting yourself up for a hard-to-shake-off embarrassment should a nasty vuln be found. Maybe a name like “selfbox” etc that drops the connotation of security would be safer.
Edit: Kudos on the project website though! Looks fricking gorgeous.
deleted by creator
If you went with Arch Linux, you could effectively set up your own mirror, download the wiki zim file, and you should be good to go.
There is bandersnatch for mirroring PyPI but docs are all over the place for Python packages. You might just have to hope they made liberal use of docstrings…
Almost without a doubt. Original Sin 1 and 2 were my all-time favourite RPGs until the same developer casually released Baldurs Gate 3 and stole the #1 slot.
I know people in the working group in the cybersecurity space working with MS on these APIs and this really isn’t their plan. They aren’t doing it to kick people out - cybersecurity want out for themselves as no one wants to do a CrowdStrike.
There are countless other use cases for kernel drivers that won’t be in scope of the APIs being drafted.
What’s that got to do with MS’s decision to kick them out? What’s the Venn diagram of mission critical systems and systems running Valorant/League?
I’m not disagreeing that these bullshitty kernel drivers running from boot exist, I’m stating that MS aren’t going to do shit about it if even more risky kernel drivers aren’t planned to be removed from the OS and there’s plenty of other popular anti cheat drivers that are only loaded at runtime.
Yes but many don’t. And the risk impact of BSODing gaming computers vs business systems is dramatically different.
We won’t see MS do anything about kernel drivers until the majority of security industry has moved to whatever new userspace APIs MS release.
Even then, do gaming anti cheat developers really care?
IMO simply vote with your wallet and don’t buy games that need kernel drivers and still fail to address cheaters who always find a way around.
You’re going to need to back up your claim otherwise you might as well be lying as there’s no CVE like this I can find nor any public disclosure.
Plex have a bug bounty program and a responsive security team too.
Post your security report.