deleted by creator
I’m Sarah. I’m a Brit who fled to Portugal on account of Brexit, increasing intolerance and the British weather. I like climbing (although I can’t do much any more for health reasons) and sailing. This is a Friendica account. Friendica is kinda like Facebook as Mastodon is kinda like Twitter, except they can talk to each other.
deleted by creator
deleted by creator
@mihnt OTOH, if it’s just you looking for access, consider Tailscale.
@mihnt Well, you could try Dyndns?
@aniki As I said, I did the comparisons fully expecting to get a NUC. The Mac was cheaper at the performance point.
As for US prices, not especially relevant to me. Import taxes are a thing.
@Skwiggs Few months. I was using an old laptop with Debian before but Friendica was cooking it, literally.
The M2 Mini doesn’t break a sweat. It just takes the load and gets on with it.
@ninjan friendica can get quite heavyweight.
@aniki because it was the cheapest machine available for the performance I wanted in a useful form factor.
@deleted I couldn’t find one with equivalent performance to the M2 for less money.
I am not purchasing in dollars.
@TCB13 I was surprised as well.
@BornDeranged I’m running everything in containers. Not got anything which cares which architecture the server is. Data is data.
@Skunk Nice. I’m happy with the M2 running MacOS and just spinning up Linux VMs in UTM as needed. It seems to handle them without breaking a sweat and, for self hosted stuff, having the VM bridged to a VLAN tagged interface gives me that extra reassurance without having to have the whole machine on that interface.
If the baddies compromise the Friendica server, I can just Remote Desktop into the Mac and nuke the VM. Bye bye.
@BornDeranged Honestly, moving stuff to the cloud is trivial. Everything is in containers and I can just setup the nginx reverse proxy that’s also running on the VLAN to redirect to the cloud. Job done.
deleted by creator
@furycd001 Impressive how it can go on at such length and completely omit to mention the replacement of coax with unshielded twisted pairs.
@Tywele How are you trying to access it locally? Are you using its fully qualified domain name and does that resolve to your WAN address? If so, you MAY need to locally override the DNS entry with its LAN address. You need to use the FQDN though.
I had this issue when using a VLAN for this server (as in the server I’m writing this on). “Thegoatery.dyndns.org” resolves to my ip address, the router goes, “oh, that’s me”, but won’t route it because the source and destination are on different VLANs and it has no rules to route via the WAN address.
@Tywele as in, you get the NPM config site?
On my docker install, that’s on port 81. My router forwards ports 80 and 443 to NPM. You probably shouldn’t be able to get to the config site through a firewall.
deleted by creator
deleted by creator
@return2ozma @davel And variously previously one-to-one, Orange, and T-Mobile.