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.

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, 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 privacy

#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 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 #encryption #PGP #secure_communication #Privacy #FOSS

⛵

.

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 #Smithereen

#tallship #FEP #Fediverse #ActivityPub @tallship. @grishka

⛵

.

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

@grishka

tallship, to foss

I'm unable to pull this up and boost here. Was able to get the whole stream on a Glitch-soc box np, and I can follow the curator here too, but I'm too tired to try testing on Hubzilla or Friendica at the moment; so I'll just post the link then, which may be of interest to some, ... Actually, I suspect, many.

We've had some discussions about this over in the Fediverse-City Matrix room, Where Ryan is also a participant. It's apropos of the recent onboarding with respect to Flipboard curators and also the nacent interoperability we're experiencing with Bluesky's ATP.

Baby steps folks, baby steps, as they say ;)

Building Bridges to the Fediverse, with Bridgy Fed’s Ryan Barrett

I'm interested in hearing any feedback you may have to offer and as always, boosts are welcome :)

#tallship #FOSS #Fediverse #ActivityPub #bridges #interprotocol_federation #ATP

⛵

.

tallship, to random

Fricken' Poettering's at it again.

⛵

.

RE: https://fosstodon.org/users/CwalkPinoy/statuses/112370934116723206

@CwalkPinoy

tallship, to browsers

After several years of warning after warning after advisory after advisory and calls to repeatedly update or remove and NOT USE CHROME by the Department of Homeland Security, it should be inconceivable that anyone does - but they do.

Sometimes these are patched with automatic updates before horrific and catastrophic results occur, sometimes not. To be frank, part of the problem stems from the fact that Chrome is the largest attack surface out there where browsers are concerned, but notwithstanding it being the fav target are also serious privacy concerns that aren't shared by other chromium based browsers.

To be fair, many exploits are indeed shared by other chromium based browsers, but not most, while some are related to other browser capabilities, like WebRTC, but it's still best to just ditch Chrome and never look back.

Here's more coverage on vulnerabilities issued less than a month ago. It took 3 seconds to bring this up, and no, not using Google, which didn't reveal this when I tried that search engine in a subsequent search, lolz. Why would they return SERPs that poo poo their own product?

This one did come up in a google search

There's truly only one way to ensure safety - unplug. But there's a lot of simple things you can do to exact a reasonable level of security, so why not observe some of those best practices? It's not like it will cramp your style.

Anyway, that's my two cents. h/t to @darnell for raising awareness of this latest brokewell. Make sure you take the time to visit the link he's provided for you too.

There are plenty of that run on (to name a few, alphabetized):

  • Brave Browser
  • Chromium
  • DuckDuckGo
  • Firefox
  • Kiwi
  • Vivaldi

IMO, No one should be running Chrome - Desktop or otherwise. It's a privacy nightmare even when there aren't CERT warnings circulating.

⛵

.

RE: https://one.darnell.one/users/darnell/statuses/112371221294882180

@darnell

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

⛵

.

tallship, to random

https://zotum.net/display/3c82070b-19d3-4cfb-a6d9-6e09b9ecf102

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 foss

Still resonates to this day. was a big deal. For a long time.

⛵

.

RE: https://social.sdf.org/users/tallship/statuses/111501910747814277

@tallship

tallship, to history

A few dollars, even that little if that's all that you can, will be greatly appreciated and goes to a tangible cause with a finite timeline. I cannot speak to what will happen to the original archival material following digitizing, but paper does have an expiration date, so the sooner anyone is able to step up with anything the sooner Jason can get back to the business of preservation.

Links are in the article linked below.

⛵

.

RE: https://mastodon.archive.org/users/textfiles/statuses/112323615004071766

@textfiles

tallship, to foss

A new version of has been released - w00t!

Not a complete feature set of Markdown, but certainly good enough for most purposes. You should give it a good look. If you're looking for a light markdown editor, one that works with bits and pieces as well as complete chapters in books, focuses on the text and authorship in a distraction free environment, then novelWriter might just be right up your alley!

@novelwriter

⛵

.

tallship, to fediverse

This is an example of a marketplace listing in Flohmarkt.

What "I" did here...

  • Went to the "All" tab over at Flen's Market - Much like PeerTube, there's a Home, Local, and All tab, the latter of which includes items from other instances that you've manually federated with within the radius you've specified from your location.
  • Next, there's a choice to make if you're interested in an item. You can register for a local account (I don't see any reason to do that unless you want to post a listing on that particular server), or you can remotely add yourself (like I did). Since the remote features don't quite seamlessly work with Mitra, I tried this from a masto server - no joy. I tried it from another masto server (a masto fork) - no problem this time, even on an older version of masto. That was humorous to me, as I've a bit of disdain for mastopub servers and found it amusing that even some of the instances running the very latest version of masto won't work, while older one's based on forks do; but I've got a twisted sense of humor.
  • So next, you can engage with the seller directly from your local instance on most Fediverse platforms (support is added for various additional Fediverse platforms all the time). In this case, (visible because I chose the "All" tab), the particular item was from yet another server elsewhere - this is a very nice feature, like !!!
  • From there, once you boost the item in the listing, others can see it in their streams, boost it further, make arrangements directly with the seller, etc. Kinda Kewl.

This is different from how most other attempts to deliver a marketplace into the . Usually, what I've seen is someone trying to integrate the functionality local to a platform, which networks (via ActivityPub federation) only with other like platforms. That's not a Fediverse solution - that's a platform solution and leaves everyone else on the fediverse not running that particular platform disenfranchised.

For example, using the Epicyon server platform as an example, it is first to be understood that this particular server platform is designed for very small numbers of user accounts per each instance. You also have to manually contact the admin of remote Epicyon servers yourself (or be contacted by them), then mutually agree to federate each other's marketplaces separately and distinct from any wider federation configurations your server has. Considering the inconveniences with locating other Epicyon instances that may or may not have enabled and made use of their marketplaces and establishing a mutual publishing agreement, coupled with the likelihood that each of your instances between 1 and 10 users, posting an item in the marketplace has a pretty high probability of being more effort than its worth - especially since it dosn't federate with any other Fediverse platforms.

Others follow a similar design, but also generally operate like normal federation using a blacklist method, as well as being able to accommodate potentially hundreds, or even thousands of users per each instance (yeah, I know, semi-monolithic); so even if those marketplaces didn't already automatically federate across the Fediverse with all instances of other like server platforms, it's still a huge improvement over the previously discussed smolweb platform's model.

But they're still not Fediverse wide...

This is where Flohmarkt really starts to shine - it's fully Federating (Still a WIP wrt some platforms - see the wiki for particulars) across the entire portion of the Fediverse.

You can check for the latest particulars on Flohmarkt's current Federation status if you're interested in your particular Fediverse platform and level of interoperation with Flohmarkt instances.

I do have some criticisms of the particular functionality in federating that the developers have chosen to incorporate, however. Basically, The server admin still needs to manually federate item listings between the local instance and other remote Flohmarkt servers. It doesn't need to be this way however, but one must concede that after going over the documentation and seeing that the concern's of the dev team are over unchecked spam, phishing, poor quality ads, etc., I find it to be a very reasonable concern, although I'm still not comfortable with how the Dev team has hard-coded this conditional into the server's capability, when a slightly different approach might afford self-hosters much greater flexibility and incintive for adoption; namely:

  • Make the current model the default
  • Enable other configurations for federating between other Flohmarkt servers (and eventually, other platform marketplaces) via either simple configuration files, runtime arguments, or via a GUI in an admin control panel, including that of an uninhibited fully blacklist model of sharing listings between Flohmarkt servers.

I generally tend to think that hard-wired, opinionated configuration choices are a less than ideal (usually bad idea) than acknowledging issues surrounding such decisions and then choosing a default while affording server admins (or users themselves) of being able to manage the options for themselves. This is one of those cases where I feel it could make a huge difference in the viabilty and adoption potential for this, "Strictly Federating Marketplace" Fediverse platform.

The other (very minor) criticism I have for Flohmarkt is the pin & string radius solution as it is currently implemented:

  • It's determined by the server admin, instance wide
  • It's determined by the server location, or some other arbitrarily decided locale

The radius is a great idea, but I think the following would go a long way towards improving the utility of this feature set:

  • The server admin decides whether to enable user-level radius configs or server level, as is the case at this time.
  • Local users determine, and have control over whether an established is applied to either their entire user profile's repertoire of items listed, or on a per item basis.
  • If he user chooses a per item radius, each listing could have a different radius established.
  • The local users have location radius specifications that can be based on different criteria, such as pinning a location on a map of their choice, by country (the free IP2Location databases can accommodate this behavior).
  • The user's particular radius settings for each listing must be preserved and observed by all federating remote Flohmarkt server instances (but not by individual remote user shares/boosts, which should remain unrestricted).

This Radius feature is extremely powerful and I think that every effort of the development team to exploit the potential of this feature set should be a major consideration. Eventually, Flohmarkt servers will federate with other server platform types, exchanging listings between say, Flohmarkt servers and Friendica servers, etc.. but the awesome power unleashed through following and boosting capabilities that are already fully available to remote users to share with others holds the potential at this very time to make Flohmarkt item listings ubiquitous across the entire Fediverse, ... And that is really kewl :)

Well, I'd rather tease your interest and see you go checkout more for yourself rather than feed you everything you wanna know about a really kewl communications tool - you really should experience how kewl it is for yourself.

I couldn't locate a support room for Flohmarkt like most contemporary software products maintain in the FOSS world, but the more traditional irc chan at is readily available, and of course, there's the issue tracker at the Codeberg repo I previously linked to above.

What are your thoughts and impressions on this novel approach to embedding the marketplace commerce structure into potentially everyone's social streams in the form of both a dedicated platform and as passive feeds via the intervention of other who share and boost individual items and listings in Flohmarkt?

I hope that helps! Enjoy!

? 🍔
@grindhold @me @flohmarkt_support

⛵

.

RE: https://fedi.markets/users/Yonggan/items/f7f7f8d1-6279-4249-890a-bdd97340d218

@Yonggan

tallship, to fediverse

Ghost is an excellent platform for publishing. I used it a lot a few years back for publishing articles when it was headless - that was optimum. Compose at your leisure within your own local environment, then push it up to your own self-hosted instance.

Unfortunately, they let it fall into disrepair, left it unmaintained, and last I checked the Ghost desktop was nowhere to be found in the repo. One of the maintainers explained to me that they just didn't have anyone willing to maintain the app and so I migrated away from the platform myself.

Integrating is a fantastic idea, and will give a run for the money, but the reasons for leaving and to publish on aren't so compelling with editors like exist now, along with the plugin.

I'm going to give it another looksee to review what happened to the elegant, nature that Ghost used to espouse as one of it's key ingredients for using it in the first place. I just hope that they don't try to go the way of , , and other projects that were forked, and somewhat marginalized, as a result of decisions to force community versions into products that lacked most functionality without fee based subscriptions. Lord knows, the last time I checked their managed hosting solutions for Ghost it certainly wasn't even competitively priced.

With this newfound revelation in the form of some kind of epiphany, let's hope their commitment to and FOSS exceeds that of their grasp for excessive monetization.

⛵

.

RE: https://todon.eu/users/MediaActivist/statuses/112302834109929024

@MediaActivist

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 foss

Thanks Evan, there's a bit to digest there, some of which I agree with, and some of which I don't, between what both you and the Other Evan had to offer.

It's good to get this stuff right out in the open, especially as the Fediverse is currently undergoing yet another paradigmatic shifts, perhaps an evolutionary step, but certainly, a complete game changer from much of the perspective offered in the Evan <==> Evan Essays ;)

https://fediversity.site/item/eed57428-ca9c-4ea1-a398-ef2d7319eff7

I hope that helps! Enjoy!

RE: https://evanp.me/2024/04/14/responses-to-rabble-on-activitypub/

@evanprodromou

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

@Teri_Kanefield

Hi Teri,

I'm writing you because I came across your blog site and thought you may be able to leverage the Fediverse in conjunction with your WordPress site's publishing horsepower.

As a advocate with great enthusiasm for mass adoption, I'd like to suggest a couple of things for you to consider, and the following treatment can also benefit others who also have bridged over to the Fediverse that already have a WordPress installation, or have been looking to deploy one.

  • First, that you think about establishing a Fediverse account other than that of a stock Mastodon instance. Sure, keep your @Teri_Kanefield@mastodon.social account, just create another account for yourself on a platform that will afford you more options that can facilitate your creative freedom (let's not dissect that word, lolz) to publish posts that are in excess of a paltry 500 characters, along with things like Markup capabilities, Etc. Just a thought. ...

This leads into the next suggestion, ...

  • Second, why not make that account your existing WordPress blog, where you already have a permanent, branded presence and readership? Let's supercharge your WordPress site by making it a full and complete publishing platform completely integrated with the Fediverse.

There's a couple of methodologies, but generally speaking, once you install the ActivityPub plugin any future blog posts are on the Fediverse as well as any other distribution channels you may already have (say, by virtue of having installed the JetPack Social plugin that propagates into the deprecated silo networks).

One method I can recommend is to follow this basic procedure to popularize your blog posts and gain followers - just like you probably have been with the mastodon.social account you already have:

  1. ) If you've already created a new account on a more feature complete platform that's better suited for long form posting, inline images, Etc., like , , any or family fork platform, , or (They all have excellent Markdown support too); simply follow your user account @<username>@terikanefield.com. If not, then simply follow your WordPress Fediverse user account from your existing masto account - which you should do anyway since I gather you have some respectable measure of followers.

2.) Everytime you publish a new news article / blog post on your WordPress site, you'll see it in your stream on your fediverse accounts.

3.) Boost each article from those accounts, your followers will see what you boost in their streams.

4.) encourage them to boost as well and/or comment - you'll see those comments in the reply section of each article on your WordPress site - Awesome!

5.) Now that you have followers of your WordPress user's Fediverse account you should be able to garner more direct interaction on your WordPress site, instead of having to post links to those posts from your mastodon.social account.

  1. ) From your @<username>@terikanefield.com account at your WordPress site, you can now directly interact with your followers, even those who post replies/comments to your articles, whether or not they are a follower of yours.

I'm taking the time to write because I see that you have a relatively decent circulation and engagement between readers and your blog articles, and the more people that see you engaging with others in the Fediverse directly from your WordPress site, the more people are encouraged to Join the Fediverse.

I am, as stated in my profile and also leading in to this, a FOSS and Privacy Advocate.

So here's a couple of links, one to the plugin itself - it's easy to install and deploy. Another older one that's still relevant that shows you how to do the install, and I think that's about it. We'll see ;)

  • WordPress ActivityPub Plugin - This is where you get the plugin
  • HowTo with Video - Really simple, easy install, right from your WordPress admin panel
  • JetPac Social - I'm definitely not a fan of this kind of engagement (with the privacy mining, deprecated, monolithic silo networks), but you do you - it can afford you with even greater reach through syndication, and if you write about the Fediverse, well, ... So much the better!
  • You should also consider following the magnanimous @pfefferle - one of the primary authors of the .

I hope that helps! All the best!

⛵

.

tallship, to random

Happy RFC 2334 day!

You're a fricken' Teapot!

https://en.wikipedia.org/wiki/Hyper_Text_Coffee_Pot_Control_Protocol

⛵

.

tallship, to random

Go Tommy, it's your birthday, Go Tommy, it's your birthday, Go Tommy, Go Tommy

- F(r)iends @TommyWiseau You can haz ! 🍔

⛵

.

RE: https://mastodon.social/users/TommyWiseau/statuses/102890475029012257

@TommyWiseau

tallship, to foss

Well... Reddit may not yet have been shown the door, but it has certainly been handed its hat.

Think about it. platforms such as the projects for Kbin, Mbin, Lemmy, Lotide, and now...

https://join.piefed.social/ and the repo is here: https://codeberg.org/rimu/pyfedi/

Be sure to check the Link below in the link that @jeze left and sign up!

Pretty kewl, IMO. Thanks for sharing Elley :) it looks really nice and I created an account for myself. Seamless federation with the others too - very nice :)

⛵

.

RE: https://kzoo.to/users/jeze/statuses/112168259370814891

@jeze

tallship, to fediverse

@ben If I read everything correctly, you indicated that it should be able to recognize WordPress sites that have the ActivityPub plugin installed, but I didn't try to plug any of those in.

It is reminiscent of Share to Any and a couple of others that used to aggregate almost all of the available share points in the old monolithic social spaces, like del.icio.us, Diigo, and the thirty or so others supported by that plugin.

I'm looking forward to seeing how your effort progresses though, and it would be kewl if you could post an Atom or RSS feed link to make that easy in the meantime, although I'll follow you now and hope not to miss any milestones :)

I did plugin many Fediverse platforms such as various Friendica, Mitra, Misskey, Iceshrimp, Hubzilla, Diaspora, Akkoma, Lemmy, Takahe, and Pleroma sites, but none of those were found.

masto is obviously low lying fruit, but the real measure, IMO, is breaking out into the at large (not just masto). Interesting though, and thoughtful, that you Support Threads and Bluesky. will you be following up soon with nostr as well?

Exciting work there! Thanks for sharing (no pun intended ;) well, maybe a little ).

⛵

.

RE: https://werd.social/users/ben/statuses/112170840438655254

@ben

tallship, to random

@mjj

Morten, I love quotes: Here's a fav from my personal collection that I thought would be a nice addition to your https://sagt.dk/ collection :)

> Ultimately, shit will happen. It also happens to fly farther when using tools.
> -Robbie Workman, May 19th, 2009, @20:31hrs (UTC -8) - LQ.

⛵

.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • normalnudes
  • hgfsjryuu7
  • magazineikmin
  • thenastyranch
  • Youngstown
  • slotface
  • everett
  • ngwrru68w68
  • mdbf
  • kavyap
  • tsrsr
  • Durango
  • PowerRangers
  • DreamBathrooms
  • Leos
  • InstantRegret
  • khanakhh
  • osvaldo12
  • vwfavf
  • tacticalgear
  • rosin
  • cubers
  • cisconetworking
  • GTA5RPClips
  • ethstaker
  • tester
  • modclub
  • anitta
  • All magazines
    •