Citations are too open ended and prone to variation, and legitimate minor mistskes that wouldn't bother a human verifier but would break automated tools to easily verify in their current form. DOI was supposed to solve some of the literal mechanical variation of the existence of a source, but journal paywalls and limited adoption mean that is not a universal solution. Plus DOI still doesn't easily verify the factual accuracy of a citation, like "does the source say what the citation says it does," which is the most important part.
In my experience you will see considerable variation in citation formats, even in journals that strictly define it and require using BibTex. And lots of journals leave their citation format rules very vague. Its a problem that runs deep.
It's unfortunate, GoTenna was (still is) pretty cool. Beartooth is similar and you can just buy them, but they unfortunately still have military-level pricing for what is pretty simple hardware.
Though in their defense, I'm not sure GoTenna was ever "popular." Probably not enough to pay the bills, given their pivot.
Meshtastic also struggles with high density and high traffic networks. Some modifications can be made to work better, but with the default settings it really grinds to a halt, and modifying the settings to be better suited requires some expertise and foresight. It works amazingly in off grid, relatively sparse networks, but it's got some major limitations.
Yeah I always wonder with these mobile ever changing mesh networks: how do they prevent messages from aimlessly looping around the network? With all the mobile devices they're too dynamic to make routing tables and broadcasting everything leads to network saturation really quickly. You could give them a very short TTL but then the reliability will suffer a lot.
Meshtastic has a TTL of up to 7 and (from what I've been able to understand) uses flood routing largely. In Northern Colorado (where I'm at) we don't have a particularly dense mesh, but are turning down from 7 because of congestion.
Meshcore seems to (I'm still learning on this) use a TTL of 64 and flood to find a route to a destination, then uses source routing for future packets, reverting to flooding again if that path fails (say a mobile repeater moves out of range).
The decision that every station is always a (delayed) router was a bad one. Also the old firmware was super chatty eating a lot of valuable ISM TX time.
They must clean up their role mess and switch to a "all clients are totally quiet - until they are set to a different mode for a reason"-strategy.
Eh, Meshtastic was originally for sparse off grid comms less than big public networks. In that role (which is still what I mostly use Meshtastic for) every client repeating messages makes more sense.
YMMV and a lot of people hate it, but I've run Nextcloud for this for years. It has pretty comprehensive support for WebDAV and CalDAV. Has sharing and lots of different authentication options; I use OIDC with PocketID.
It used to be a constant headache to keep running, but ever since I switched to the TrueNAS/Docker plugin it has worked smoothly. I know a lot of other people also have had good luck with the much lighter Radicale if CalDAV is your primary concern.
> It used to be a constant headache to keep running
It’s been very easy to run for me since version 15 or something. Basically i just use the stock docker image and mount a few files over there. The data folders are bind-mounded directories.
As usual with anything php, it’s only a mess if you start managing php files and folders yourself. Php has a special capability of making these kind of things messy, i don’t know why.
Android TV can run Tailscale or Wireguard natively. AppleTV has a native Tailscale app, and I think you can also use Passeportout for Wireguard on AppleTV but I haven't used it. Alternatively if you're on the go a lot and want to use a streaming stick in your hotel you can use a travel router that supports VPNs like GL.inet.
Airplay and Chromecast are a different story. Maybe someone else here knows different, but while it's not literally impossible it doesn't really work because of mDNS. A layer2 VPN might, but not so much on Tailscale/Wireguard.
To be fair to e.g. Baldur's Gate, finding game breaking builds appeals to many people in the core audience of that sort of game along with classic TTRPG players. Making those builds harder to achieve by accident is a good thing, but doing away with them entirely would probably be detrimental for the intended audience. True brilliance is also have systems that make that sort of build still fun to play, e.g. BG3 has some pretty amusing hidden interactions if you steamroll events you're not supposed to be able to win.
Reminds me of a game-breaking strategy in the (interesting, flawed) hybrid RTS/RPG War in Middle Earth (1988).
The RTS part involved moving armies and heroes around to fight Sauron / Saruman’s armies and defend your citadels. There was a game loss condition if you lost something like three citadels in battle.
But if you abandoned your citadels, their subsequent occupation didn’t trigger the loss. So you could simply aggregate all your forces into one giant army and take Barad Dur and Mt Doom by force.
The drama was mostly over whether or not Wayland should have been the replacement. AFAIU, everyone agreed X11 development was effectively unsustainable or at least at a dead end.
So is X11, though the reference implementation of X11 is also widely agreed to have some serious problems going forward on top of problems with the protocol itself.
Taskwarrior has a phone app on iOS and Android, and can sync with the cli one if you set up a sync server. They also revamped the sync server not long ago to be less janky than the old one.
In my experience you will see considerable variation in citation formats, even in journals that strictly define it and require using BibTex. And lots of journals leave their citation format rules very vague. Its a problem that runs deep.
reply