While popular in the 80s and 90s, they obviously decreased in popularity as cell phone usage/coverage increased.
730 karma · joined June 13, 2013
[ my public key: https://keybase.io/ytjohn; my proof: https://keybase.io/ytjohn/sigs/NbVxmFLTGl5RnWbxGpDTbDPW7lC6hXYkJD-9EcI7GEo ]
While popular in the 80s and 90s, they obviously decreased in popularity as cell phone usage/coverage increased.
But if someone else set it up, or you're using one of the cloud ones, FaaS sort of reinvents the cgi-bin mindset. Here is a talk by one of the Fission.io devs showing the similarities.
https://www.youtube.com/watch?v=X-XV6vvwhuo
Not a plug for fission, not affiliated. I mainly like how they integrate with Keda for event/message queue setups.
But for ISDN, each channel was the full 64k and that would bond two channels to 128k. I had a cisco modem that would let me use either channel as an analog phone. So it would connect up both channels, and when a call came in, drop down to one 64k channel. It was incredibly reliable. Even when I got DSL, I kept the ISDN for quite a while because it had more consistent upload speed.
More seriously, most ebike firmware is written in C.
This is really amazing stuff. Years ago, I was heavily interested in scuttlebutt [1]. I'm interested in grid down and "occasionally connected" communications. I particularly liked the island to island sailing analogy.
SSB has a few downsides - mainly that your client needs to download full logs. You can't just request the last 30 days. They call this out as well that your first sync could take over an hour and consume several gigs of data.
I'm just today learning about NNCP, but I've used FidoNet and UUCP in the past, so the concept is pretty familiar to me. In my mental model, I would be less interested in sneakernet than standalone wifi hotspots that one could connect to and exchange data, possibly combined with an AREDN style mesh[2].
[1]: https://staltz.com/an-off-grid-social-network.html [2]: https://arednmesh.readthedocs.io/en/latest/arednGettingStart...
As DSL and broadband became more popular, chat moved to being more asynchronous. Chat clients started synchronizing message history with the server to make it avaialble on all your devices. It was easier to leave your presence online, even when you were unreachable.
IRC itself still retains a lot of that realtime chat, mainly because of its transient nature. Yes - the channel might be populated with people that aren't actually there, but the conversation is much more real time. Unless you have a bouncer or web client, the chat history starts when you join the channel and ends when you leave. There's no threading (ok, maybe some of the web-based clients will do that), so even if you see a conversation from a few hours ago, you can't participate in it. At best you can start a new conversation referencing the old one. Not everyone in the channel will have that history.
I consider that lack of permanence a feature. When Google Talk came out, I loved the fact that all my chat history was saved and it was available everywhere. Now that all chat clients have that, I find myself preferring the more ephemeral/transient chats.
For someone starting out, don't go crazy adding empty accounts. Start with a small set of account like the check register or "common accounts" that have a checkings, savings, and maybe a few expenses. Start transcribing from your main or most active checking account. As you enter, you'll see and "Imbalance-USD" account get created automatically in your "transfer" column. What I found useful is to do a few of these, then switch to the accounts tab and create an account for it. Expenses like "Household", and then you can create somethng below that like Utilities. You can put all your Internet and Electricity expenses under that, of if you desire, go ahead and make sub-accounts like "Expenses:Household:Utilities:Internet". Or drop the "utilities" category altogether and embrace a more flat sty "Expenses:Internet". You can later reorganize/rename these however you want.
But once you get the first month in, you have most of your categories setup. If you start on a second month and get something new, you can let it in imbalance and come back to it a bit later. I love the autocompletion and easy account filtering/search/selection in-line.
I don't know if I do enough nowadays to really need this, but if I did, it's definitely pretty easy to work with.
Later, switched to beancount, it had a CSV importer and I tweaked some example script to do an "interactive" import. Each transaction would be presented and I could accept it as is, or modify it. If I saw a common issue, I could make a copy of the CSV and do a bulk replace, massage the data up front and quickly import.
I'm not saying you need to switch to CSV since your system is working for you. I'm mainly just agreeing that manual entry from a monthly statement can be pretty quick. But for those that are lazy like me that don't responsible balance the books each month, manually grabbing the CSVs and importing many months of statements in an afternoon can still be pretty quick. I would keep the bank statement PDFS + the "official csv" around as a sort of backup. Someone wanting to try GnuCash or any accounting software can start by downloading their statements/csvs for the last year and start punching their transactions in to get a real feel for how working with it will be.
Not a total loss, CGA was also also popular in cabinet arcade games. You can get converter boards. All the ones I've seen had 5-pin headers and you have to build your own cable.
The source is available as well, and it's also a python module, which is great if you're writing python apps. I found it rather simple to integrate inside of just about any flask/fastapi/django application.
One additional note: after setting the defaults, if you want it to take place immediately, you need to kill finder.
killall FinderWill definitely give Forklift a try.
https://play.google.com/store/apps/details?id=com.burton999....
They also have a "Storage Share" which is about the same, but you can serve static files to a group or with the public (ie, hosting videos, images, iso images).
In the US rsync.net provides the same type of (storage box) service. Hetzner's new pricing comes out much cheaper, but if sometimes it's the latency between your location and the storage location.
https://www.cnn.com/2021/11/08/homes/zillow-ibuyer-homes/ind...
I think a better comparison for NFTs is a star registry. You pay a company to name a star after you (or someone else as a gift). That company will provide a star locator chart and publish a book each year with all the star names they registered that year. You don't own the star, but you do own an certificate saying the star is named after you. Unlike an NFT though, you can't transfer the star registration to someone else.
A number of planes fly low and when I check flightaware, they're not on it. Or there's a plane that could be it, but it's flight path is heading East to West 30 miles North of me, while this plane came from the South heading North. Also, pretty much once a month or so, a pair of A10 Warthogs fly over or near our house. Last month, we had a real treat with 4 of them directly over the house, better than an air show.
So I'd like to setup 4 cameras on my tower focused skyward and have them try to catch clips of planes. I'll be looking at your work to see if I can also match those with flightaware.
https://github.com/lavie/runlike/
But I've got those migrated to docker-compose files these days and I try to start with the docker-compose file instead of going directly into testing out docker run commands.
I got my start with BBSes, lots of fond memories. There was one BBS in my area, and they had it setup to RelayNet (similar to FidoNet, but smaller). I knew when they would connect up to exchange, so I would be sure to upload my mail packet and then dial back up 5 minutes after they did their exchange to see if I had any new messages. I could send and reply to messages across the country in a matter of days.
The "downside" is that these custom responses were global, while a slackbot can be channel specific.