Avatar

otl

otl@lemmy.srcbeat.com
Joined
1 posts • 33 comments
Direct message

Sorry guys I’m out of the loop - could someone explain this?

permalink
report
parent
reply

I think learning how to make packages for package managers is also becoming less popular :(

Even learning how to do the simplest thing possible that is easy to package by anybody - something like a tarball or zip - is becoming less popular :(

permalink
report
parent
reply

omg that is sssooooo exaggerated like 1000% take that back pls

permalink
report
parent
reply

Back in 2005, I never would have thought YouTube would be so popular as it is now. But here we are over 15 years later. Teens probably think Facebook is uncool, and apparently they’re not all on Instagram “almost constantly” the same way as TikTok. Yet there is YouTube, chugging along, hugely popular for young and old.

permalink
report
reply

Cross-platform clients, yes, but that’s only a (small) part of the way there. For example, Signal is actively hostile to other client implementations just like Apple is with iMessage, unfortunately :(

permalink
report
parent
reply

I’ve found this feature mostly reliable. Those times where it doesn’t work, or I’m travelling, or don’t have phone reception is kinda annoying. But being able to just use my Mac is fantastic.

permalink
report
parent
reply

It’s really about interoperability of systems, protocols, services, and clients. Since we’re both using Lemmy I assume we both understand at least a bit about the significance of interoperability.

I think it’s a shame that effort is put in to reverse engineering.

permalink
report
parent
reply

Hey no problem :) I totally understand and read through the linked README. FWIW I find the fact that Lemmy is in Rust, pretty… tricky. Getting Lemmy to run on my OpenBSD server started with a couple of crazy segfaults!

permalink
report
parent
reply

Time to turn your laptop into a router! Let’s say you’ve got 2 network interfaces on your laptop, eth0 and wifi0. wifi0 is joined to your university WiFi as normal. Connect your iPad to your laptop via ethernet (with a USB-C adapter).

iPad -> usb-c-ethernet -> eth0
wifi0 -> internet

Rather than setting up a DHCP server or IPv6 stuff, I’d just configure the wired interfaces manually. Let’s use the network 192.168.69.0/24. Laptop will be 192.168.69.1, iPad will be at 192.168.69.2. On the laptop:

ip addr add 192.168.69.1/24 dev eth0

On your iPad, go to Settings -> Ethernet:

  • address: 192.168.69.2
  • subnet mask: 255.255.255.0
  • router: 192.168.69.1

Curious to see if that works. We haven’t set up DNS or DHCP or done any sysctl for IP forwarding or any nftables.

How can we test if it works? We can set up a TCP listener using nc(1) on the laptop that the iPad’s web browser could hit. On the laptop:

nc -l 8080

On your iPad, open Safari and browse to http://192.168.69.1:8080

Curious to see if that all works!


See also:

permalink
report
reply