eh

joined 1 year ago
[–] [email protected] 2 points 1 year ago

All of these are "root" mounts. I don't explicitly mount any subvolumes (they get "implicitly" mounted as folders though)

 

I couldn't find any documentation about this anywhere, but it seems like they do NOT work together

% rg -i storage /etc/fstab
UUID=7c16eaa0-a423-4e51-aa5c-116adf806511     /storage/disk1          btrfs           noatime,lazytime,compress-force=zstd:9,x-systemd.automount      0 0
UUID=567c5fc4-3cc5-4572-9d45-01e55d30647c     /storage/disk2          btrfs           noatime,lazytime,compress-force=zstd:9,x-systemd.automount      0 0
UUID=d0e1ec15-2699-4afa-9393-60ae3d4370b7     /storage/disk3          btrfs           noatime,lazytime,compress-force=zstd:9,x-systemd.automount      0 0

% mount | rg -i storage
systemd-1 on /storage/disk1 type autofs (rw,relatime,fd=52,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=16608)
systemd-1 on /storage/disk2 type autofs (rw,relatime,fd=53,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=16614)
systemd-1 on /storage/disk3 type autofs (rw,relatime,fd=54,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=16620)
/dev/sdc1 on /storage/disk2 type btrfs (rw,noatime,space_cache=v2,subvolid=5,subvol=/,x-systemd.automount)
/dev/sdb1 on /storage/disk3 type btrfs (rw,noatime,ssd,discard=async,space_cache=v2,subvolid=5,subvol=/,x-systemd.automount)
/dev/sda1 on /storage/disk1 type btrfs (rw,noatime,space_cache=v2,subvolid=5,subvol=/,x-systemd.automount)

running Arch (btw), if that makes any difference

[–] [email protected] 3 points 1 year ago

Storage space is one issue. Bandwidth (how many TB/mo goes out the server) is another. And for any "serious" use case transcoding would also be important (so you can keep the other two down for everyone except Apple users who are stubborn to adopt VP9/AV1, and to provide multiple quality options), which unlike the other two requires powerful hardware most instances do not have.

[–] [email protected] 8 points 1 year ago (1 children)

It uses WebTorrent for distribution between viewers watching at the same time which can temporarily help with the load on popular videos, but there still needs to be at least one source instance that's sharing the video "regularly" (for unpopular or old stuff), which ends up having the same bandwidth issues you'd get with any other video platform.

[–] [email protected] 1 points 1 year ago (1 children)

nobody (in terms of both apps or servers) uses the C2S API. the closest you can get to a "de facto" standard is unfortunately the Mastodon API.

[–] [email protected] 1 points 1 year ago

alongside the others mentioned here, lemdro.id exists for Android-related stuff and lemmyrs.org exists for Rust stuff (but seems to be running an old version of Lemmy, so YMMV)

[–] [email protected] 3 points 1 year ago

Light mode only "clicked" for me when I set my monitor's brightness all the way down. If you're getting "flashbanged" turn that brightness down. It helps (or maybe my monitor is just really fucking bright)

Except Discord which somehow manages to have the worst light theme ever created by mankind. I have no idea how anyone can use light mode without going mad. Everything else's fine.

[–] [email protected] 10 points 1 year ago

Well, the "how" is technically simple. You paste the URL to the search box and you hit subscribe. You can do that right now with:

  • Lemmy communities
  • Kbin communities
  • PeerTube channels
  • Mayyyyybe a.gup.pe / chirp.social groups???? idk how well those would work

Lemmy itself only let you subscribe to ActivityPub Group actors though, so it's quite restrictive in that regard. kbin adds user follows and microblogging into the mix, but you can't do those through Lemmy yet (or perhaps ever).

However, the real "problem" is presentation. While you can, say, follow a Lemmy group from Mastodon. Mastodon is not intended for groups so it kinda breaks and ends up spamming your home timeline with all the posts and comments. Other implementations such as Akkoma or Misskey or Calckey (pending rename) might end up interacting better (because Mastodon will try to convert everything it gets into Notes in a "lossy" fashion).

While the protocol does allow you the freedom to interact between services, you will not get the best experience if you're not on a "similar enough" service. Although that does not stop you from following a PixelFed account from Misskey, or a Mastodon user accidentally finding their way into the Lemmy comments section. (You can tell because they'll be the only comments that end up tagging people when replying)

[–] [email protected] 4 points 1 year ago (2 children)

You have to actually toggle to see it but IMO it massively improves how scrolling feels.

There are a few more scrolling-related options out there on the net if there's a particular "feel" you want to go for. https://github.com/yokoffing/Betterfox/blob/main/Smoothfox.js provides a couple you can try out, and most of these custom scrolling options use msdPhysics as a baseline.

[–] [email protected] 8 points 1 year ago (5 children)

Not obscure but general.smoothScroll.msdPhysics.enabled=true is a must have IMO.

[–] [email protected] 1 points 1 year ago

.ml unblocked the kbinBot UA a couple days ago so as new posts and comments are made it should be syncing up. there are still a few instances out there that seem to not federate as well (in particular beehaw doesn't seem to be federating beyond community discovery) but i believe that's just some reverse proxy misconfiguration (the lemmy-ansible nginx config had some federation related fixes with the release of 0.18.1 they may not have applied) rather than anything intentional

[–] [email protected] 1 points 1 year ago (1 children)

Again - I have no idea how well it's hardware support is. I assume 3d accel and whatnot would be fine because it's widely used, but dunno if anyone tried running ROCm on it.

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago)

Just let some bees loose on your system for a while and they'll sort that out.
Also depending on how good your CPU is btrfs compression would also save a fair bit. AFAIK shared libraries are pretty well compressible.

 

The "native" Android ecosystem has grown way too over-complicated for my liking. I do not want to dependency inject a Reactive ViewModel Room Repository DAO Purpose Factory (without blocking the main thread), I just want to make a god damn app.

My current wishlist is:

  1. Be reasonably efficient (we're working with phones here)
  2. Be completely open source (i.e. I should be able to throw my app on F-Droid when it's ready)
  3. Have a not terrible implementation of Material 3/You
  4. Don't be too "janky" for the end user (sorry, PWAs)
  5. Be reasonably mature

What does this leave me with? Flutter? React Native?

view more: next ›