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 #Fohmarkt server elsewhere - this is a very nice feature, like #DeSoc #eBay!!!
- 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 #Fediverse. 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 #ActivityPub 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 #ActivityPub 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 #social_commerce communications tool - you really should experience how kewl it is for yourself.

I couldn't locate a #Matrix support room for Flohmarkt like most contemporary software products maintain in the FOSS world, but the more traditional irc chan #flohmarkt at #LiberaChat 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 #Fedizens who share and boost individual items and listings in Flohmarkt?

I hope that helps! Enjoy!

#tallship #FOSS #Marketplace #eBay #I_can_haz_Cheezburgerz? 🍔
@grindhold @me @flohmarkt_support #flohmarkt_support

⛵

.

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

@Yonggan

@coffeegeek

Hi Mark,

I've got a follow up here for you :)

A few items, but for the tl;dr please scroll down towards the end. The first few appear to be precisely what you asked for, the third is my rather enthusiastic recommendation.

I believe this first one is the plugin I mentioned, and was found to be quite lacking, further, frustrating to most - This showcases the glaring problem associated with conflating mastodon with that of the #Fediverse - most things break, early and often, over and over again.

- A simple share button that breaks about a fourth of share attempts:

Here's Terrence Eden's article on the Share on Mastodon plugin. I thought a link to this article best, as it leaves you lots of breadcrumbs to pick up along the way to the plugins page at WordPress. Including Jan's blog article. I believe this was the one with the least utility, that caused the most problems with people, which is quite a bit more than frustrating for a lot of people, angering many. masto isn't even the big man on campus anymore - those days have passed, and are in the past; it's just one of many increasingly popular platforms that people use in the ActivityPub portion of the Fediverse.

I believe Jan is incorrect on the number of images that masto can accommodate - yes it used to be four, but lately, when authoring articles in the Fediverse with platforms that accommodate inline media in the posts, I've noticed that masto actually will include 5 images, the rest it summarily discards, making for an even more confusing event for those on masto (NGI Zero funding has just been secured BTW, to at least bring masto into the 21st century with Quote Posts - like pretty much everyone else has had for a long time, some for a decade now).

Perhaps in time this will improve, or you can get into it with the aid of some of the others below, or just move past all that and install the plugin at the end of it all which performs famously ;)

- Conflating mastopub with the Fediverse is a Bad thing:

I've heard a few good testimonies of how well the Fediverse share button performs. Note that no where in the description or documentation is the word mastodon used; no one is mislead to believe that there is such a thing as a mastodon network - because there isn't.

- People should be offered the opportunity to share interesting content into (and throughout) the Fediverse, not some small slice of the available platform choices existing there:

This next option was heavily inspired by the old AddToAny plugin back when a kazillion different silos were popular and extant. I remember using that plugin to support sharing across upwards of 30 or so various social networking, bookmarking, link aggregation, and other types of obscure sites in far flung places of the world. I've also heard some good things about this solution too - please take note of all the certified platforms that it supports, and yes, mastopub is one of those ;)

If you do choose this method, do please join us in the Fediverse-City Matrix room to offer a review / evaluation as to how well Fediverse Share works for you. Several project leads there are always interested in viable solutions that are inclusive and accommodate the wider community at large without any marginalization through misleading brand recognition.

I do like the colorful buttons too in the demo here. I also like the non-traditional "Lorem ipsum" example prose too. I find it refreshing :)

- Either through simple naivety or conscious exclusionary arrogance, here's some other masto branded share options, at least one, IIRC, was much less than satisfactory, but I typically don't traffic mastodon branded things anymore when the insinuation is that the product represents the Fediverse. You may find, however, that one of these is just what you need, and that with a little bit of tweaking will fit nicely into your website's business processes. A little branding can go a long way, but sometimes a solution depends on, for example, a "share API endpoint", not strictly compliant with the W3C's published specifications, that serves to marginalize all other platforms by excluding them (that's commonly regarded as EEE). I'll just post the links w/o commentary:
- mastodon share button
- Share on mastodon button
- MastodonShare
- Toot Proxy
- Yet another mastodon share button
*Share to mastodon

There's another utility by Nikita Karamov (creator of the Toot Proxy above) that doesn't embrace the predatory branding of a diluted trademark:

- Share₂Fedi - Share₂Fedi isn't a button, exactly, but the functionality is there and it is inclusive of the larger diaspora of the ActivityPub powered portions of the Fediverse, avoiding any sort of marginalization as a result of marketing through leveraging overt, and predatory branding campaigns.

Alright, I know you're interested in getting to the good part. Yes, I'm guilty of that same sort of mindset that makes you scroll down to the bottom of the ToS before you can click on the submit button. But before we get to the tl;dr:, we have one more which in spirit at the very least, is promising, I encourage you to read it:

- Honorable mention goes to shareOnFediverse, which works even with GNU Social, Diaspora, PixelFed, Hubzilla, Lemmy, Friendica, Kbin, Misskey, Pleroma, Etc.

# tl;dr:

That bit of markdown above (the H1) may not show up on your platform, depending. Regardless, you've arrived. Here's the solution that I personally recommend, a very fine solution that not only allows one to share their content into the Fediverse by providing links back to their website, but providing the gateway for people in the Fediverse, #Fedizens, if you will, to engage the authors of news and blog and lifestyle and cookbook style tutorial and HowTo sites, directly, with two way commenting and sharing of dialog in true open and participatory fashion:

First, (and it has indeed come a long way since the post of this article), a page on how exceedingly simple it is to install and configure this, the WordPress ActivityPub Plugin:

- Making the Social Web a Better Place: ActivityPub for WordPress Joins the Automattic Family

Bear in mind that the plugin was in beta at the time, so never mind the sourpusses in the comments who wanted it, and yet couldn't have it because they weren't self-hosting #WordPress. I must reiterate that development has come a long way, the plugin is in general production release and available for any WordPress site, managed, self-hosted, or otherwise, and it's got a powerful feature set.

Posting links back to clear-net websites on the open Internet is fine, it's not like clicking a share to Faceplant or InstaSPAM button when you share an article that you like into the Fediverse, After all, it's every blogger's mission to drive traffic to their own site (not Faceplant or InstaSPAM), but then your visitors are limited to offering comment replies in the manner of a form submission on the site that really only allows you to subscribe your email for subsequent comment notifications for the article or thread that your commenters spawned.

What the #ActivityPub plugin enables for those who engage with you, is to provide an instant audience of several million MAU (monthly active users) throughout the Fediverse who will be able to directly participate and engage in the conversation from their own native Fediverse platforms, receiving replies as well.

I've called this, A Game Changer, before. A few times, actually. @matthias@pfefferle.org @pfefferle and his small team of developers created and curated this plugin that enables this hitherto (mostly) inaccessible feature set for the masses. Literally anyone in the ActivityPub portion of the Fediverse can now comment and reply to the comments of others on WordPress sites, which is pretty much like 40% of the entire word wide web nowadays, and you can check this out for yourself right now by visiting his blog at https://notiz.blog/ in the comment section of any one of his articles.

There were some issues, which could be attributed to the predatory marketing practices by Mastodon gGmbH, whereby a lot of what is actually ActivityPub or Fediverse centric was being referred to, and worse, attributed to mastodon in one sense or another, further diluting their trademark which places it in jeopardy of losing its registration (the first item in mastodon's general guidelines states, "Only use the Mastodon marks to accurately identify those goods or services that are built using the Mastodon software." - but the defense of trademarks themselves is another matter entirely, although the discussion has come up many times with the responsible parties, often, in very heated, public, forums.

Anyway, Mattias and his team have become incrementally more mindful of placing emphasis upon #Fediverse, the brand, instead of masto, the brand, and that's a good thing because it goes a long way toward correcting the existing confusion that exists due to the abuse certain marketing personalities have, and continue to pursue. Indeed, the plugin itself is named ActivityPub, which is appropriate - and it certainly is not an exclusive tool for mastopub.

You can download the latest and greatest version of the WordPress ActivityPub Plugin HERE, which was released just 3 days ago, and I know because I was on the periphery of an issue that was resolved, making this an even more relevant and quickly becoming (IMO) essential tool for #DeSoC and Fediverse aware bloggers, journalists, chefs, and anyone else that knows they can benefit from deploying their own WordPress site for business or personal use in communicating with the world beyond the walls of the deprecated, proprietary, privacy mining monolithic silos.

In wrapping things up here, it goes without saying that one of the very most powerful aspects of the #WordPress_ActivityPub_Plugin isn't actually that people can respond to your published articles from the comfort of myriad clients such as #FediLab, #Husky, #Phanpy, or the native web or desktop interface for their Fediverse instance, but the reality that they can simply follow you, on your blog, and receive your blog or news or HowTo articles in their streams whenever you publish a new item. From there, they can boost (more exposure for your published works), reply (of course), and even offer a bit of narrative introducing your work with a #Quote_Post. It's like a butterfly affect, or concentric circles emanating from one little plop of a pebble into a pond.

Oh, one more thing, there's nothing preventing you from including one of the pretty little Fediverse Share buttons either, in conjunction with the ActivityPub plugin. After all, some folks like to comment and let you know their thoughts, while others prefer to simply share it with others who will also tell two friends or themselves offer comments to your articles - it's a win win for everyone on both sides of the line that divides the Fediverse from those so-called Big Tech institutions comprising the walled gardens of subjugation by the #Sunnyvale_Syndrome.

I hope you've found this helpful, I didn't want to send you on an errand of discovery without making sure that there's been some decent coverage of several different alternatives currently available for you.

All the best!

#tallship #FOSS, #Automattic @pfefferle

⛵

.

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

⛵

.