There's a new kid on the block - and there's no punches being pulled here either - I would love if some of the folks could weigh in here with their thoughts about the developer's observations...
But what about those #MS_Windows users out there? How about a gzipped tarball, all nicely packaged up so you can distribute around, of a custom built #PuTTY client that will securely connect people to your #Synchronet_BBS over telnet?
Okay it's one of those, "What's peculiar here?" kinda things.
Consider the source itself. And I certainly don't mean code of any sort. 'Why' would 'They' cite Wikipedia, as good a resource as anyone might think it to be?
Why not cite yourself? Instead of citing someone else - who will merely turn right around and cite you as the ultimate source reference?
I've seen this on four social networks in the #Fediverse now in just over a week - #ActivityPub, #ZOT, #nostr, and #Movim/XMPP. These memes are going around, but what about those privacy disrespecting, deprecated legacy silos like #Faceplant, #Twitter, and #InstaSPAM or #Reddit - Why is it that we're preaching to the choir instead of to the sinners of the #SunnyVale_Syndrome?
Go forth, save those poor souls over on the silos, Tell them that they're pork bellies. Muahahaha!
Up until that time, #LAMI operated and sailed the 70' gaff-rigged topsail schooner, Swift of Ipswitch (previously James Cagney's personal yacht) for it's youth sailing program. It took a few years to complete the Irving and Exy Johnson, sister Brigantine vessels built and outfitted by dozens of volunteers over the duration of the program. At some point, another gaff-rigged schooner was borrowed and enlisted, the136' Bill of Rights filling the need for accommodations of a youth sailing program that had greatly expanded over time, with many ups and downs, achievements and disappointments, but building two square rigger tall ships for and by a non-profit organization dedicated to youth educational programs for the community, a truly novel pursuit, eventually came to a close as a great success.
This photo shows the 113' brigantine Irving Johnson, on 23 March 2005, and which, after less than three years of service, she had run hard aground on a sandbar following several storms that affected local charts, leaving them partially obsolete - in short, on her way into the Channel Islands harbor, well... sadly, the pic speaks for itself.
Another year and two million dollars later to repair structural damages and flooding, the #Irving_Johnson once again joined her sister ship, #Exy_Johnson, in the pursuit of education as #school_ships, something that Irving and his wife Exy (Electa), following no less than 7 circumnavigations together, pioneered and championed in the 20th century aboard their three successive sailing ships - a #schooner, a #brigantine, and a #ketch - each named the #Yankee.
This image or file is a work of a United States Coast Guard service personnel or employee, taken or made as part of that person's official duties. As a work of the U.S. federal government, the image or file is in the public domain (17 U.S.C. § 101 and § 105, USCG main privacy policy)
Finally, someone understands the value of requiring someone to pay "SOMETHING", in order to alleviate #Spam and hold people posting their thoughts accountable as the individuals that have done so.
It's a proven concept by the #Stellar Foundation that has proven that even some pittance of monetary consideration breaks Spam because Spammers follow the path of least resistance (zero cost).
The captain's gig on the Glenlee, Glasgow's tall ship. A replica of the original, this small boat was the captain's personal transport and would have been used by him to go ashore when at anchor, visit other ships or to check out potentially dangerous routes through shallow coastal waters.
If Substack is perfect for your needs then use that. Your problem with substack prolly isn't who else uses it, but rather, that you yourself are calling a proprietary, privacy disrespecting deprecated monolithic silo a "Perfect solution".
Instead of doing what's right, and for the right reasons, you eschew dogfooding on #FOSS when you should be championing it, and call a professional data mining haven perfect, when it is anything but.
Well, you're already on the Fediverse, so you should know better, but I'll dispense with the lecture now and point out a few good FOSS solutions that are Fediverse powered (and one that isn't, but still rocks as a publishing platform) for you:
Option #1, #WriteFreely, which you can find over at its git repo under https://gitHub.com/writefreely/writefreely.
Option #2, deploy yourself a #WordPress site, Then install the #ActivityPub plugin - the latest release publishes into the Fediverse and allows any Fediverse account to reply/comment threads natively - like I'm responding now. It also allows anyone on the Internet to join the discussions as well. WordPress has many options for subscriber lists, Etc., as well as #paywalled#digital_downloads, if you like.
Option #3, #Mitra is a Fediverse publishing platform that currently supports paid subscriptions for Authors: https://mitra.fediverse.observer/list - pick one that has open registrations or self-host yourself, like all of the other solutions here :)
If you're really talking about maintaining subscribers lists, but especially Having a subscriber list and building it up, then most ignorant folks would recommend HubSpot - but they would be wrong, because you can get the same powerful inbound marketing solution / #CRM, only better, for #FREE (That's a bare minimum savings of over $500/month)!!! So install #Mautic and let it do what it does, which you can get here: https://www.mautic.org/download/source-code and then after that, use it in conjunction with the following FOSS application that was tailor made for exactly what you're asking for...
#Ghost is FOSS, and in conjunction with an inbound marketing platform like Mautic is the perfect dynamic duo - like Batman and Robin. But even better, is that I'm going to point you towards a #HowTo that is an actual cookbook #tutorial written by someone expressing the same lamentations as yourself, and here's the exact solution they've provided for you:
By the way, your Mautic server also integrates directly with#MailGun (or Sendgrid, SendinBlue, SparkPost, etc.) to complete your transactional email system that will tell you when each and every recipient received, viewed (and or how long) your emails, as well as how many times they looked at those emails, with a bunch of other tools as well.
I hope that helps, and I'm very glad that you came to your senses about not using a privacy disrespecting, proprietary closed source solution like Substack - besides, registering your own domain name would have hidden the fact that you were using substack anyway, so it's about YOU doing the right thing the right way. Please choose your software in the future based upon the freedoms and ethics it offers in serving you and your customers. There's evil people everywhere, and the smart ones are using FOSS too - not substack.
#e2ee is a goal, not a promise. As far back as I can remember, forums like those supporting #Enigmail and #gpg were staffed with volunteers from the privacy community who repeatedly insisted on answering questions, like, "Is <this> (whatever this might be) totally secure?" with stock questions like, "What is it that you consider 'totally secure?" or answers such as, "Secure is a relative term, nothing is completely secure, how secure do you need your mission's communications to be?"
Phrases such as, reasonably secure should be indicators of how ridiculous it is to assume that any secure platform isEVERcompletely, and totally secure.
That begs the question, "Exactly how secure do you require your communications to be?" The answer is always, ... relative.
Which means that you should always believe Ellen Ripley when she says, "Be afraid. Be very afraid!"
@mike 's contributions to #FOSS and #DeSoc go back much further than just the #ActivityPub portions of the Fediverse, well over a decade in fact, as the creator of #Mistpark, now #Friendica, and also #Zot6 and #Nomad, which promises to be a show changer for identity in the world of Social communications.
Prolly explains why, everytime I felt burnt out and sought out a different career path, then threw the switch and continued to clackity clackity clack down that other track...
I always came back. In fact, Looking back, it should have been obvious - why would someone go to bed with a technical journal or some textbook on IT by choice when they've left (or so they thought) that career for a new and unrelated one?
Really now, why do people stubbornly adhere to the belief that Government entities require warrants to determine anything about you - like, where you are at this particular moment or the GPS coordinates of your location last Tuesday at 17:42hrs UTC? ... And pretty much anything else you can dream up about yourself: The content of conversations with others, everything you've purchased at anytime, what you are likely to eat for dinner this coming Friday, your medical records; you name it!
All without a warrant, even for local law enforcement.
And why would they bother, when they can just buy it from the#privacy_miningcompaniesthat you already gave it to for free?
Going back to Konversation for GUI stuffs. DCC file send/receive is kinda important to me. For everything else, including a lot of Matrix usage, WeeChat is still the Kewlist :p
Honorable mention goes to Halloy, which I think looks really good, supports tiling, and says it supports DCC Send - I don't mind manipulating config files by hand, and I might check it out with a FlatPak, but if I'm sufficiently impressed it looks like I'll have to build the .deb and SlackBuild myself, ... Well? Somebody's got to! Right?
Okay I thought I'd share this recent post here on the #Fediverse. To give it some context, it's an answer to a common question, often a misunderstanding (even by many knowledgeable folks) as to just how we got here.
There's a lot of apples and oranges here. And everyone had a lot of good points made, but your question is simple, and has a very simple answer. I'll endeavor to address that directly, but do need to tend to some of what has already been said.
Scroll down to the tl;dr for the succinct answer of your question
Ethernet, ARCNET, Token Ring, Thick net (RG-59), Thin net (RG-58 A/U), and UTP (Cat 3, Cat 5, and Cat 6 unshielded twisted pair, Etc.) really have zero bearing on your question insofar as IP is concerned. All of these specifications relate to the definition of technologies that, although are indeed addressed in the OSI model which is indeed very much in use to this day,but are outside the scope of Internet Protocol. I'll come back to this in a minute.
It's quite common to say TCP/IP, but really, it's just IP. For example, we have TCP ports and we have UDP ports in firewalling. i.e., TCP is Transmission Control Protocol and handles the delivery of data in the form of packets. IP handles the routing itself so those messages can arrive to and from the end points. Uniform Data Protocol is another delivery system that does not guarantee arrival but operates on a best effort basis, while TCP is much chattier as it guarantees delivery and retransmission of missed packets - UDP is pretty efficient but in the case of say, a phone call, a packet here and there won't be missed by the human ear.
That's a very simplistic high level-view that will only stand up to the most basic of scrutiny, but this isn't a class on internetworking ;) If you just want to be able to understand conceptually, my definition will suffice.
Networking (LAN) topologies like Token Ring, ARCNET, and Ethernet aren't anywhere in the IP stack, but figure prominently in the OSI stack. I'm not going to go into the details of how these work, or the physical connection methods used like Vampire Taps, Thin net, or twisted pair with RJ-45 terminators, but their relationship will become obvious in a moment.
The OSI model unfolds like so, remember this little mnemonic to keep it straight so you always know:
> People Don't Need To See Paula Abdul
Okay, touched on already, but not really treated, is the description of that little memory aid.
> Physical, Data Link, Network, Transport, Session, Presentation, and Application layers (From bottom to top).
The physical and Data Link layers cover things like the cabling methods described above,and you're probably familiar with MAC Addresses (medium access control) on NICs (network interface controller). These correlate to the first two layers of the OSI stack, namely, the Physical (obvious - you can touch it), and the Data Link layer - how each host's NIC and switches on each LAN segment talk to each other and decide which packets are designated for whom (People Don't).
In software engineering, we're concerned mostly with the Session, Presentation, and Application layers (See Paula Abdul). Detailed explanation of these top three layers is outside the scope of this discussion.
The Beauty of the OSI model is that each layer on one host (or program) talks to exclusively with the same layer of the program or hardware on the other host it is communicating with - or so it believes it is, because, as should be obvious, is has to pass its information down the stack to the next layer below itself, and then when it arrives at the other host, it passes that information back up the stack until it reaches the very top (Abdul) of the stack - the application.
Not all communication involves all of the stacks. At the LAN (Local Area Network) level, we're mostly concerned with the Physical and Data Link layers - we're just trying to get some packet that we aren't concerned about the contents of from one box to another. But that packet probably includes information that goes all the way up the stack.
For instance, NIC #1 has the MAC: 00:b0:d0:63:c2:26 and NIC #2 has a MAC of 00:00:5e:c0:53:af. There's communication between these two NICs over the Ethernet on this LAN segment. One says I have a packet for 00:00:5e:c0:53:af and then two answers and says, "Hey that's me!" Nobody else has that address on the LAN, so they don't answer and stop listening for the payload.
Now for Internet Protocol (IP) and TCP/UDP (Transmission Control Protocol and User Datagram Protocol):
IP corresponds to Layer 3 (Need) - the Network Layer of the **OSI Model.
TCP and UDP correspond to Layer 4 (To) - the Transport Layer of the OSI model.
That covers the entire OSI model and how TCP/IP correspond to it - almost. You're not getting off that easy today.
There's actually a bit of conflation and overlapping there. Just like in real life, it's never that cut and dried. For that, we have the following excellent explanation and drill down thanks to Julia Evans:
Layer 2 (Don't) corresponds to Ethernet.
Layer 3 (Need) corresponds to IP.
Layer 4 (To) corresponds to TCP or UDP (or ICMP etc)
Layer 7 (Abdul) corresponds to whatever is inside the TCP or UDP packet (for example a DNS query)
You may wish to give her page a gander for just a bit more of a deeper dive.
Now let's talk about what might be a bit of a misconception on the part of some, or at least, a bit of a foggy conflation between that of the specification of the OSI model and a Company called Bolt Beranek & Newman (BBN) a government contractor tasked with developing the IP stack networking code.
The TCP/IP you know and depend upon today wasn't written by them, and to suggest that it was the OSI model that was scrapped instead of BBN's product is a bit of a misunderstanding. As you can see from above, the OSI model is very much alive and well, and factors into your everyday life, encompasses software development and communications, device manufacturing and engineering, as well as routing and delivery of information.
This next part is rather opinionated, and the way that many of us choose to remember our history of UNIX, the ARPANET, the NSFnet, and the Internet:
The IP stack you know and use everyday was fathered by Bill Joy, who arrived at UC Berkeley in (IIRC) 1974), created vi because ed just wasn't cutting it when he wanted a full screen editor to write Berkeley UNIX (BSD), including TCP/IP, and co-founded Sun Microsystems (SunOS / Solaris):
> Bill Joy just didn’t feel like this (the BBN code) was as efficient as he could do if he did it himself. And so Joy just rewrote it. Here the stuff was delivered to him, he said, “That’s a bunch of junk,” and he redid it. There was no debate at all. He just unilaterally redid it.
Because UNIX was hitherto an AT&T product, and because government contracting has always been rife with interminable vacillating and pontificating, BBN never actually managed to produce code for the the IP stack that could really be relied upon. In short, it kinda sucked. Bad.
So! You've decided to scroll down and skip all of the other stuff to get the straight dope on the answer to your question. Here it is:
> What were the major things that caused TCP/IP to become the internet standard protocol?
The ARPANET (and where I worked, what was to become specifically the MILNET portion of that) had a mandate to replace NCP (Network Control Protocol) with IP (Internet Protocol). We did a dry run and literally over two thirds of the Internet (ARPANET) at that time disappeared, because people are lazy, software has bugs, you name it. There were lots of reasons. But that only lasted the better part of a day for the most part.
At that time the ARPANET really only consisted of Universities, big Defense contractors and U.S. Military facilities. Now, if you'll do a bit of digging around, you'll discover that there was really no such thing as NCP - that is, for the most part, what the film industry refers to as a retcon, meaning that we, as an industry, retroactively went back and came up with a way to explain away replacing a protocol that didn't really exist - a backstory, if you will. Sure, there was NCP, it was mostly a kludge of heterogeneous management and communications programs that varied from system to system, site to site, with several commonalities and inconsistencies that were hobbled together with bailing twine, coat hangers, and duct tape (for lack of a better metaphor).
So we really, really, needed something as uniform and ubiquitous as the promise that Internet Protocol would deliver. Because Bill Joy and others had done so much work at UC Berkeley, we actually had 4.1BSD (4.1a) to work with on our DEC machinery. As a junior member of my division, in both age and experience, I was given the task of, let's say throwing the switch on some of our machines, so to speak, when we cut over from the NCP spaghetti and henceforth embraced TCP/IP no matter what, on Flag Day - 01 January 1983.
So you see,the adoption of Internet Protocol was not a de facto occurrence - it was de jure, a government mandate to occur at a specific time on a specific day.
It literally had nothing to do with popularity or some kind of organic adoption, the erroneously described, so-called demise of the OSI model, or any physical network topology.
DARPA said 01 January 1983 and that's it, and that was it - Flag Day.
Sure, it took a few days for several facilities to come up (anyone not running IP was summarily and unceremoniously cut off from the ARPANET).
And one also needs to consider that it wasn't every machine - we only had some machines that were Internet hosts. We still had a lot of mainframes and mini computers, etc., that were interconnected within our facilities in a hodgepodge or some other fashion. Nowadays we have a tendency to be somewhat incredulous if every device doesn't directly connect over IP to the Internet in some way. That wasn't the case back then - you passed traffic internally, sometimes by unmounting tapes from one machine and mounting them on another.
There was a lot of hand wringing, stress, boatloads of frustration, and concern by people over keeping their jobs all over the world. But that's why and when it happened. Six months later in the UNIX portions of networks we had much greater stability with the release of 4.2BSD, but it wouldn't really be until a few years later Net2 was released that things settled down with the virtually flawless networking stability that we enjoy today.
8 years ago today (yesterday, actually), 20 September, 2015, when I was a contract engineering mgr for GoDaddy in #Culver_City - a company they had just acquired in the process of an #IPO.
I'm not quite sure how that all works, but everytime I get in the middle of one of those, all the C-Level folks and those who hired me disappear a few days later, buy #yachts and #islands, and I end up being one of the big bosses working for bunch of people I never meet, lolz.
Reprinted from the Fediverse-City Matrix room, with permission from the author (myself):
I was just participating in another discussion elsewhere on the connotations and perceptions relating to a global feed of the entire known Fediverse, as it pertains to what various platforms call it (in their selector tabs).
Lots of suggestions, and every platform uses a different nomenclature. Some use 'global', some use 'live', and there's a few others as well that try to convey that type of extremely busy feed.
But then I touched on the subject of Local feeds - not all Fediverse platforms utilize this type of concatenated feed. I related that the Hometown fork of mastopub was [at least one of] the first to incorporate this as both a feed, and a type of post that is localized to only that particular instance.
I also, because I've read his contention, included the Dev's reasoning on having such a utility as a feature - because he intended Hometown to be a Fediverse platform that could encourage a Highly localized "community".
So you can select the other various, common types of scope for a post when making a post, as well as posting something that is only viewable to other users on your local instance - thereby supporting the 'local community only' aspect that has eluded and mostly deluded users on other platforms.
Why "deluded", because having a Fediverse account in the minds of most folks coming from the deprecated, monolithic silo space is something that has been heavily promoted by Fedizens as one of the reasons why it's better to use the Fediverse instead of those impersonal deprecated silo systems.
And that's simply not true.
Take me, for example. I have several accounts and interact using them with different circles of people (I won't get into the power of recursive circles as they were implemented in gplus). So I'mma just use mastodon.social, one of the biggest monolithic-like silo instances in the Fediverse, as an example here.
People there, most often n00bs from the November Rain or later) talk about the sense of "community" they have there, when they're really only speaking of the connections they have by following and being followed by not just people on that instance, but across the entire Fediverse.
The sense of community that almost everyone in the Fediverse perceives is mostly a compilation of the follows and followers that they each have, and is unique to themselves alone.
For example, I prolly know 4 or 5 people on each instance I have an account on. My community is comprised almost entirely of the direct connections I have made with others across the Fediverse at large, and yes, people on platforms with 'local-only' feeds to see my posts, know them to be local, but so do folks on other instances watching their 'global feeds' (or home feeds where someone they follow includes a follow of my account).
So to me, in my experience, my community is comprised of those who I've made connections with and the people they are connected to, with very little traffic from the local instance I am on at any given time.
To think that you're going to have a community on mastodon.social consisting of people primarily from that instance is a bit naive, IMO, coz your default feed grows exponentially with foreign user's posts the more you connect with anyone - not just the people you follow that are local to your instance. You see something, you interact because it's interesting, pertinent, or relevant to you - you don't do that because you've discerned that you will only interact with local accounts... that just ain't natural, human tendency.
So the creator of the Hometown fork realized that one type of vehicle in the feature set to mark this kind of delineation was that of the ability to post and see in your feed, local only posts, with the overt assertion that Hometown is a fork that in part, is a platform that can facilitate the social diaspora consisting of a 'mostly local' community.
Even entire instances, named or stated as localized geographically or topically, as having publicly open registrations miss this mark in a big way - people for whatever reason, want a Fediverse account, pick a host/instance, by whatever criteria, and then inadvertently end up creating their own diaspora of social connections across the entire Fediverse anyway.
nostr, Bluesky (when it eventually fully supports other instances), Threads (yeah, I know, it's a bastard, lolz), Minds, and other, bigger instances or monoliths, don't try to capitalize on this notion of "Your instance is your community" because overwhelmingly, it just isn't the case in reality.
I'm not saying that there aren't Fediverse instances are successful in cultivating small communities consisting of connections with others on those particular instances, but the most successful of those are the instances that have actually disabled Federation on those instances, lolz.... There's lots of examples of that, which is kewl - to each their own.
But the tendency of everyone to follow the Ew! Shiny! paradigm of simply liking and following what you like irrespective of whether it's on your local instance or not is the lions share of how people interact with each other.
Your thoughts, observations?
Attached graphic attrib: A Jack Russell, happy as can be, sitting in the pilot's seat flying a Cessna, not knowing WTF he's doing.... but he's really happy! The caption reads: "I have no idea what I'm doing".
We went for a pleasant 90 min cruise on the Lady Nelson this afternoon. I pulled on some ropes to raise/lower sails as well, because what pirate wouldn’t partake in sailing the ship?