Shimitar

  • 2 Posts
  • 43 Comments
Joined 2 days ago
cake
Cake day: January 28th, 2025

help-circle

  • Its nice and pretty nerdy. As web based nmarkdown editor in pretty good and the extra features rocks.

    It has a few quirks I don’t like though, on the self-hosted side:

    • no multi-user support.
    • auth is quirky and required a ticket to make it work at all
    • must be deployed on subdomain, which make it impossible to host multiple instances for multiple users easily

    But from functionality point of view, I love it










  • ShimitarAtoOpen Source@lemmy.mlVespucci for OSM
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 day ago

    GPS works with a fully offline and in airplane mode device. GPS is 100% passive, unless you want faster initial fix, for that A-GPS comes into help and require data connection.

    But plain nice old reliable GPS is 100% passive and works fine with totally disconnected devices. Actually original GPS devices (who remmebers those…) where 100% offline. Maps on the SD card, no live traffic or accidents data, nothing fancy. Yoiu had to purchase yearly maps updates too, what old times.





  • I think you have it backward. Notifications come from your email client after it polls the email server. So you need an email client on your android device that checks the server.

    No need to self-host anything, unless you want to self-host your own email server, something that (while doable) is NOT to be taken lightly and will undounbtely lead to difficulties and lots of hiccups down the road.

    I am currently self-hosting my email server (bee, doing for almost 20y) but not at home and absolutely can confirm it’s very complex to setup properly.





  • No, the router being the SPOF (single point of failure) is totally avoidable.

    At mny home (no SaaS services offered, but critical “enough” for my life services) i have two different ISPs on two different tecnologies: one is FTTC via copper cable (aka good old ADSL successor) plus a WFA 5G (much faster but with data cap). Those two are connected to one opnSense router (which, indeed, is a SPOF at this time). But you can remove also this SPOF by adding a second opnSense and tie the two in failover.

    So the setup would be:

    • FTTC -> ISP1 router -> LAN cable 1 to port 1 of opnSense n.1
    • FTTC -> ISP1 router -> LAN cable 2 to port 1 of opnSense n.2
    • FWA -> ISP2 router -> LAN cable 1 to port 2 of opnSense n.1
    • FWA -> ISP2 router -> LAN cable 2 to port 2 of opnSense n.2

    Then in both opnSense i would setup failover multi-WAN and bridge them together so that one diyng will trigger the second one.

    edit: fixed small errors





Moderates