moira

joined 2 years ago
 
 
[–] moira 1 points 2 years ago
79
water WATER (sh.itjust.works)
submitted 2 years ago by moira to c/[email protected]
 
[–] moira 6 points 2 years ago

I do also feel like it is more jittery (android 13, jerboa 0.0.35)

[–] moira 1 points 2 years ago

Depends which route you wanna take:

  • cheap and works out-of-the-box - entry level synology/qnap/asustore
  • have some more room, cheap, expandable, want to tinker a bit: consider used/refurbished SFF/Tower, you can get some of them in very decent price, like HP Z230 (or other haswell+ CPU), slap truenas and there you go.

Personally I prefer the more DIY approach, as it doesn't lock me into hardware (e.g can diagnose/replace faulty parts instead of throwing away whole box) or software (synology actually use standard md/btrfs raid so it can be read by any modern linux). Although I was using Synology myself and was very happy about the software

[–] moira 1 points 2 years ago

I've been looking for something like that! It would be awesome if it would be adopted by many servers as imo this is the biggest drawback with discord compared to old school forums

[–] moira 1 points 2 years ago

Tbh today you only have firefox and chromium based browser, most of them use similar amount of memory. On my laptop with 4gb of ram (which is running endeavoros with xfce) I'm using firefox with multiple add-ons. I suggest installing ublock origin, but I wouldn't expect much of a difference on that tier of hardware

[–] moira 1 points 2 years ago

On your own email server make sure that you have correctly setup dkim, spf, reverse dns, and the ip of server is not on any known denylist - but it still doesn't guarante that your email server would not get flagged as a spam source.

Or maybe setup transport rules that would try to deliver most emails directly, but to major providers like Gmail/outlook which are quite picky via smtp relay - at work we are using AWS SES to do that, it is not that expensive, but it depends on the volume.

[–] moira 3 points 2 years ago (1 children)

As you are running cloudflared in docker container, by default 127.0.0.1/localhost equal that docker container. Easy fix is to add

extra_hosts:
      - "host.docker.internal:host-gateway"

to your cloudflared service in docker-compose. Then you can point tunnel to host.docker.internal and it should point to your docker host instead of localhost of container. (ofc after reloading services by docker-compose up -d)

Another easy solution would be to make your owncast server listen on lan IP of your server, and point cloudflared tunnel to that

[–] moira 1 points 2 years ago

I also sometimes experience that issue, check in developer console if you don't have errors with websocket connections. Not sure what causing that (my side/server side), but most of the time CTRL+F5 (refresh with clearing cache) fixes the issue

[–] moira 1 points 2 years ago

I'm not new to fediverse, but i found the same friction points like with mastodon

  • which instance to pick (or maybe i should host my own straight away?)
  • how to discover new communities - browse.feddit.de definietly helps with that
  • links that redirects me to another instance
[–] moira 4 points 2 years ago

Mostly overwatch and sometimes beatsaber on quest