tallship

@tallship@public.mitra.social

Slackware, OpenBSD, and a bit of a Debiantard.
FOSS and Privacy Advocate. Secure, Enterprise Cloud.

This profile is from a federated server and may be incomplete. Browse more on the original instance.

simon, to random
@simon@simonwillison.net avatar

Several of the major social media platforms - Instagram, TikTok, LinkedIn, Twitter - have effectively declared war on linking to things and I absolutely hate it

"Link in my bio" / "Link in thread" / "Link in first comment"... or increasingly no link at all, just an unsourced screenshot of a page

tallship,

@simon

A couple of things there Simon. How do you know this? Are you still using the deprecated, privacy mining, monolithic silos to which you refer, or are you just taking this on the word of good, 3rd party information sources?

If it's the former, why?

If it's the latter, then yippie kai yay! The demise of these platforms is underway and in full swing - just as Steve Ballmer once called Linux "Cancer", the fact that these silos aren't simply ignoring links to particular resources, especially those in the , and have taken up with the practice of actively blocking them, is a good thing; and you, as a , should be proud.

Yet again, if it is the former, and you really insist on validating and monetizing those privacy mining silos via your subjugation as inventoried chattel there, consider pinning something akin to the following to the top of your profile (make sure to read the alt-text for the image):

tallship, (edited )

@silverpill @OrangeFren @monero

And there's also good, well formatted ActivityPub federation with these too:

⛵

.

tallship, to random

@silverpill

Not sure if you would have noticed the boost so I've pinged you on the QuotePost.

RE: https://socialhome.network/content/c94bb475-e75d-4a23-87b7-90d5d544d378/

@tallship

tallship, to foss

This comes as no surprise to anyone who's actually been paying attention over the past couple of years:

https://privacy.thenexus.today/mastodon-hard-fork/

All I can really say is, "OH Happy Day!"

Let the games begin, I'll bring the popcorn :p

@thenexusofprivacy

⛵

.

julian, to random
@julian@community.nodebb.org avatar

At the last ForumWG meeting, we discussed at length about Article vs. Note, and whether there was a desire to expand usage of as:Article. You can review those minutes here.

One of the action items that came out was to collate the state of current implementations. Unfortunately, outside of implementations that federate non-textual content (e.g. Pixelfed Stories, Mobilizon Events, etc.), the majority of implementors just use as:Note, which is not surprising given Mastodon's treatment of non-Note objects.

You can see the results of the summary here.

What is less clear is whether there is pent-up demand for use of a different data type for more richly forrmatted content. @mikedev and @jupiter_rowland provided some very illuminating history behind previous attempts to use as:Article, but importantly it seems that Mastodon (via @renchap) may be open to supporting this in some form as well.

While Mastodon has every reason to display as:Note as it sees fit, I'd like to hopefully address the undue influence towards using it especially in instances where as:Article were more appropriate. Mike (upthread) suggested a compromise:

  • that as:Note be reserved for content with attachments (images or otherwise), perhaps with a limited subset of html
  • and as:Article be used for content with a richer set of html (e.g. tables), and including the ability to display inline images

I explicitly did not specify that Note was for shorter content and Article for longer, because there exist plenty of examples of the reverse.

Does anybody see potential complications from such an arrangement?

tallship,

@silverpill @jupiter_rowland @renchap @mikedev @julian

Socialhome supports inline images in posts. Are those as:Note or as:Article?

tallship,

@silverpill @julian

Silverpill wrote:
> Could you provide an example of such post?

Here you go bro: Socialhome post w/inline images.

I'll try to give it a boost from my , , and accounts too (if I haven't already) so you can study/compare the various treatment cases :)

Sadly, I have not yet launched streams yet for study. I know, I'm a lame-O. I'll get to it shortly, prolly just spin up a local VM on Proxmox for that here, I really am anxious to give it a go :)

⛵

.

tallship, to bbs

Synchronet BBS as an node makes over a secure protocol because your exit node is the itself...

Brilliant!

But what about those users out there? How about a gzipped tarball, all nicely packaged up so you can distribute around, of a custom built client that will securely connect people to your over telnet?

Brilliant!

What was that again? Oh yeah, ... Brilliant!

Enjoy!

h/t to @dheadshot

⛵

.

tallship,

@silverpill @Hyolobrika

Hehehe.... I suppose this is my opportunity to plug Joshua's free domain name service here that's been a trusted mainstay for over 20 years :p

Perhaps one of the best parts is that you can see how many days (years) the domain has been part of the service, to dissuade concerns over whether there's a likelihood of it suddenly disappearing :)

And.... who doesn't love ?

Aside from lotech schemas, there's also several FOSS based community driven initiatives. There's been a lot of real-world, ad-hoc development since my years of participation in the IRTF/IRSG DTNRG. Full disclosure, I was also formerly employed by Semtech. The notion that there's a use case for communications that can take months, even decades to arrive (or never at all) is a valid concern for many practical applications.

More immediate, and relevant communications systems for most folks here on Terra Firma include projects like Lokinet, which has some great info HERE, and also aspires to the same level of, um... disconnectivity (sneakernet-like) or operability that @silverpill mentions above - the value of having a client/server architecture that is prepared to exploit this out of the box is much relevant that one might think.

Some of these semi-production or production ready real world initiatives and communities are:

  • CellSol - It is noteworthy to mention that Texas is the only state in the USA that sports an (actually only mostly) autonomous electricity grid (not dependent upon the national grid), although it's not publicly managed, and has been criticized as such due in part to nearly 1000 deaths occurring in the winter of 2021. The repo is HERE. Here's a PoC for one such use case from the PoV of a native Texan: Apologies for directly linking to an article in the monolithic silo space.

During my years living quite literally off-grid in the wilderness of the forested mountains in Northern California, I had the privilege of meeting and contracting for several farms and individuals deeply steeped in what is generally referred to as the prepper movement. These weren't cray cay militants (at least not most of them) or paranoiacs calling for revolution or believing the end is nigh, but rather, farmers and families who were, rightfully so, extremely concerned with security and safety for their small communities and loved ones. To survive in places like that, which exist all over the world, one must begin with self-sufficiency that covers 4 seasons; beyond that, protecting the 'me and mine' aspects of your assets and property are very real considerations.

The work I focused on led me to developing microwave surveillance systems using inexpensive, solar powered Ubiquiti Nanostations with ranges capable of exceeding 10KM, strategically placed in almost inaccessible locations overlooking entire valleys as well as within small perimeters of their farms and households. This included off the shelf PTZ cameras, many of which were capable of license plate and facial recognition, but more importantly, being able to determine the difference between things like Bears, Deer, and Humans - false positive intrusions detected are quite frustrating, lolz.

All of this was coupled together with Shinobi, which can be monitored and controlled from anywhere, on any device. The repo is here.

With the extreme threat levels of thievery and other concerns in those regions, and continuous incidents of such, a comprehensive based, powered communications and surveillance system is an in demand market. Internet access is of course, problematic in such regions, which creates the market for WISPs operating in the unlicensed microwave bands a high demand commodity as well.

This is merely demonstrative of the need for another niche type computing arena - community networks completely unconnected to the Internet:

All of these projects, protocols, and initiatives have solution based choices for the various kinds of Delay Tolerant Networking standards and communities actively developing for connectionless, intermittently connected systems, or autonomous networks that aren't neccessarily interdependant upon a classic, traditional, Internet connection.

Not sufficient to just eschew the deprecated, privacy disrespecting monolithic silos, it's also not prudent to depend upon clearnet aspects of the Internet either. In practice, it's possible to take pretty much any platform technology that listens for packets and fashion the ability to be accessible and available via I2P, Tor, IPFS Yggdrasil, and other IP routed constructs, yet moreover, the majority of people only consider intercommunication in terms of the IP routed packet switched network we call the Internet (powered almost entirely by Cisco IOS and the like), without due consideration given to the fact that this single common denominator is also a single choke point - kludgy platforms like masto that can't even keep up with the contemporary movements in the social networking landscape aren't going to fare well when it comes to the expanding horizons opening up with movements like those above, while others like Sreams, Mitra, and perhaps protocols such as Nostr that exhibit the ambitions to explore and exploit emerging technologies in communication will fare much better, adapting (and embracing layer 1 & 2 networking) along the way.

⛵

.

tallship, to foss

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?

, get it? I was rather amused. Anyway, Here it is.

h/t to: @csolisr You can haz ! 🍔

⛵

.

tallship, to random

Test post...

Gemini URI's should resolve as links:

gemini://git.skyjake.fi/

Gemini aware browsers will either open the page or launch Lagrange or other default Gemini browser

tallship, to ukteachers

About twenty five years ago, we laid out the keels for a new adventure - The Twin Brigantine project, in the parking lot of the , next to the , in the old ferry building that was, along with a pontoon bridge, obviated by completion of the connecting the mainland to .

Up until that time, 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 once again joined her sister ship, , in the pursuit of education as , 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 , a , and a - each named the .

⛵

.

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)

tallship, to fediverse

This Should be *a huge conversation in the - really.

@jupiter_rowland certainly paraphrases much of the sentiment here in the Fediverse where many conversations are taking place, albeit briefly, and then dismissed, but why? Are people too busy to care? Are people too apathetic to take seriously anything that begins with the letters, masto...? Do those 5 letters really invoke such categorical dismissiveness that cuts into topics that would otherwise likely gain immediate traction were it not for mention of that corporate monolithic silo brand?

Probably; likely; perhaps - take your pick. There is indeed a general apathy amongst especially long term Fedizens and also Lemmy users who are refugees from Reddit, but it's okay to dismiss masto as the neo-corporate EEE platform conceivably threatening the UX for millions of Fedizens. And like it or not, there does need to be a viable shitposting platform, which is exactly what masto is, inhabited in very large ways by people who, as Jupiter raises the question, "are incapable of actually engaging in textual conversation. There's something to that.

Well, is a very real concern, perhaps for the FEPs, considering there are projects that are very close in architecture to completely ignoring anything that isn't part of the W3's official specification, and that's okay.

It is, however, a misnomer that one must insert alt-text into media on the masto platform, at least at this juncture. Forcing the hand of refugees from the deprecated, , monolithic silos is yet another complication that those poor souls need to be gently nudged into accepting - but even more importantly, ... "Why".

Some popular Android clients will complain if you try to post media without also including alt-text, some have no facilities at all for doing so. This is an adoption phenomenon, slowly being rolled out, as awareness increases (awareness of the WHY - not the HowTO) with respect to the reasons it is an important design consideration.

Do people actually get unceremoniously banned for not including alt-text for attached media on masto? Yes, On some instances they do, as if it will have any affect at all on the wider Fediverse - I have heard on several occasions that this does indeed happen - there aren't many things that piss people off more than having something that is important to them getting yanked out from underneath them in rug-pull fashion than that of an , and yet childish, juvenile moderators and admins on several masto instances are truly guilty of such dystopian tyranny and abuse of privilege.

Those types of adversarial, clickish masto instances are much of the reason Fediverse gets a bad rap in some silo social networking circles, and it isn't a fair characterization, but the offensive behavior persists. More than an impetus for the deployment of , single-user instances, it is indeed primarily a masto phenomenon.

Not a pretty thing, but masto always has been a caustic cauldron of cacophony of enmity and active vitriol, and that's just one more reason to expedite the outreach programs popping up all over the place to entice the good folks to ditch it in favor of many other good social networking platforms mentioned by Jupiter in his cw-LONG article (I wish he wouldn't bother catering to those mastoblasters with that sentiment, they should at least be smart enough to see that it's more substantive than their shitposting personas are capable of parsing).

RE: https://hub.netzgemeinde.eu/item/9e481d2a-72a6-4f4a-bad8-b72cf6272327

@jupiter_rowland

tallship, to fediverse

I've been seeing this question come up time and again over the past several years, and it's understandable when you consider that often, the people asking it come from the deprecated, legacy silo space.

"When I follow someone, why don't I see their older posts?" - or some variant of that.

For example, when you follow someone on Faceplant, you see everything going back historically; because it's a silo. One theoretical host (server) with a centralized database that everyone using that host/service has in common.

When you follow someone in the , you begin to see their posts in your timeline/feed moving forward from the point in time that you follow them, because we're talking about the database local to the Fediverse server instance where your account is.

Okay kiddies, let's be real careful with this - again, Be really mindful, and especially careful here. You can accidentally DoS your box very easily if you're not, but here's a useful tool for those occasions where you want a history you might not normally have:

https://github.com/AdamK2003/masto-backfill

tallship, to foss

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".

⛵️

.

tallship, to random

Dits and dahs are still alive and well in maritime amateur radio...

https://www.theatlantic.com/magazine/archive/2024/04/ann-hermes-morse-code/677468/?utm_source=pocket-newtab-en-us

Another feel good story :)

⛵

.

tallship, to random

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?

https://pa2.freeshell.org/pa2/Retirement/Retirement.html

h/t to @pa2 for sharing :)

⛵

.

tallship, to random

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 companies that you already gave it to for free?

⛵

.

RE: https://fosstodon.org/users/RTP/statuses/112018299149948961

@RTP

tallship, to fediverse

Okay I thought I'd share this recent post here on the . 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.

So first, the question, posed HERE.

And my answer follows below:

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.

I highly recommend that you take a look at this excellent resource explaining the OSI model.

tl;dr:

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.

Enjoy!

⛵

.

tallship, to foss

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

https://bugs.quassel-irc.org/projects/quassel-irc/wiki/Migrating_from_Monolithic_to_Client+Core - just ain't gonna cut it right now.

I still love HexChat.

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?

⛵

.

tallship, to aitools

lolz....

Yes, I recall Sandra Bullock telling Sylvester Stallone:
"All restaurants are Taco Bell Now!"

⛵️

.

RE: https://mastodon.social/users/_elena/statuses/111923753460975543

@_elena

tallship, to privacy

is a goal, not a promise. As far back as I can remember, forums like those supporting and 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 is EVER completely, 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!"

https://www.city-journal.org/article/signals-katherine-maher-problem

⛵

.

tallship, to fediverse

First, Mostr, the bridge between and .

Next, Bridgy Fed, the Fedivese bridge between ActivityPub and .

:)

So Ryan, thank you for this most valuable tool to bring people around the globe together in - creating (and curating, as you have) ***Bridgy_Fed is one of the very best things that the Fediverse has to offer people on both sides of the protocol divide, and I really don't think that there are enough Thank you's to go around for all of the selfless effort you've put into this service.

So as meek and perhaps insignificant as it may sound, THANK YOU!

⛵

.

RE: https://fed.brid.gy/r/https://snarfed.org/2024-05-20_53092

@snarfed.org@snarfed.org

tallship, to random

More great news on the front - remote access for and Home based networks as simple as a single apt install command!

Give it a try today and let us all know what you think! I'm interested in hearing your thoughts and experiences with this invaluable remote access tool.

https://www.raspberrypi.com/news/raspberry-pi-connect/

@Raspberry_Pi

⛵

.

tallship, to random

Content from Socialhome boosted or quote-posted in Hubzilla looks really nice and the inline media of articles is preserved as presented in the original post as well - very nice!

RE: https://zotum.net/hq/d071a370-de40-5298-92d7-3f19b88d0717

tallship, to fediverse

Thanks for this Gregory :)

I'm sure a lot of folks will be interested in what you've been doing toward this rollout of groups on

@tallship. @grishka

⛵

.

RE: https://mastodon.social/users/grishka/statuses/112378383977893952

@grishka

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • JUstTest
  • GTA5RPClips
  • DreamBathrooms
  • cubers
  • mdbf
  • everett
  • magazineikmin
  • Durango
  • Youngstown
  • rosin
  • slotface
  • modclub
  • kavyap
  • ethstaker
  • provamag3
  • ngwrru68w68
  • thenastyranch
  • cisconetworking
  • khanakhh
  • osvaldo12
  • InstantRegret
  • Leos
  • tester
  • tacticalgear
  • normalnudes
  • anitta
  • megavids
  • lostlight
  • All magazines
    •