tallship, 4 days ago to foss

Better editors - better world :)

https://github.com/vkbo/novelWriter

#tallship #FOSS #writing #editors #novelWriter

⛵

.

tallship, 5 days ago to Horses

One of the most beautiful photographs of a horse that I've ever seen...

#tallship #livestock_photography #horses #photography @pczachurski

⛵

.

gabek, 6 days ago to random

The number of words that people self-censor in YouTube videos is out of control. I've more than once watched a video where a sentence was incomprehensible because so many words were removed.

"Tim <mute> with <mute> because of <mute> and their <mute>. Unfortunately, <mute> <mute>."

I hope those YouTubers are enjoying their "freedom" of "working for themselves" and "not having to answer to others" when making content they care about.

tallship, 7 days ago to debian

Congratulations to Andreas Tille the newly elected Debian Project Leader.

#tallship #debian #Debian_Trixie

⛵

.

tallship, 8 days ago 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 #FOSS #IRC #DCC #GUI #Quassel #Konversation #Halloy #HexChat #WeeChat

⛵

.

tallship, 14 days ago to fediverse

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

⛵

.

dimkr, 14 days ago to random

gplaces 0.19.0 is out and available on Flathub! This small #gemini client now supports Titan https://flathub.org/apps/com.github.dimkr.gplaces

lminiero, 16 days ago to random

20 years after the first themes came to me, I finally did it... My 27 minutes rock opera song on Cleopatra is now done! It's an appetizer to my upcoming "Musae" album, where it will be one of the tracks: in this EP I decided to split it in different parts for easier listening.

Bandcamp: https://lminiero.bandcamp.com/album/cleopatra
Mirlo: https://mirlo.space/lminiero/release/cleopatra-(ep)
Faircamp: https://music.lminiero.it/cleopatra/

Will soon be on Spotify/Apple Music/iTunes/etc. too.

I'd love to hear what you think, boosts welcome!

#FairTradeMusic

tallship, 17 days ago to foss

Here we go folks!

This just in, hot of the press, on the tail end of the NLnet grant and the release of Garage version 1.0 - w00t. 🤘💀🤘

https://git.deuxfleurs.fr/Deuxfleurs/garage/releases/tag/v1.0.0

#tallship #Garage #S3 #Self_Hosting #FOSS

⛵

.

dansup, 17 days ago to Pixelfed

Experimenting with separate hashtags in the @pixelfed app

Before vs After

Wdyt?

#askFedi #pixelfed #pixelfedApp #pixeldev

Hashtag buttons
Inline hashtags
Hashtag buttons

tallship, 19 days ago to retrogaming

Here's some fun stuffs!

http://www.cs.cmu.edu/~bmm/dvx.html

#tallship #Quarterdeck #DESQview/X #DOS #Retrocomputing

⛵

.

smallcircles, 19 days ago to DuckDuckGo

Typing "frozen" just now in #DuckDuckGo gives zero indication it might have anything to do with water going below zero degrees Celsius.

Sad! #HyperCapitalism

darnelltv, 21 days ago to random

Welcome to WordPress! This is your first post. Edit or delete it to take the first step in your blogging journey.

https://darnellclayton.com/2024/04/07/hello-world/

FantasticalEconomics, 23 days ago to Economics

Say it with me folks, inheritance tax.

We are entering into "the great wealth transfer" where about $5.2 trillion (that's the one with more zeros than I can count) is about to pass from the, largely undeserving, super rich to their entirely undeserving heirs.

"Research by Forbes magazine found there were 15 billionaires aged 30 or under but that none had created their own wealth, instead benefitting from huge inheritances."

https://www.theguardian.com/business/2024/apr/03/all-billionaires-under-30-have-inherited-their-wealth-research-finds

#economics #TaxTheRich #EatTheRich

tallship, 24 days ago to TeslaMotors

Whoa, Maverick, Whoa Horsey! 🐎

I Must be in the front row! 🤘 💀 🤘

#tallship #elon_follows_me #elon @elon_musk01 #I_can_haz_Cheezburgerz? 🍔

⛵

.

tallship, 24 days ago to random

Everybody loves #Bob_Ross 🤘 💀 🤘

https://yewtu.be/watch?v=y3s82WKTIfw&si=ZeCh44FhvKfZXGhe

#tallship #Jack_Black #painting #parody

⛵

.

Sandra, 25 days ago to random

Not happy with issue trackers that has a ton of required boilerplate just to suggest an issue. Users (“lusers”) who are reporting bugs are helping the project and if it’s easy for them to contribute, more bugs will be found.

Non-mandatory boilerplate prompts (“here’s where you can find the version number”, “here’s where you can find logs”) are great but it should be possible to bypass since it’s stuff that’s not always relevant, like a user finding a bug can’t submit the admin’s logs for example.

I’ve said it before but probably the biggest culture shock when working in the corporate world was that they pay for testers and UI designers while when users give such suggestions for free in the FOSS world, they get kicked in the head.

The flipside to that is when the users are coming across as entitled, that’s not right either. Users, you’re not a paying customer or employee.

tallship, 26 days ago to fediverse

An excellent expose on one of the most prolific and creative minds in the #Fediverse, and as the following article by @sean eludes to, far far beyond.

https://wedistribute.org/2024/03/activitypub-nomadic-identity/

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

#tallship

⛵

tallship, 26 days ago to random

Interesting?

https://github.com/dahlia/fedi-badge

#tallship #FediBadge #badges

⛵

.

tallship, 26 days ago to foss

More champions of the relevance of #FOSS, #Dogfooding, and deprecating proprietary close source systems like Google and Dropbox in favor of taking back the ownership of our own data, and moreover, our privacy 🙂

Yes, you can haz #Cheezburgerz 🍔

#tallship #Nextcloud

⛵

.

jacqueline, 29 days ago to random

look i dont even think flatpak is a bad idea in some cases, but this kind evangelism is just so annyoing

(from a github issue asking prusaslicer for official flatpak releases)

tallship, 29 days ago to node

@tapir

Hey Adam,

Just touching base here, I wanted to see how #Tapir is coming along and... Oh, it's been a while since the last commit.

Anyway, had some discussions with a couple of folks about it and how it's #Deno, so there's excitement there.

Do please lemme know when you've taken up that torch again - I know you wear a lot of hats :)

All the best!

#tallship #FOSS #Fediverse #ActivityPub #smolweb
You can haz #Cheezburgerz! 🍔

⛵

.

danie10, 1 month ago to linux

10 Things You Probably Didn’t Know You Could do With Nano Editor

OK, you probably do know at least one or two of these, but I’ve added the auto backup, line numbers, mouse support, and scroll bar to an alias for every time I start up nano.

See https://itsfoss.com/nano-tips-tricks/

#linux #nano #opensource #technology

phasorburn, 3 months ago to sysadmin

Settle down there, internet router. It'll be fine, take a breather.

Sat Jan 27 15:18:28 2024 daemon.notice netifd: wanv6 (17372): sh: you need to specify whom to kill

#sysadmin