Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)F
Posts
0
Comments
180
Joined
2 yr. ago

  • 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.

  • It's frustrating that there isn't stronger enforcement by the USB-IF about how these standards can or can't be implemented. The savings of a few pennies for the sake of not including basic fast charging hardware is ridiculous.

    The idea that adopting the connector is more important than adopting the standard generates infinitely more confusion than if the connector matched the standard.

  • The standard is a collection of mostly optional features, with the only real requirements being USB 2.0 speeds and 5V1A power delivery.

    However, USB-PD, the actual fast charging standard in the USB-C spec is pretty universally implemented at this point across mobile devices. At the very least, it will always fall back to the standard 5V1A if the device is stupid enough not to support anything better.

  • Craigslist? Kijiji? Dunno where you're based out of

  • PCBWay, the Raid Shadowlegends of electrical engineering projects

  • 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

  • Tl;dr: NPP suffered a supply chain attack via their hosting provider. They've moved hosts and improved checks performed by the in-app updater. 8.9.1 is the version to be on.

  • Right now you're probably only going to find their products in SEA, SA and China based on what I've seen. You could try Chinese sites like Taobao and Alibaba, but if you're an American citizen then you aren't technically allowed to port them, as they're a banned manufacturer, as with most Chinese brands.

  • 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?

  • I think HTG used to be, but they seem to have pivoted to more than just their tech listicles and have a few writers that cover niche tech topics

  • 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?

  • I'm using Fedora 43 Plasma under Wayland, with the regular Discord flatpak. Vesktop works, but I recall some oddly hacky things I had to do to make it work

  • It works and has worked for a while. Application specific sharing for audio is an oddity though, since it can't seem to isolate and you get all desktop audio excluding discord

  • It's best practice to keep it separate, and that mostly just has to do with how the different file systems are handled.

  • Wayland works differently than X11 in this regard. Using Fedora 40 on a Lenovo Yoga 730, I had to enable Tablet Mode from the KDE settings and then auto-rotation worked fine

    Surface devices might be different though, so I can't say too much about them. There may be a specific sensor library or tool required, since Wayland communicates with your device differently than X11