If I remember right, that post wasn’t designed to highlight a practical use-case, but rather to set up a simple task as a “how could I apply this?” type of experimentation. The guy got roasted for it, but I think it’s a very reasonable thing to try because it’s a simple task you can see the direct result of in practice.
The cost problem was highlighted as well, because if such a simple task is a problem, it can’t possibly scale well.
Audio hasn’t worked for me or my friends across Linux or Windows. Been kind of a pain.
It also seems to suffer the XWayland issue in Linux that Discord did for quite some time where it just flat out fails to get screen capture in the desktop app, but works in the browser. Electron pains
Paying for journalism is ideal, but unfortunately makes it difficult to cite/link to a source the way Wikipedia needs as a way to ensure the information remains open and accessible.
Admittedly, I’m not familiar with these outlets enough to know if those paywalls are significant, but the problem with direct article links is that those links can change. Archival services (I suppose not archive[.]is) are important for ensuring those articles remain accessible in the format they were presented in.
I’ve come across a number of older Wikipedia articles about more minor or obscure events where links lead to local new outlet websites that no longer exist or were consumed by larger media outlets and as a result no longer provide an appropriate citation.
I wouldn’t expect that to change. Their primary intention is in building out a suite of tools for use within their own government institutions, rather than a wider audience. If you’re interested in self hosting though, the Github documentation is pretty much all in English
“Visio” is their internally developed video conferencing platform. It’s part of their “La Suite Numerique” suite of software, most of which is open source in large capacity
It is. Currently their code is published under an Apache 2.0 license. There’s links to it on the website, but the whole suite is on Github. It would be nice to see them migrate that codebase elsewhere down the line though
They’ve been building an entire open source suite of software tailored to their needs. If I had to guess, Jitsi isn’t performant enough for large (100+) user meetings in a way they can scale easily. It’s a great tool, but it seems better geared towards smaller loads. Video conferencing at scale is a pretty big challenge.
Between this, their new Docs platform and some Matrix-based chat platforms, I think this is something they’ve put a fair bit of thought into how they want to build. Overall, it’s a cool initiative, but I think it’s pretty clear that it’s open source as a means to be transparent as a government organization rather than to form a platform for broad use by everyone. They do have some self-hosting instructions on their GitHub though.
…Lyft Bieber?
Yes, you got it.
It’s possible that however your ISP provided router is designed, it’s got some hidden port forward configuration. If that router has an option typically referred to as “bridge mode”, you could bypass its routing features altogether and use your own router instead.
ISPs often have clauses about using their residential internet for hosting servers or exposed services, and it’s possible your has taken a different approach to mitigating traffic from those sources.
If you can, I’d recommend using your own router rather than what the ISP provides.
If I understand correctly, it sounds like you moved from an ISP that uses CGNAT to one that does not. Does your ISP provide a modem? If so, are you relying on the software features of that modem, or do you have a router inbetween?
Interviews do typically count, it just has to be citable. Videos are sufficient in that regard as well, not just articles or books. It would be different if Torvalds had edited his own wikipedia page, but an editor who updates the page and cites this video would not be in the wrong.
I mean, I feel like he outright confirms it in the video. It’s his distro of choice since it allows him to easily use his own compiled kernels in testing. Anything else is an inconvenience to his work.
How’s the overall health of the drives? You might want to get a quick SMART report.
Otherwise, this sounds like pretty normal drive activity. It could be the result of anything from indexing tools to casual background processes doing a read.
If it’s periodic in a way that’s consistent, then it’s almost definitely something in software. What docker services are you running? Do you have any auditing tools or security processes that might be actively logging activity?
It’s pretty unlikely you’ve contracted malware unless you’ve gone out of your way to expose the server to outside sources, so I think you can alay those concerns.
A couple points:
I dove into self-hosting several years ago and ultimately I think I found the experience quite welcoming. I also don’t know that Safebox has a lot to offer over well-established alternatives these days like Unraid or TrueNAS, which have large user-bases and a depth of support articles to help admins better understand what they’re doing and how to do it. It’s true that not everyone would want to do this as a hobby. No one wants their services to break, or their data to be lost, and more tools that make it easier to prevent these scenarios are helpful. With that in mind, I am not left with a clear understanding of how Safebox is meant to provide safeguards here.
I used the word “admin” in the previous paragraph for good reason. Self-hosting makes you the administrator, and it means that you, the administrator, have the power to make mistakes. My recommendation is not to talk down to your users. Someone interested in self-hosting should be aware of the potential security implications of what they’re taking on, alongside the risk to their data and that breaking changes are something they can and will make along the way. If you really want to make self-hosting accessible, then the documentation for your tool needs to be accessible too.
Safebox runs on Linux, macOS, and Windows, supports both x86 and ARM64 (including Raspberry Pi, Banana Pi, and others), and handles domain/subdomain setup, Let’s Encrypt certificates, DNS configuration, reverse proxy (nginx), and also offers WireGuard-based remote access.
A user should be able to learn why these elements are important and how they work together. Talk about the limitations of running it on a raspberry pi vs a workstations or server. What’s a reverse proxy? Is WireGuard good? This doesn’t mean the average person needs to know how to configure detailed permissions or application configs, and if the goal is to provide a repository of pre-hardened Docker configs for use then that’s cool too, but there should never be a barrier to the information itself. Especially as it is relevant to the tool you’ve built.
I think that fundamentally, you’ve built a good tool that simplifies things someone who is already familiar with its components, and where it needs to improve is by expanding to help new users familiarize themselves. Education is as big a part of accessibility as the ease-of-setup.
Something KDE has done seems to have resolved the issues I used to have with DPI related scaling problems in Wayland. Once Plasma 6 hit, it’s been nothing but rapid improvements with Wayland as a focus and man does it feel nice.
That said, there’s virtually no downside to still using X unless you have explicit display features you need from Wayland like HDR or the per-display scaling. Xfce is stupid lightweight and still my default for anything where battery life is a benefit.
Using the old interface seems to yield better results there. It appears to be their newer API model that’s suffering.
Fair enough. I missed this push amidst every other AI related enshittification tactict at the time I guess. That said, this is how it should work. An organization proposes a change and the change is withdrawn or halted after the userbase is able to weigh in. I’m pleased that they didn’t barrel ahead with it despite the outcry.
I feel for the Wikimedia foundation right now. They’re under mounting pressure to compete with corporations that hold a monopoly on how people access their sites and subsequently the information on them. The goal is to provide open information, but that information is no less open to the AI that aims to scrape, rehost, and re-use the work of individuals who have volunteered their time to it.
I think it would have been easy for them to effectively do what Reddit did, and lock down the access to the site and its content in order to develop their own AI tools to perform similar tasks trained on their dataset exclusively. Instead, they’ve listened and I hope they continue to listen to their dedicated members who believe in the foundation’s original goals.
Not all AI use is bad, and it sounds to me like you didn’t read that article itself. They have no desire or intention to use AI in a way that directly effects the information on the site, how it’s presented to visitors or to use it in a way that would manipulate how articles are edited.
The only potential note is translation, but translation is such a massive undertaking that by providing a means to discuss and interact between languages, the information becomes more broadly available and open to correction as needed by native speakers.
Also, Britannica does employ the use of AI within their own system as well, even providing a chatbot by which to ask questions and search for information. It is, in this way, more involved than Wikipedia’s goals.
To add, Apple has actually been making amends regarding repairability. It’s small steps, but leagues ahead of what’s offered for popular android manufacturers, while still maintaining their IP68 ratings on most devices.
I can’t speak to how they make their parts available to third parties (seems to be a grey area), but there has been a reasonable focus with the last couple generations of iPhones that ensures the device can be repaired from either side.
Overall, the tide seems to have shifted. If you’re going to be at the mercy of a corporate giant in order to keep up with modernity, then Apple is currently holding the dimly lit torch of consumer rights.
I hate playing this on a N64. I own it, I’ve tried, it’s a miserable experience. I largely chalk this up to it just being the N64 controller though.
With a proper controller, it controls very nicely imo. Inputs are precise and it takes some work to get good but it’s overall still one of my favorite Mario games, next to Odyssey.