fmstrat

joined 2 years ago
[–] fmstrat@lemmy.nowsci.com 9 points 2 days ago

Agreed. Amazon is a sales company. Google is a data company. Open Home Foundation is a better company.

[–] fmstrat@lemmy.nowsci.com 24 points 1 week ago

Best part:

The unauthorized party gained access to “information from a limited number of users who had contacted Discord through our Customer Support and/or Trust & Safety teams”

[–] fmstrat@lemmy.nowsci.com 1 points 1 week ago

And so have countless closed-source developers/companies/applications. A vulnerability existing does not change the fact that FOSS projects should be funded more.

[–] fmstrat@lemmy.nowsci.com 70 points 1 week ago (15 children)

We aim to introduce additional paid services (not paywalled features, as we will never implement paywalled features), which will help support the project and that enhance self-hosting, making it easier and more reliable. First among the many services already planned is an end-to-end encrypted, off-site backup and restore feature, built directly into Immich. This will enable a buddy backup feature as well.

I love this.

Free features, but offering actual useful services for self-hosters (encrypted cloud backup). Great business model for a project like this.

[–] fmstrat@lemmy.nowsci.com 1 points 1 week ago (1 children)

My understanding is the stability risks come from active development additions vs "fixes" during that stage of the development cycle.

https://linuxiac.com/torvalds-expresses-regret-over-merging-bcachefs-into-kernel/

Simply put, only small bug fixes are allowed after the post-merge phase to integrate changes into the current kernel cycle. However, Overstreet’s PR included more than just fixes; it continued to develop new features, which always carry risks. That’s why Torvalds was unhappy with it. As a result, the changes were rejected.

...

Currently, the file system is being actively developed. Although it shows great potential with impressive features and strong data reliability, it’s not yet stable enough to be adopted by major Linux distributions as a proven and reliable solution.

YMMV, but my production systems will stick with ZFS since it's kernel release updates are clear when there are "upgrades" vs "updates", as you do those manually when it alerts you.

"Stable" in this context doesnt mean "your PC will definately crash and you will lose data!", bcachefs is well past that. It means that the development is too active to be considered production ready since the code changes are too large to confirm the scary bit won't happen (as much as can be).

Even JC threw in the towel on bcachefs-tools due to this: https://www.phoronix.com/news/Debian-Orphans-Bcachefs-Tools

[–] fmstrat@lemmy.nowsci.com 5 points 1 week ago

In this situation it works well, IMO. For some more context, ZFS was created by Sun (FOSS). Oacle bought them and built Oracle ZFS out of it. OpenZFS forked at that point from Sun code, and that's what we use in Linux/etc. The Oracle variant supplies support to the FOSS variant. So Oracle has no control over OpenZFS.

[–] fmstrat@lemmy.nowsci.com 1 points 1 week ago

This is flawed thinking. There is no "them" with a huge salary. The people making decisions are salaried or invested employees, and their livelihood depends on the stock regardless. There isn't "one guy" that this hits, like it would with a salary, there's thousands of investors which must be appeased.

Also, it's likely many of those canceling were people who didn't use the service as much as power users, which means they're losing the cheapest to maintain customers (industry insight, no research to back this up, to be clear).

If we had boycotts and cancelations even a quarter this big across other media giants, our media would be a far better place.

[–] fmstrat@lemmy.nowsci.com 2 points 1 week ago (3 children)

Fair enough on "major". Edited that. But it has stability issues that aren't handled well enough for RCs, so it's not a hit piece to state that fact. Those stability issues may come from it being new, but it's still an issue. Saying it's because they want to "get rid of Kent" is just as much of a hit piece, too.

[–] fmstrat@lemmy.nowsci.com 5 points 1 week ago (6 children)

Everyone always says "Companies should fund FOSS instead of spending money on big corpos!", yet then this.

It's FOSS. It's auditable. Funding is a good thing.

[–] fmstrat@lemmy.nowsci.com 7 points 1 week ago

I was thinking the same thing. Sounds like they did exactly what any studio would do in a regular shoot.

[–] fmstrat@lemmy.nowsci.com 11 points 1 week ago

Weechat.

Or if you're feeling nastalgic, BitchX.

Or if you want to be more modern, Matrix with the mautrix-signal bridge and Element as a client. This is what I do so I can combine all my chat apps into one.

[–] fmstrat@lemmy.nowsci.com 24 points 1 week ago* (last edited 1 week ago) (17 children)

No, comment is not true. You can use ZFS or BTFS, both of which are open source. ZFS just happens to be historically funded by Oracle, which is a good thing.

The reason is bcachefs has ~~major~~ stability problems (that don't allow it to meet kernel release schedules). https://hackaday.com/2025/06/10/the-ongoing-bcachefs-filesystem-stability-controversy/

@BombOmOm@lemmy.world

@nixon@sh.itjust.works

 

Hi all,

I run a private self-hosted Synapse server with bridges for:

  • Signal
  • WhatsApp
  • Doscord
  • IRC
  • Google Voice
  • Custom APIs

I am thinking of switching to XMPP. Can anyone recommend a good Docker-based server and transport combo that I could test out?

10
submitted 4 months ago* (last edited 4 months ago) by fmstrat@lemmy.nowsci.com to c/games@lemmy.world
 

Really wish the DLC for this was still available. Slay away Camp is good, but this was so much better and I missed out on the DLC..

 

Hi all,

I've been running a bunch of services in docker containers using Docker Compose for a while now, with data storage on ZRAID mirrored NVME and/or ZRAID2 HDDs.

I've been thinking about moving from my single server setup to three micro-servers (Intel N150s), both for redundancy, learning, and fun.

Choosing Kubernetes was easy, but I'd like to get some outside opinions on storage. Some examples of how I'm using storage:

  1. Media and large data storage: Currently on the ZRAID2 HDDs, will stay here but be migrated to a dedicated NAS
  2. High IO workloads like Postgresql and email: Currently running on the NVMEs
  3. General low-volume storage: Also currently on NVMEs, but different use case. These are lower IO, like data storage for Nextcloud, Immich, etc

I'm a huge fan of being able to snapshot with ZFS, as I mirror all my data off-site with hourly pushes for some container data, and daily for the rest. I'd like to be able to continue this kind of block-level backups if possible.

Assume I'm a noob at Kubernetes storage (have been reading, but still fresh to me). I'd love to know how others would set up their storage interfaces for this.

I'm trying to understand if there's a way to have the storage "RAIDed" across the drives in the three micro-servers, or if things work differently than I expect. Thanks!

 

Hi all,

Working through some things like a Will (I am fine, just normal life planning), and debating on methods for digital management when I do die.

I run a lot of self-hosted services for family and friends, all on secured servers with ZFS and on/off site backups. Key ingredient is Vaultwarden for password management.

I'd like to put something in place so that encryption keys, some docs, and key passwords are released to a tech savvy friend. Anyone know of existing solutions for this?

Requirements of:

  • Not providing keys to a third-party beforehand
  • Not forgeable to open
  • If possible, no "weekly press a button"

I'm thinking some kind of key pair where my friend has the private key and the public key is provided to a family member, and when activated a timer starts where I could cancel the release.

 

Hey all,

Anyone familiar with the state of Raptor Lake performance + efficiency cores in Linux? I'm specifically curious about how the kernel balances things when running multiple containers (without pinned CPUs)

Thanks!

13
submitted 10 months ago* (last edited 10 months ago) by fmstrat@lemmy.nowsci.com to c/games@lemmy.world
 

There's a part as a sniper, I think, and maybe it was third person mostly? The name was initials that remind me of XKCD, like that sound, but probably 3 letters. And I feel like the character wore white cloths. PC game. This is a stretch.

 

It has fInally happened. And Technology Connections approves.

 

cross-posted from: https://lemmy.nowsci.com/post/9782596

Hi all,

I've finally gotten around to releasing these formally after much testing of prints and usage.

The Twystlock system is a set of 100% 3D printable gaming accessories that require no printed supports or additional parts. This means no springs to buy and no metal elements to melt in, just access to a 3D printer and a bit of super glue. Originally designed for the Steam Deck, these accessories can be applied to the case of any mobile gaming device.

The Twystlock connector itself is designed as a quick-connect that secures parts together with a simple twist motion, can be fully recreated with affordable home-based 3D printers, and doesn't require complicated supports to print. The first use of this connector has been for the Steam Deck, specifically to supply an alternative accessory platform that is more accessible to the everyday 3D printing hobbyist, however it could be utilized as a connector in almost any environment.

Feel free to download what you like, and if you would like to request a new accessory design, or vote on the next accessory to be created, please visit our Lemmy community at https://lemmy.world/c/twystlock@lemmy.nowsci.com.

 

All the posts about Reddit blocking everyone except Google and Brave got me thinking: What if SearNGX was federated? I.E. when data is retrieved via a providers API, that data is then federated to all other instances.

It would spread the API load out amongst instances, removing the API bottlenecks that come from search providers.

It would allow for more anonymous search, since users could cycle between instances and get the same results.

Geographic bias would be a thing of the past.

Other than ActivityPub overhead and storage, which could be reduced by federating text-only content, I fail to see any downside.

Thoughts?

 

Almost 30 more minutes of dishwasher.

view more: next ›