tallship, 12 days ago to random

What's the words to.... How does it go? Alanis Morissette singing:

Isn't it ironic?

Jello Biafra and the Dead Kennedy's said it a bit differently with the album title "Fresh Fruit for Rotting Vegetables" - but you can, ... Extra! Extra! Read All About It Here! - Hmmmm for those familiar with the actual song, do you think that maybe Eugen is playing the character in the DK song, "Pull My Strings"?

At least he didn't choose Ev Williams to sit on his little boardgame.

https://labyrinth.zone/users/yassie_jYasberry Pi 3 Model B+ :baba_baba_yaseen: :agenderFlag: :transgenderFlag: wrote the following post Sun, 28 Apr 2024 07:57:40 +0000

Oh cool, new Mastodon official blog post! Let’s read it…

Huh… Okay… Well, that sucks for their tax status in Germany… Interesting they’re incorporating in the USA… The USA does have a very… Open… Tax regime for non-profits.

Oh, new board members!

The fourth one is COFOUNDER OF TWITTER?

God damn, Mastodon is really going corpo now, what the stars is this nonsense

Move to glitch-soc RN TBQH

tallship, 26 days ago to fediverse

The question posed was:

What were the major things that caused TCP/IP to become the internet standard protocol?

This had to be addressed, with so many people piling on and choosing that the OSI model was replaced by TCP/IP because it worked better and increased in popularity

Nothing could be further from the truth.

https://public.mitra.social/users/tallshiptallship wrote the following post Sat, 13 Apr 2024 17:34:29 +0000

DARPA Logo Defense Advanced Projects Administration
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.

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 #DARPA #IP #Internet_Protocol #Computer_History #internetworking #Internet #ARPANET #MILNET #NSFnet #Bill_Joy #BBN #UNIX #BSD

⛵

.

tallship, 1 month ago to fediverse

More than anything, the following isn't any sort of treatise on threads itself. In fact, Threads is largely irrelevant - this is an impeachment on the state of the (deprecated, monolithic silo) mentality that is somewhat pervasive in the Fediverse: That you switch one Satan for another Satan. You swap out #Sunnyvale_Syndrome silos managed by people who in no way have your best interests in mind for some masto admin you don't know anything about, regardless of their stated mission.

You're not consulted, at all, about blocks and mutes of remote users and domains (instances) that you may or may not have interests in following, connecting with, or otherwise engage. Such is indeed the prerogative of the instance admin and their so-called staff members, and truth be told, all without due consideration of your particular feelings.

A couple of notions, ...

First, Fediverse development is in a state where you can choose to migrate your account elsewhere - well, not really the history of your posts, includng graphics, etc., intact, but certainly, your follows and followers lists. Masto no longer can monopolize on keeping you put and under the thumb of what could very well be eventually revealed as some, immature, juvenile, tyrannical despot who wears the clothes of some benevolent dictator as their disguise.

Next, even with respect to the most feature complete platforms, you easily can self-host the most comprehensive amongst those - if you can install a WordPress Website, then you can install a Hubzilla or Friendica Server. You can invite your friends and family, or just leave it as a single-user instance.

If you do that, no one can tell you what is appropriate - it's your world. You make your own rules. you decide what and who you want to see and allow through your machine - Want Threads? kewl. Don't want to interact with the big bad zuckerberg wolf? Kewl - block it. It's your world.

Similarly, and I cover this often, there's no real community in selecting an existing server to join. Sure, you can choose to only watch the "local" stream, revealing just how limited and how little in common you share with most of those folks, or you can build your own streams by following the things that interest you and allow people to connect with you on your own terms. The community you have, is always ultimately going to be the community you build for yourself - not some recommended antennae designed by some admin on a Misskey fork that purports to know what you want.

Some added benefits of Hubzilla and Friendica instances are built in interoperability with other Fediverse network protocols. No, Threads is not one of those. Threads is ActivityPub. I'm talking about native communication between your account and Bluesky, or Diaspora - two very vibrant and active networks of Fediverse instances that don't even speak the same language as the old, feature starved masto platform.

I'll also post real quick, just a mention (with links this time, I've been asked to always do this) of single-user-by-design Fediverse platforms you might find quite to your liking. They vary in features and even the bells and whistles that their respective developers felt that they wanted to address, but the basic functionality is there - again, you decide for yourself what sort of community you want and what kind of blocks or mutes at the domain or user level you're interested in.

Now, let me just say, smolweb, instead of single-user Fediverse platforms, because as suitable as they are for self-hosting (often in your home on an old laptop or Raspberry Pi) as single-user instances, that doesn't have to strictly be the case with some of these:

• Snac - #^https://comam.es/snac-doc/README.html
• Bovine - #^https://codeberg.org/helge/bovine/src/branch/dev/README.md
• #^https://docs.microblog.pub/

I'm going to keep this short enough to put the emphasis on the boost of my previous post below - the important concept being that in coming to the Fediverse, it is you, who should be in charge of what and who you interact with, and not somebody else who (as evidenced recently) will pull the rug out from under you and tell you what you can and cannot do, who you can and cannot talk to, or worse than all of that, ... Will judge you.

You shouldn't take that kind of shit from anybody. You be you. You're fine just the way you are :)

https://public.mitra.social/users/tallshiptallship wrote the following post Sat, 30 Mar 2024 05:28:37 +0000

![Cover of Boardwatch Magazine from the early 90's featuring Bill Gatus of Borg - "You will be assimilated".](https://public.mitra.social/media/c30634759c1a18cff76d637f81090acf541a512b22f4affda37c4f87424e8b3d.jpg "Cover of Boardwatch Magazine from the early 90's featuring Bill Gatus of Borg - "You will be assimilated".")
@onepict

> On any online space, you should consider who you give power to. Who has the control over who you choose to associate with?

I concur 100% with this assertion.

> All that the instances who sign the fedipact are doing is signalling to some of us that somewhere is safe for folk who don't want to engage with Facebook at all.

I don't think that's all, and actually, What those instances may (inadvertently) be signalling is that they will take it upon themselves to remove the Freedom of Association from the user themselves, without prior expectation or consultation.

I don't know where "Freedom of Speech" entered the conversation, but the notion of "Freedom of Association" has indeed been taken from those who have chosen to excercise those privileges belonging to the users themselves. Waking up and realizing that you can no longer communicate and share recipes with grandma, without evern having been consulted, is an affront to the Freedom of Association - it's inclusive of an even larger issue surrounding the reasons that *smolweb and single-user and self-hosted platforms are protective of such principles Freedom of Association.

Further, it serves to create an environment (especially when so many platforms now support migration ingress) where one's Fediverse accounts are considered ever more transient, as the realization that having an account on a silo based Fediverse instance is the antipathy of #Fediverse and #DeSoc philosophies.

It also erodes the trust between the average user and administrators that you thought you could entrust with respecting your freedom of association with.

> This is a Freedom of Association issue, ...

it is indeed, and a betrayal of trust for anyone who realizes that it is the overreach by someone else to decide that you should not have the Freedom of Association that likely brought most folks to the Fediverse in the first place.

I did a little non-scientific, anecdotal survey by contacting people I know on many of the instances that arbitrarily decided to remove those freedoms from their users overnight, and discovered that many have already migrated to other instances, or are contemplating it - the interesting thing? Many of my acquaintances had already decided to, or even configured their accounts to block #Threads; but to have someone else tell them what they're allowed, or not allowed to do, is a violation of someone's freedom to choose for themselves by despot personalities who dismiss the relevance of a right to choose for oneself.

It's a simple matter, to block instances, at the domain level, from one's own user account, and on most Fediverse platforms, there's actually an announcement utility (usually only used to beg for donations) whereby administrative staff can inform their user base of their own ability to control how they themselves choose to exercise their own preferences with respect to #Freedom_of_Association.

Ironically, when perusing the stats, it's the very largest (deprecated, monolithic silo oriented) Fediverse instances (in terms of the # of user accounts and MAU) that have chosen NOT to trample upon the individual user's Freedom to Associate with whom they themselves decide.

NOTE to Fediverse instance admins: Please take under consideration the trust that has been placed in you with respect to the freedoms all individuals are entitled to determine for themselves - reach out to your user base, deploy surveys, collect votes, whatever, but please don't just decide for someone else what you decide is good for people who are NOT YOU.

Subjugation and assimilation into the Borg Collective goes both ways folks.

#AYBABTU (All Your Base Are Belong To Us)

#tallship #despotism #dystopian #authoritarianism

⛵

.

mario, 1 month ago to fediversenews

Release banner for Hubzilla 9.0
Hubzilla 9.0 is here and delivers many improvements under the hood and at the UI level. Two of the most asked features have been implemented: repeats a.k.a. boosts and adjustable theme colors at the channel and site level. Hubmins can also customize other components via the bootstrap sass variables.

Under the hood we implemented a short term object cash which will improve performance when fetching objects. The internal use of ActivityStreams1 has been deprecated in favor of ActivityStreams2. Object integrity proofs (EddsaSignatures) according to fep-8b32 have been implemented. Interesting for developers: CI and the test environment have been vastly improved.

Other notable changes are: refactored browser to browser encryption using the modern sodium crypto library and support for custom emojis with configurable emoji sets.

For a complete list of changes in Hubzilla 9.0 please refer to the changelog.

A big THANK YOU! to all contributors and everybody who supports Hubzilla and its development.

Breaking changes

• The .htaccess file has been updated to fix an issue with recent Apache versions
• Require sodium PHP extension
• Require bcmath or gmp PHP extension
• Require intl PHP extension
• Versions < 9.0 will not be able to decrypt encrypted messages composed in version 9.0 in the UI
• Poke and Mood apps removed
• Removed smiley button addon
• Removed smiley_pack addon
• Removed emojione addon (use the emoji addon instead)
• Removed fediwordle addon (use the fediquest addon instead)
• Individual connection filters need manual intervention (e.g. replace http://activitystrea.ms/schema/1.0/share with Announce when filtering repeats)

Update

1. Backup your data
2. Make sure that the sodium PHP extension is installed and enabled
3. Make sure that either the bcmath or gmp PHP extension is installed and enabled
4. Make sure that the intl PHP extension is installed and enabled
5. Execute util/udall

Install

Please refer to the install instructions.

#Hubzilla is a powerful platform for creating interconnected websites featuring a decentralized identity, communications, and permissions framework built using common webserver technology.

https://hubzilla.org

CC: @Fediverse News

tallship, 2 months ago to internet

jupiter_rowland@hub.netzgemeinde.eu

WRT your post here: #^https://hub.netzgemeinde.eu/channel/jupiter_rowland?mid=b64.aHR0cHM6Ly9odWIubmV0emdlbWVpbmRlLmV1L2l0ZW0vOGMyZDQzMjAtYTBmYy00MzljLThmOWQtOTU4ZGQzMzQ1OTQ4

and notice the last paragraph at the end of my article where mastodon is removed an replaced, here:

#^https://socialhome.network/content/14862911/iow-the-reader-doesnt-have-to-leave-their-comf/
This should cheer you up with a bit of validation for what you're conveying :)

#tallship #FOSS #Fediverse h/t to Yukio @Yohan Yuki Xieㆍ사요한・謝雪矢 @♾️ Yuki (스노 雪亮) 🐬 🌏

https://c.im/@youronlyoneYohan Yuki Xieㆍ사요한・謝雪矢 wrote the following post Sun, 03 Mar 2024 04:40:15 +0000

My SNS apps.
A screenshot of my #SNS apps as of 2024-03-03. 🤣🤣🤪🤪🤪

#SocialNetwork #SocialMedia #Fediverse + #ATproto + #Silo / #WalledGarden

tallship, 3 months ago to random

https://gleasonator.com/users/tallshiptallship wrote the following post Sun, 21 Jan 2024 04:51:16 +0000

⛵

Hey there friends :)

Um... if you take this Pepsie challenge, I promise I will never give you a Harrier JumpJet no matter how many Pepsi points you think you've earned. And I'm really only looking for a couple (two) names, Any other backstories are a total bonus.

If you're wondering, well... I'm wondering just how much we lose in the generational abstractions that occlude truths as facts or popular fictions as the years pass.

For example, I really have no grasp of why boys the age of my grandpa wanted to fuck Gracie Allen so badly - I did see a lot of George Burns' later movies, and I got to thinkin' many years ago when my dad sat me down and made me both listen and contemplate the song, "I Wish I was 18 again" by her widower.

Don't be obtuse! Of course I dismissed it, but even then as an 18 or so year old boi, I realized that at some point in my life I would realize that what my father was subjecting me to was so fucking significant (and fleeting), that I would eventually come to understand what he was conveying to me.

And now we have a clueless population of snot-nosed children yet again, for the innumerable time since time began, that is incapable of comprehending a simple paradigm - NO asshole - Not of Burns and Allen. Geez! But if you need to start there then okay, please do that.

It's like one of those little maze puzzles you penciled in the escape route for when your parents took you to one of those stupid restaraunts that had the foresight to keep the kids quiet by occupying their interests while their dinners were cooking. The alternative was others enduring the wailing lamentations of snot nosed brats who wouldn't wait patiently on their favorite dish to be plated and delivered to their table.

Well, whatev. Most folks are cowards, and your likely amongst them - but if your'e not, please feel free to accept this challenge to give me just two names - unrelated personnas that have left indellible marks upon the subtext of everyday everythings that you may not even know you invoke and stand upon the shoulders of each and everyday.

The hints are there, you can be distracted, sidelined, and offer up something other than what I'm actually looking for and even that would be most excellent!!! I'm merely hoping to help you excercise your mind, recollections, and ability to research things that are buried deep within the Dark Abcesses of your Mind.

Wanna play? I'll continue to engage you if you like, if you miss the mark, or even better, bring out aspects that I've not thought of myself as to how these things became and remain so significant to me even to this very day.

"Jim, your mission, if you choose to accept this, is..." Don't let that fucking tape self-destruct in five seconds!

Regardless, peace be with you all my friends.

#tallship #humanity #social_science #literature #history #aspirations #disappointment #levity

:sailboat:

.

tallship, 9 months ago to fediverse

Yet another example of how development in a vacuum can ultimately fail, and it's inferior to #Open_Source models of collaboration and auditing.

Some folks, you just caen't reach, lolz.

Stupid goes all the way to the 🦴 bone! You no can haz #Cheezburgerz! 🍔

#tallship #proprietary #deprecated_silos

⛵

.

https://social.sdf.org/@tallshiptallship wrote the following post Fri, 21 Jul 2023 22:25:52 +0200

The big news here isn't the headline, it's what's buried in the article itself - an article that links and clings to non #Fediverse, deprecated silo resources like Twitter to pad the results of cooperative studies between these two universities.

Of particular note is an apparent broken promise to #open_source the technology on one hand, and the infinite power that #FOSS can play when millions of eyes are on the prize with cooperative development.

https://decrypt.co/149272/chatgpts-performance-is-slipping-new-study-says

#tallship #AI

⛵

.

tallship, 9 months ago to linux

https://fosstodon.org/users/hadretFilip Chabik 👻 wrote the following post Sun, 16 Jul 2023 08:35:24 +0200

@tallship Oh man, this brought me way back. Two of my colleagues in the beginning of 2000s recommended me #Slackware as the best distribution to kick-start my #Linux journey. Initially I was sure they were trolling me as it took me good 3 months to get to the point I was able to launch X, but I’ll remain forever grateful as I learned so much because of it… To this day my muscle memory defaults to checking out man pages instead of Googling things 🤷🏻‍♂️😄