sorted by: new top controversial old
[-] yhvr@lemm.ee 2 points 1 week ago

Hadn't heard of pikvm before. Will keep that in mind, thanks!

[-] yhvr@lemm.ee 7 points 1 week ago

While you didn't name names of what app you were using for streaming, I just got into a similar situation with my dorm and what I found worked was using wired ALVR for my streaming. Not wireless, but good, long right-angled USB-C cables don't cost a fortune. https://github.com/alvr-org/ALVR/wiki/ALVR-wired-setup-(ALVR-over-USB)

[-] yhvr@lemm.ee 9 points 1 week ago

I'm at college right now, which is a 3 hour drive away from my home, where a server of mine is. I just have to ask my parents to turn it back on when the power goes out or it gets borked. I access it solely through RustDesk and Cloudflare Tunnels SSH (it's actually pretty cool, they have a web interface for it).

I have no car, so there's really no way to access it in case something catastrophic happens. I have to rely on hopes, prayers, and the power of a probably outdated Pop!_OS install. Totally doesn't stress me out I'll just say I like to live on the edge :^)

[-] yhvr@lemm.ee 0 points 2 weeks ago

What's Reddit?

[-] yhvr@lemm.ee 1 points 2 weeks ago

I don't know the specifics behind why the limit is 72 bytes, but that might be slightly tricky. My understanding of bcrypt is that it generates 2^salt different possible hashes for the same password, and when you want to test an input you have to hash the password 2^salt times to see if any match. So computation times would get very big if you're combining hashes

[-] yhvr@lemm.ee 9 points 3 weeks ago
[-] yhvr@lemm.ee 18 points 4 months ago

While I do agree that this is bad, I'm a little confused—what does this have to do with dead internet theory? Doesn't that relate to users being bots?

[-] yhvr@lemm.ee 8 points 6 months ago

I'm sure a lot of forks will pop up right around this time. I'll be less skeptical of them once I see actual commits made to the codebase instead of things like just changing the readme

[-] yhvr@lemm.ee 141 points 6 months ago* (last edited 6 months ago)

I hate to be that guy, but it doesn't seem like there's anything to this fork. At least a few links in the README don't work, and the domain for the "email" is actively for sale. The owner of the repository doesn't seem to have any real previous projects on their GitHub account.

I can understand that it's a new fork, but in my mind you'd want to at least make sure the Readme is... passable before you spread the word and make a Patreon for the project.

EDIT: The Patreon link has been removed since I made this comment. I'm still incredibly skeptical of the project though

[-] yhvr@lemm.ee 35 points 7 months ago

The brief explanation is that Nitter worked by creating "guest accounts", which were a leftover from when you used to be able to use the Twitter mobile app without an account. After creation, these accounts lasted for a month. The time since the ability to create these accounts was removed is nearing (has reached?) a month

[-] yhvr@lemm.ee 8 points 8 months ago

I think what was meant here is that it won't run apps designed for the Oculus Quest lineup (which is based on Android), not the actual Facebook application

[-] yhvr@lemm.ee 1 points 10 months ago

I have an external monitor that runs at 144Hz, but a while ago I realized because it was connected over HDMI, it was limited to 60Hz (for some weird reason). So I bought a DisplayPort cable, and after plugging it in the screen was flickering/artifacting in some weird way that I haven't seen it do on X11 or Windows with the same cable. So as a result I've had to reluctantly switched back to i3 for daily use

view more: next ›

yhvr

joined 1 year ago