#cw — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #cw, aggregated by home.social.
-
RE: https://mastodon.radio/@va3fwe/117139195633086408
Similarly: Anyone know a #cw #MorseCode learning app that does random strings of words with a configurable # of words?
Random letter blocks of increasing length was very helpful to me, and I'd like to do same with whole words but all tools I have are either random single words OR entire sentences/QSOs/news articles.
I'd like something where I can start with two random words and build up.
I use iOS and web apps but if you know an Android app feel free to mention for others.
-
#cw aislop - Some vaguely in the ballpark mockup for reference
-
-
Je plaque tout pour devenir influenceur petit déjeuner. #CW #nourriture
-
Zero-gravity CW paddles?
Ok, I confess, I’m a bit of a klutz when it comes to sending Morse Code. I started out, many years ago, with straight keys. I never got along with the typical flat knobs, I preferred “Navy Knobs” – the kind with a big round thing on top that you can really get a firm grip on and a wide flat disc below. The original purpose of the flat disc at the bottom was to discourage operators from touching the high voltage contacts underneath. There was always the possibility that an inattentive operator would touch the metal parts of the key – in the good old days of the electric telegraph, that is, whereupon his sending speed would either suddenly accelerate to 100 wpm or drop to zero, permanently.
My issue was my nervous tight grip. That resulted in me pounding brass in a very literal sense, sometimes lifting the key right off the table. But then I acquired a very nice set of Bencher paddles as part of a package of QRP gear I purchased from another ham. Paddles require a very light touch and so I learned to relax and control my heavy fist.
Over the years I acquired several more sets of paddles; I even built some of my own – with varying degrees of success. As well as being a klutz I am also of a miserly nature. A set of paddles is really just a simple two-way switch; why the heck should I spend hundreds of dollars for something I can build from an old hacksaw blade and a dollar’s worth of hardware?
And then, my growing interest in portable operating out in the Big Blue Sky Shack took hold. Now I needed paddles that were small, lightweight but still rock firm and stable. Hmmm? SMALL, LIGHTWEIGHT, STABLE – pick any two! New problem – small, lightweight paddles have a tendency to go skating across the table unless the operator has a very, very light touch. I do not.
And so it came to pass that I attended a local hamfest recently and picked up yet another set of paddles. They were inexpensive, which checked the miser’s box in the shopping list. They are also small, very small, very lightweight and … not so stable! Frankly it would take the touch of an angel to operate them without chasing them all across the table. I call them my zero-gravity paddles.
I really like my zero-gravity paddles but I had to find a way to stop them going on haphazard excursions across the table whenever I touched them. Their tiny rubber feet did not provide enough friction to keep them from moving around, so what could I do?
Oh no John, no John, no John, no!
Alrighty then, this first attempt was not my most inspired idea. Carrying a bench vise out to the field is pretty impractical – but it works fine business!
There had to be a better way. As Sir Isaac Newton could have maybe once said: “A set of paddles that are stationary or in motion continue in that state unless acted upon by an external force.” Well, speaking as that “external force”, I knew the onus was on me to create an equal and opposite force to oppose the force of my less than delicate keying.
As a young high school student I was fascinated by another famous scientist over in the Land of Hope and Glory. Among his many notable scientific achievements Michael Faraday was a pioneer in the field of magnetism. His discovery of a magnetic field surrounding a wire carrying electric current was perhaps the spark of genius that would later lead to the development of radio.
Thank you Sir Isaac and Mr Faraday
I am no great scientist myself but I am willing to learn from those in whose footsteps I am not worthy to tread. Now the solution that emerged from the mist was as simple and obvious as it could possibly be – magnets.
Drawing on the work of Sir Isaac Newton, the force of friction was insufficient to overcome the force of my over-enthusiastic keying, but thanks to the work of Michael Faraday, the force of magnetism is more than sufficient to solve the problem.
So, I carefully removed the glued-on rubber feet and replaced them with small, strong magnets. The paddles came inside an Altoids mint tin – actually a very old Altoids tin that is probably worth the price I paid for the paddles. Altoids were originally made in Great Britain (actually in Wales) before corporate buyouts moved production to Chattanooga, Tennessee.
That tin serves two purposes – it keeps the rather delicate paddles safe during storage and transport, and also acts as a base for the magnetically secured paddles. Now everything works as it should (except for my keying perhaps). These paddles have a very nice feel which improves my sending accuracy.
The ham who sold these paddles to me did mention the original source which I promptly forgot. If you recognize them perhaps you could let me know in the comments. And, if we meet on-the-air, these are most likely to be the paddles I’ll be using.
Help support HamRadioOutsidetheBox
No “tip-jar”, “buy me a coffee”, Patreon, or Amazon links here. I enjoy my hobby and I enjoy writing about it. If you would like to support this blog please follow/subscribe using the link at the bottom of my home page, or like, comment (links at the bottom of each post), repost or share links to my posts on social media. If you would like to email me directly you will find my email address on my QRZ.com page. Thank you!
The following copyright notice applies to all content on this blog.
#CW #MorseCode #OutdoorOps
This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License. -
@eniko That's why I love it here: it's all in the author's hands; just use content warnings.
I think it's important to call people out — bonus points for doing so in a constructive manner — but it's even more important to protect your peace of mind and sanity; to be able to participate without fearing... harm, effectively.
Offering readers / viewers ban lists, etc. — I haven't been on X in ages, but I can't imagine it's changed much — is _not_ the same thing _at all_.
-
An Outside the Box look at the 48 inch base loaded vertical antenna
It’s not the smartest idea really is it? A quarter wavelength vertical whip for the 20 meter band should be around 5 meters (17ft) tall. Why build a vertically challenged whip that is less than a sixteenth of a wavelength long and expect it to work? And … with a QRP transceiver too!
Yes, indeed it’s not the smartest idea in the world, but Elecraft and others sell such an antenna and many hams use them. So is there another angle to this idea? Am I missing something? I watched another of G3OJV’s videos recently in which Peter Waters (of the UK’s Waters and Stanton amateur radio store) put a different perspective on the idea, so I decided to try it.
G3OJV’s idea is to force the counterpoise to do most of the radiating. Huh? If the counterpoise is raised above ground it will radiate – in fact, if the radiating element is only 48 inches (about 1.2 meters) tall, the counterpoise will do most of the radiating. I decided to model the idea using EZNEC to find out how to configure such an antenna so that it would actually have a chance of working. The model yielded some very interesting surprises.
But there’s a hidden gotcha!
The radiation pattern looks fantastic, and the gain is equally impressive at 4 dBi. It’s no wonder these little critters sell so well, but wait, let’s take a closer look. The NEC-2 engine I use for antenna modeling is notoriously unreliable for antennas that are close to the ground. I had set the Ground Type to Real | MININEC. Now suppose we take another look using Ground Type: Real | High Accuracy. Whoa, now we lose 6.4 dB; the actual gain figure is now predicted to be minus 2.4 dBi.
There are two ways to look at this result. First, the optimistic view: -2.4dB is less than half an S-unit at the receiving end – the receiving station probably won’t even notice the difference. Second, the pessimistic view: if our transmitter is pumping out a mighty five watts of RF, the amount of RF actually leaving the antenna drops to less than 3 watts (ignoring any losses in the feedline). On a good day when the propagation is favorable we are still going to make contacts. But, if the propagation is unfavorable, or we are trying to break a pile-up, our self-imposed handicap is going to be a problem. And, all of this assumes that NEC-2 is not being optimistic in its calculations.
But wait, there’s more bad news
I only modeled the far field propagation of an unloaded 48 inch whip worked against a 17 ft (5 m) single raised counterpoise. Of course, a base-loading coil is also required to match the impedance of the short whip. We’ll get back to that in a moment.
Let’s go ahead and waste more of our radiated power
Typically, very short whips are used for portable operations, and the temptation is to simply throw the counterpoise wire on the ground. Now EZNEC Pro/2+ set for high accuracy ground shows a gain of -3.31 dBi and our actual radiated power drops even further to a little over 2 watts. We are on our way to QRPp! (QRPp refers to radiated power of 1 watt or less). Remember, these little baby whips work best when we force the counterpoise to do most of the radiating. If we lay the counterpoise down on the ground the whole strategy is defeated (but the earthworms will be grateful for the warmth).
About that loading coil
The usual method of constructing a loading coil is to wind wire around an air-core former, or some other non-conducting material. Sometimes the wire used is copper, sometimes it is stainless steel. Now we have to take into account the DC resistance of the wire. Copper is good, silver or gold is better; stainless steel is ungood. You don’t need to be a rich ham to use silver or gold (although it might be a good hedge against inflation if you wind all your coils with solid gold wire); due to the skin effect gold-plated wire would work very well. Even copper-plated stainless steel would be better than unplated stainless steel.
The website 66pacific.com calculates that a loading coil of 9.1 microhenries is required to match a 48 inch whip at 14.150 MHz. That would require 30 turns on a 1 inch diameter air-core former. The length of wire required will be about 95 inches (2.4 m). The same coil can be wound around a powdered iron toroidal core with considerably less wire. Less wire means less resistance loss. Are we nit-picking here? Yes, the resistance losses are fairly small, but remember, we are already down to 2 watts out of our original 5 so every watt counts.
The long and winding coax that leads to your transceiver
Our best bet is to use a very short whip mounted directly on the antenna connector of our transceiver, otherwise coax loss can also become an issue. But make sure your antenna connector is mechanically capable of supporting the weight of a loading coil and whip. Some radios have a BNC antenna connector directly mounted on the transceiver’s circuit board which is an obvious weak point. Further stress is added if the counterpoise directly connects to the shell of the BNC.
I built a 48 inch whip antenna; how well did it work?
I own a collection of old ham stick antennas. Hamsticks have two parts, a helically wound loading coil section and a stainless steel whip. I grabbed one of the whips which happened to be the magic length of 48 inches and mounted it on a tripod with the feedpoint about 4 feet above ground. I then added a loading coil wound with 16 gauge enameled copper wire around a small type 2 toroidal core. My counterpoise was a single radial wire, 17 ft long sloping down from the feedpoint to a few inches above ground at the far end. EZNEC predicted that mounting the far end close to the ground improves the performance.
I fired RF at the antenna, through a few short feet of RG-58 coax, from my mighty mini QMX transceiver at nominally five watts and monitored the SWR on the QMX – all was good. Time to go hunting.
I considered it risky to attempt a POTA activation with an experimental antenna so the trial was to be a backyard hunting session. Well, knock me down with a feather, I actually made a contact with my microwhip. Propagation conditions that day were forecast to be good on 20m and I could hear several POTA stations on the air. I selected a station in Florida which is over 2000 km from my QTH in Ontario, Canada. I could hear the Florida station fairly well so, with a good deal of trepidation, I called him on CW with 5 watts into my test antenna. He came back to me right away, and after a couple of attempts to copy my callsign, we signed off and I put the contact in the log with his RST report to me of 229.
Wow, is this antenna a “keeper”?
No.
There is a popular expression in the QRP world: “QRP – when you want to send the very least”. My interpretation is: when you want to send the very least – get a 48 inch whip!
What is your experience?
If you are still wondering (really?) what my opinion of these vertically challenged antennas could possibly be, then let me say there are better options for ultra-portable lightweight antennas. Even a slightly longer whip would be better. I also built a version with a 9 ft whip – the extra length makes a lot of difference. Adding a top (capacitance) hat improves performance even further.
But, I am sure there are Ham Radio Outside the Box readers with entirely different experiences. For example, if you are an FT8 operator, the lower signal to noise performance – even over CW – may help to squeeze contacts out of a highly compromised antenna. SOTA operators working from the top of a mountain out in the Rockies may experience very short whips very differently. Perhaps if I were to take my 48 inch whip out to one of Ontario’s soaring peaks which sometimes scrape the clouds at 500 m (1640 ft) above sea level I might have a different experience. But then again I might go to the same high point with a real antenna!
Let me know what you think in the comments.
Help support HamRadioOutsidetheBox
No “tip-jar”, “buy me a coffee”, Patreon, or Amazon links here. I enjoy my hobby and I enjoy writing about it. If you would like to support this blog please follow/subscribe using the link at the bottom of my home page, or like, comment (links at the bottom of each post), repost or share links to my posts on social media. If you would like to email me directly you will find my email address on my QRZ.com page. Thank you!
The following copyright notice applies to all content on this blog.
#Antennas #CW #POTA #QMX
This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License. -
Hi everyone. I am calling #CQ on 10.110 MHz #CW #HamRadio #AmateurRadio
-
CardWirthシナリオ感想・おすすめ記事を書きました。今回は『万物の起原を思考して』です。
https://iekonkon.com/15576.html
#CardWirth #カードワース #CW #感想 #フリーゲーム #ゲーム -
TechTip #3 Radials and counterpoises
TechTips on Ham Radio Outside Outside the Box are occasional short posts on specific technical topics. But beware, along with regular posts here on this blog, the content is not a definitive technical treatise and should not be read as such. I write about my own opinions and experiences; your opinions and experiences may be quite different. I welcome constructive feedback either in the comments or, if you prefer, by direct email.
“All lies and jest …
Still a man hears what he wants to hear and disregards the rest”. Paul Simon and Art Garfunkel sang those words in their song “The Boxer”. The words reflect how hams often react when our long-held, cherished beliefs are challenged. “My antenna just works, I don’t care about all that technical stuff” is a view I have heard – especially when the antenna cost hundreds of dollars. And nothing creates more exothermic debate than the subject of radials. Or is that counterpoises?
Definitive definitions
On Ham Radio Outside the Box, when the word “counterpoise” is used, it refers to the “other half of an antenna”. The “other half” could be 120 buried radials, or it could be a “magic carpet” (Faraday cloth). It could be a ground rod driven vertically into the ground. It could even be the ubiquitous (and apparently blessed by angels) 17 feet of wire laid on the ground. That magic length of 17 feet has been proved by thousands of QSOs so why care about all that technical stuff? Eh?
When you read the word “radial” here on Ham Radio Outside the Box it refers to a length of wire. A counterpoise may comprise one or one hundred and twenty radials. Radials could be buried in a shallow grave inches below the surface or they might be raised above ground. Buried radials – or even radial wires laid on the ground – are detuned by the ground and can be any length. Longer radials work better on the lower bands.
“Crickets are singin’ and lightning bugs are floatin on the breeze”
It’s been a while since I went “Fishing in the Dark” (for contacts on the radio) but I do spend a lot more of my on-air time out in the Big Blue Sky Shack, usually on a sunny afternoon – even if it’s only out in the backyard. If we venture out to a park to spend a couple of hours playing radio, we really aren’t going to waste that time laying out 120 radials. If an antenna needs ground radials I lay out between 4 and 8 of them. I know my antenna’s efficiency will be compromised, and I acknowledge the physics, but field expediency is the prime directive. Heck, I usually operate QRP in the field too; maybe I should try “QLF” (sending CW with my left foot) too. Some of my code buddies claim I’ve already mastered QLF!
Floatin’ on the breeze
Compromising efficiency is not mandatory. If we raise the antenna (a vertical whip) above ground. Now just a couple of tuned radials is as efficient as a rat’s nest of wires on the ground. A couple of radials? Why not just one radial? I was asked that question recently by a Ham Radio Outside the Box reader. I had to put on my physics graduate gown and mortarboard while I thought about that.
I started with the idea of a vertical dipole – that’s a quarter wave of wire on top of another quarter wave of wire with the feedpoint in the middle. Now let’s bend that dipole a little. Now it looks like a vertical radiator with a quarter wave high flying counterpoise. If we keep that configuration well above ground it should still be as efficient as a dipole.
I got wires in low places
How low can we go? My theory (which is open to debate) is based on interaction between that raised radial and the ground. The current in the radial wire induces an out of phase image in the ground. In the near field the image wave and the wave in the radial wire tend to partially or fully cancel each other.
The amplitude of the image wave in the ground varies based on two things. (1) the amplitude of the current in the radial, and (2) how close the radial is positioned with respect to ground. A high radial has almost no interaction with the ground, whereas a low radial will have a much greater interaction.
Now, let’s consider this: we can reduce the amplitude of the current wave in the counterpoise if the current is shared between more than one radial. Two radials each carry half the current; four radials each carry a quarter of the current. The lower the current, the lower the canceling effect of the image in the ground.
So we can conclude that it is fine and dandy to use low radials if there are a lot of them. On the other hand, a single radial should be kept well clear of the ground. Does that make sense, or didn’t I wake enough brain cells with my morning espresso today?
But wait, there’s more …
If the objective is to reduce the interaction with the ground, and the amplitude of the current wave in the radial wire(s) is a factor, there is another way – reduce transmitter power. See, QRP ain’t so bad after all!
Incidentally, the image wave in the ground travels more slowly than the current wave in the radial. If the length of the radial wire is one full wavelength, or more, the two waves eventually are in phase and the current is reinforced instead of being canceled. That is how Grasswire antennas work.
Murphy’s opinion
Electrically, a single raised radial will be efficient, subject to the conditions discussed. According to Murphy’s Law, if you use a single raised radial, you better anchor that antenna down good or the tension in that radial wire is gonna pull your antenna over. Murphy says two radials, 180 degrees apart, will keep it up.
#Antennas #Counterpoise #CW #Ground #OutdoorOps -
-
🎉 Thrilled to complete my FIRST Satellite CW QSO! 🛰️📻
Date/Time: 2026-08-04 13:02 UTC
Satellite: FO-29 (Mode V/U)
Callsign: BH3HMP
RST: 599 / 599
Freq: TX 145.948 MHz | RX 435.855 MHz
Antenna: Az 332.8° / El 37.2°
DXCC: China 🇨🇳
First of many contacts on the key through the birds! ⚡️ -
I mean, you can't help but be real about what we're facing, but I really don't enjoy the news spigots. XD
Also, some items, even if they're from someone who isn't a regular poster/booster are just so dang depressing, they should really be #CW'ed. :/
-
Starting in 12 minutes I'll be participating in the upcoming #NAQP #CW #AmateurRadio contest on the Braille team. Watch for NU7I on the 10M, 15M and 20M bands as propagation and time allow. #HamRadio
-
Ich habe mir ein kleines Werkzeug gebaut, das aus einem Contest-Log ein Video
macht. Die Animation zeichnet jede Verbindung zum
Zeitpunkt des QSOs auf die Weltkarte, eingefärbt nach Band und wahlweise mit
Grayline.Beim CW-Fieldday waren das 815 QSOs animiert in dreieinhalb Minuten. Ich stelle das
hier inklusive Quellcode vor https://www.dh3iko.de/qso-animation/Ich freue mich über jedes Feedback. Antworten hier werden automatisch als
Kommentare unter dem Artikel angezeigt.
#darc #hamradio #e13 #amateurfunk #contest #fieldday #cw #foss -
The #parksontheair #POTA Gods smile on me this morning during my "Beat The Heat" #QRP #AmateurRadio #HamRadio #MoreseCode #CW activation including a 20 meter #SSB #QSO to Japan from Kentucky, USA
-
A 5-Band, Lazy-L, Linear-Loaded, Ladder Line Antenna (aka the “5B6L”)
About a year ago I mentioned an antenna devised by Peter Waters G3OJV that used a 13 feet (4 m) vertical wire to create a multiband antenna. I used Peter’s idea to create “A Simple, Low Profile, Multiband Antenna for POTA“. The antenna was designed to work on 20m, 17m, 15m, 12m and 10m with the aid of a tuner. But, I discovered a small problem on the 17m band. If we do the elementary calculation for the length of a quarter-wave radiator at the bottom end of the band (18.068 MHz) we find that it works out to be 12.95 ft – just a whisker short of the 13 ft recommended by G3OJV. So why is that a problem?
The problem arises because the antenna uses a 4:1 unun at the feedpoint. Since the 13 ft length is already almost resonant on 17 meters, the 4:1 unun makes the job of the tuner much harder. That did indeed prove to be the case when I tested my derivative in the field. So, I made a small change when designing the new 5B6L antenna – I increased the length to 14 feet (4.2672 meters) – well … not quite true, but that is the underlying principal behind the linear-loaded equivalent.
Here are the calculated lengths of a quarter-wave radiator at the mid-point of each of the five bands of interest:
20m: 16.6 feet17m: 12.92 feet15m: 11 feet12m: 9.39 feet10m: 8.11 feetA 14ft radiator slips nicely in between the 20m and 17m quarter wavelengths and becomes a “random length” on all 5 bands. Nice. But this is a linear-loaded antenna made from ladder line. Linear-loading shortens the required length by around 30%. Fourteen feet, shortened by 30% works out to 9.8 feet (~3 meters). After field adjustments I settled on a length of 9.75 ft (a little less than 3 meters).
Lose the radials!
I wanted this antenna to be what could be loosely described as a random length dipole – two equal lengths of ladder line (each shorted at one end) so that was how it was constructed. Now we have the benefit of versatility. It could be erected as a traditional dipole although with two very short arms it would be tricky to get it up in the air. It could also be erected as a vertical dipole on a support pole about 7 meters (23 feet) tall like my Spiderbeam. But that would make it difficult to orient the coax feedline so that it comes away from the antenna at 90 degrees, as is required to prevent the feedline picking up some of the radiated signal. Perhaps a sloper would work; now that is a very viable solution.
How ‘Bout a Lazy-L?
One of the YouTube channels I follow is “Jim’s Cool Stuff“. In one of his videos Jim suggested using a “Lazy-L” orientation of a vertical simple wire radiator and single raised radial wire. Why? The purpose is to increase the take-off angle. A vertical antenna usually has a very low take-off angle which is great for chasing DX, but what about shorter-range contacts? From my location in Southern Ontario, Canada it is only a short hop down to the north-eastern states in the USA. The US northeast has a very large concentration of amateur radio operators many of which participate in popular activities like POTA. A vertical antenna is likely to send my signal whistling over their heads, or at the very least, be received at a reduced level.
A Lazy-L configuration optimizes radiation to favor short to mid-range contacts by raising the take-off angle to achieve much shorter hops. Does it work? Yes indeed, during test operations I have been able to make contacts, just over the shallow puddle they call Lake Erie, into Pennsylvania, and across Lake Ontario into the state of New York, with quite respectable signal reports for my QRP CW signal.
The 5B6L antenna erected for test transmissionsBut what about DX?
Stations on the west coast of the US or western Canada could be considered almost DX – each is thousands of kilometers away. No problem! I said this antenna has versatility. The Lazy-L configuration can be re-oriented to a straightforward regular vertical with a raised counterpoise very easily. In fact the angle at which the radiating element leans can be adjusted to find an optimum at which near-DX and short hop stations all fall within its radiation pattern.
How to Build a 5B6L
The following describes construction of a 5-Band, Linear-Loaded, Ladder Line antenna that can be operated on 20m, 17m, 15m, 12m and 10m with the use of a tuner. Materials needed are:
- Ladder Line. I recommend stranded conductors because this makes the ladder line more flexible than solid copper conductors. Use of the 5B6L as a field portable antenna may stress solid conductors and lead to failures.
- a 4:1 unun. This item can be purchased or you can build your own using twin lead speaker wire (or similar) wound around a type-43 ferrite toroid
Instructions
- Cut two lengths of ladder line each 10 feet (3 meters) long. These may need to be trimmed during testing.
- Connect the two conductors of each piece of ladder line together at one end only.
- At the other end of each piece of ladder line, cut off the end of one of the conductors.
- Strip the insulation from the other conductor – this will be connected to the 4:1 unun.
- Connect each piece of ladder line to the unun.
Erection of the antenna
Attach a coax feedline to the 4:1 unun. A tuner may be inserted at this end if desired. For practical purposes, unless a very long coax is used, the SWR losses in the coax will not be significant so a tuner at the radio end can be used.
Set up your choice of pole, or other support, attach one end of the antenna to the top of the pole. The other end of the sloping radiating element (the feedpoint) should be supported on a short stick.
The other half of the antenna serves as a raised counterpoise and its far end can be supported by, for example, a trekking pole.
The slope angle can be adjusted by simply moving the counterpoise support sticks. See what works best for you. The whole antenna can be quite stealthy. I erected mine on only a 10 feet high pole. Efficiency may be improved by using a taller support but I prefer stealth when operating in public spaces. Tall antennas arouse suspicion!
The end is nigh!
A generous friend donated a lot of ladder line some time ago and I have used all but a few feet of it. Maybe it’s time to experiment with something different. So my next project – take a deep breath – is something I have been writing about in unflattering terms recently – a short, base loaded whip! What? Have I been enjoying too much Scottish champagne? Well, I thought it would be an interesting challenge to see how efficient I could make a short-ish whip antenna with a base-loading coil. A prototype has been constructed and has made contacts in backyard tests (with my helping fingers tapping on the key ). When the design has been completed you will be able to read about here on Ham Radio Outside the Box. Stay tuned.
Help support HamRadioOutsidetheBox
No “tip-jar”, “buy me a coffee”, Patreon, or Amazon links here. I enjoy my hobby and I enjoy writing about it. If you would like to support this blog please follow/subscribe using the link at the bottom of my home page, or like, comment (links at the bottom of each post), repost or share links to my posts on social media. If you would like to email me directly you will find my email address on my QRZ.com page. Thank you!
The following copyright notice applies to all content on this blog.
#AmateurRadio #Antennas #Counterpoise #CW #Ground #OutdoorOps #Portable #POTA
This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License. -
@Truth & Answers Let me be honest: Mastodon isn't the right thing to rely on for this.
There are two common misconceptions on Mastodon about Mastodon. The first one is that Mastodon is the only free, non-commercial, non-corporate, decentralised social anything. Once Mastodon users are over this, they still think Mastodon is the best free, non-commercial, non-corporate, decentralised social anything.
I've seen Mastodon being advertised by users as a Fediverse alternative to literally everything, including Reddit (because, like, you can communicate, right?) and even YouTube (because, like, you can upload videos, right?).
But again, let me be honest: The only thing that Mastodon can hope to be an alternative to is 𝕏. Because it's a Twitter clone. A purist Twitter clone whose developers intentionally reject feature requests because the requested features don't fit into their image of purist, minimalist, old-school, original-gangsta microblogging. They want to keep Mastodon a slightly more glorified SMS than 𝕏.
Mastodon isn't even the only microblogging server application in the Fediverse. It isn't even the best at that. 80-90% of Mastodon's users don't and probably will never realise that Mastodon is an intentionally crippled resource hog. Many believe that Mastodon is the fully-featured be-all, end-all of social networking.
By the way, even the Mastodon developers claim that Mastodon is fully featured. I've had a Mastodon dev try hard to convince me that Mastodon is fully featured although I've told him that I'm on Hubzilla. He essentially tried to tell me that Mastodon has every last feature that Hubzilla has plus even more on top.
In reality, Mastodon isn't the fully-featured be-all, end-all of social networking. It isn't even a social network. It's social media, just like 𝕏 is social media. It's designed for pumping out content and being followed because it's designed as a Twitter-like microblogging application. And it isn't even the best at microblogging.
Almost everyone on Mastodon is fully convinced that Mastodon has to be the best. After all, it's the biggest. It's what everyone chose.
No.
Mastodon is the biggest because everyone who wants to leave 𝕏 or Threads or Bluesky is railroaded to Mastodon. It's the biggest because all the newbies are only told about Mastodon. It's the biggest because none of the newbies even learn upon on-boarding that other 𝕏 alternatives exist in the Fediverse, that anything else exists in the Fediverse other than Mastodon. It's the biggest because mainstream media, tech media and even Fediverse activists only ever talk about Mastodon, Mastodon, Mastodon. (Granted, it's also the biggest because it's the only one with an official phone app in the Apple App Store and the Google Play Store. Even though that app sucks.)
All these Mastodon users who claim that Mastodon is the best choice don't realise that they themselves did, in fact, not choose Mastodon. They didn't know they had a choice. All they were told about was Mastodon. Seriously, if they'd had a choice, they'd probably be on Sharkey now and not on Mastodon.
I've read what people had to say who moved from Friendica to Misskey. Or to now defunct Calckey/Firefish. Or to Sharkey. Or to Akkoma. All these are microblogging server applications in the Fediverse. But none of them are intentionally crippled to stay close to Twitter, at least not to such a degree as Mastodon.
It was nothing short of eye-opening to them. Only by daily-driving something else than Mastodon did they realise what the non-Mastodon Fediverse can be like. And how crippled Mastodon actually is. That Mastodon is far from being the absolute pinnacle in decentralised social media.
They no longer had only 500 characters. They had thousands of characters. They would have had thousands of characters on every server running that software without having to ask around which one has more than 500 characters. It felt like a restraint being removed which they had never considered a restraint, at least not that much of it.
They saw text formatting which they considered technologically absolutely impossible in the Fediverse when they were on Mastodon. In fact, they had considered text formatting entirely impossible while on Mastodon until they had come across the first message from outside with text formatting. Actual text formatting, not Unicode trickery. Now they suddenly saw a lot of the stuff that Mastodon's HTML sanitiser removes. And they themselves could use it!
If they were on one of the *keys, they no longer had a timeline of single-message piecemeal. For the first time ever, they experienced what it's like to have something else than single-message piecemeal. Namely entire conversations right in front of them, right away. Without having to dig for them first.
They had features which they had always wished the Fediverse may introduce. They never knew that the Fediverse does have these features, only Mastodon doesn't. They had features that were completely unimagiable to them in the Fediverse.
There are users who have moved from Mastodon to something "minimalist" and lightweight like snac or GoToSocial, often on self-hosted, single-user, private servers. Even they suddenly had features they didn't have on Mastodon. Mind you, while not missing a single Mastodon feature (except maybe for a built-in Web UI).
And that's just the microblogging side of the Fediverse. None of this is actual social networking. You know, what Facebook does.
First of all, if it's about following and being followed, it's social media. A social network doesn't have followers. In case you don't know, Facebook doesn't have followers. It has "friends". Bidirectional connections. Not 𝕏/Mastodon-like mutuals which are two connections, one in each direction, but one connection that goes both ways.
Besides, there are even more important social networking features missing from the microblogging side of the Fediverse.
Where are the contact suggestions? Where does Mastodon suggest new contacts based on how many contacts you have in common with them? Where does Mastodon suggest new contacts based on what profile information you have in common with them?
Oh, right, the latter is impossible because Mastodon doesn't have profile fields with defined purposes. In fact, where are these? Every good social network has them! But Mastodon only gives you four all-purpose profile fields (just like Mastodon only gives you four of everything, four file attachments, four options in polls...).
Where is the list of unread posts, unread comments and other unnoticed actions? How are you to make sure you really catch everything your friends do? Because you can't do that if all you have is a timeline to scroll through until you no longer see new stuff. If you manage to scroll down that far. And only absolute newbies can do that on Mastodon because they hardly follow anyone.
Where are groups? Seriously, I've lost count of how many times Mastodon users said "the Fediverse" must introduce something like Facebook Groups. The huge majority of Mastodon users is fully convinced that the Fediverse does not have groups in any shape or form because Mastodon doesn't have them.
Where are all these things? In the Fediverse, no less? Where are they?
I'll tell you where they are.
Friendica. Hubzilla. (streams). Forte.
The actual social networking side of the Fediverse (although Hubzilla is more like a social CMS or a "social Swiss army knife" that you can also use as a Facebook-like social networking application). I mean, I've already explained that Friendica was created in 2010 as a Facebook alternative. Not a faithful Facebook clone, though, but better than Facebook.
Mike Macgirvin took over from Facebook what social networks really need. And Farmville isn't that, and spying on your users and passing that data on to the NSA and selling it to the highest bidder isn't that, so he didn't take over that. He didn't want to build a clone that also adopts the bad sides just to be as close to the original as possible.
He took over the detailed profiles with profile fields with dedicated purposes. He took over profile privacy settings. In general, he took over a lot of privacy features. He took over advanced user discovery and connection suggestions. He took over bidirectional connections, only without that silly name "friends". He took over groups with moderation, only that a group on Friendica is just another account with a special automated reposter. He took over enclosed threaded conversations with one post at the top and otherwise only comments. He took over a "timeline" of full conversations as the default. He took over the event calendar. And so forth.
Instead, he added useful stuff on top. He gave Friendica all the posting features to make it fully capable of long-form blogging with all bells and whistles. No character limit (except for in the database, but I think that was over 65,000 back in the day already). All HTML text formatting features (only that Friendica only used BBcode back then; now it can optionally also use Markdown). A post/thread title. Summaries. Embedded images and other media with no limit in number. He even added a spoiler tag like in forums that can hide parts of a message.
He took care of privacy beyond what Facebook had to offer. He introduced a permissions system. Friendica got multiple profile per account, only one of which is public, so that you can show different sides of yourself to different connections.
Now, if you want to embed images or other media in your messages, you have to store them somewhere. And not everyone could be expected to set up a little file space somewhere. So he built a file space into Friendica, one that can even be used as a Dropbox alternative, all the way to restricted access to certain directories.
Mike also added a content warning system that automatically generates content warnings on the reader's side, based on a keyword list. If you need something behind content warnings, add the keywords to the list, and you'll have the respective content warnings, but the next user receiving the self-same post or comment does not have these content warnings if they don't need them.
One important part of what makes Friendica Friendica is being able to connect to a whole lot of stuff. For example, Friendica could federate with StatusNet via the OStatus protocol from the get-go; this is also how it immediately federated with Mastodon when the latter was launched. Mastodon generates an RSS feed, something that many users don't know. Friendica not only generates an Atom feed, but it can subscribe to feeds. Friendica can "federate" with e-mail. Over time, more and more connection features were added, including Tumblr, Twitter (!), Facebook (only for a few years before Facebook crippled it) and a WordPress cross-poster.
Lastly, he made it possible for third parties to add extra features by implementing an add-on system.
I dare those who are fully convinced that Mastodon is the best Facebook alternative possible to use Friendica for a year. Not only dip one toe in to the water, but use it as their one and only daily driver for everything they've used Mastodon for. Not scratching the surface and using it like Twitter while ignoring any and all features the Twitter they remember didn't have, but going all in. In fact, I dare those who are fully convinced that Mastodon is perfect and fully-featured to do the same.
And then there's Hubzilla. It came to exist by Mike forking Friendica in 2011, then forking that fork the same year, then rewriting that fork of a fork in 2012, then repurposing, rebranding, repositioning and greatly expanding it in 2015. Long story.
Hubzilla adds even more stuff on top. Most importantly, it introduced nomadic identity (https://joinfediverse.wiki/Nomadic_identity) in 2012.
Hubzilla, or its 2012 prototype form named Red, became the first decentralised social software that uncoupled the identity from the login. This was necessary for nomadic identity, but it also introduced the option to have multiple independent identities, basically what's an account elsewhere, on the same account, the same login. This makes sense, given the many different roles and purposes a Hubzilla channel can have. The big advantage over having multiple separate accounts is that you can switch between the channels on your account without logging out and back in.
Hubzilla, or its 2012 prototype form named Red, got an even more advanced and fine-grained permissions system. Hubzilla has 17 individual permissions on three levels, channel level, contact level, content level. At channel level, each one has seven or eight permission options to choose from, depending on whether or not it makes sense to give a permission to everyone on the Internet.
Mike added optional features to Hubzilla that were previously unseen on social anything, features that you'd rather expect from a CMS and maybe not even from that. Non-federating long-form articles. Planning cards that are based on these articles. Wikis that can be formatted with BBcode or Markdown. Webpages that can be formatted with BBcode, Markdown or HTML, that can include dynamic content from elsewhere on the channel, and that can add extra content to the channel pages.
Hubzilla can even act as groupware. It has a CalDAV calendar server; the event calendar can double as a crude UI for the CalDAV calendars. It has an optional CardDAV addressbook server. Its built-in file storage can be accessed via WebDAV, so you theoretically even have some cloud file space you can mount as a network drive. Rather recently, there was even a way found to tie Collabora Office into Hubzilla.
If you should ever read about Bonfire: Bonfire is Hubzilla ordered from Wish.com. Whatever Bonfire promises to have or to introduce has been available as a rock-solid stable feature on Hubzilla for over a decade. Bonfire only gets away with what it's trying to do because nobody knows Hubzilla.
I think it's safe to say that those who "chose" Mastodon didn't choose it over the rest of the Fediverse because it's better. They "chose" it because they didn't even know they have a choice.
As for your post, the technology for redeveloping socialising is there. And it certainly isn't Mastodon, and it never will be Mastodon. Mastodon can't be that due to its design philosophy, due to it being a Twitter clone, due to its own developers intentionally crippling it.
If you want to move on from 1-way interaction, you have to move on from 1-way connections. Move on from Twitter followers to Facebook friends.
You have to offer better options for the users than shouting into the void, attaching a bunch of hashtags and hoping that some of their followers or someone who is following one of the hashtags happens to be bothered to scroll down their timeline far enough.
You have to make sure that people don't miss content due to basic design and philosophy decisions. You have to make sure that people don't miss content because they simply never know that this content is there in the first place, because they can't scroll down far enough their timelines until they reach that content. You need something else than a timeline of single messages to scroll down with the user not having an idea just how far down that timeline goes. You have to tell the user how much unread content there is, what it is, where it is, and take the user directly to that unread content.
You have to stop presenting content to users as a long list of single posts and more single posts with only tiny details telling them that these posts are, in fact, part of a longer conversation which they don't see. Where they have to click or tap themselves through various UI pages to see that post in its context. Users must see the whole conversation Right. Off. The bat.
You need groups. Not kluged onto something that had no group support whatsoever two seconds earlier, not intentionally crippled, not crippled by the technology they're built upon, not intentionally re-invented to be incompatible with whatever already exists (and this is how Mastodon would do them). But fully functional, on an appropriate base, interoperable, user-moderated, optionally private, optionally hiding from directories.
If you want to go "social", you really have to go social. You have to go Facebook, not Twitter.
Users must find other users based on common interests. Or users living close to them. Or users with lots of contacts in common with them. Not by being on the same local/regional server of the same server about a certain topic. Not by searching for hashtags in the main profile text. But by examining specialised profile fields and the contacts.
Users must have such users suggested to them as new connections. Users must have such users at the top of their directory. This is how Facebook does it. And this is one thing that Facebook has always done right.
Again, Mastodon will never offer any of this. But that doesn't mean that you'll have to compromise and lower your expectations. Because you don't have to. There are server applications in the Fediverse, fully federated with Mastodon, that offer literally all of that. They exist right now. And some of them have existed for longer than Mastodon.
If you need something better than today's Mastodon, stop wishing for a better Mastodon. Instead, use something that's better and more appropriate for the job than Mastodon right now. For it exists right now.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #Fediverse #Mastodon #MastodonFediverse #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse #Friendica #Hubzilla #Streams #(streams) #Forte #Privacy #Permission #Permissions #Groups #FediverseGroups #FediGroups #NomadicIdentity #MastodonCentricity #MastodonNormativity -
@Truth & Answers I've just come across a toot from a Mastodon user who demanded that everyone who posts, quote, "on Mastodon," end quote, limit their posts to 500 characters.
This was far from being the first time I've read this very demand or similar demands. It just was the most recent time.
Where this comes from? Well, it has two sides.The Mastodon side
One side are Mastodon users. Not all of them, but most of them. Literally all of them were on-boarded onto Mastodon with the notion that Mastodon is its own enclosed network with nothing else in it. Those who pull them on board either think it's easier for them to understand if they aren't told about the non-Mastodon Fediverse, or they don't know about the non-Mastodon Fediverse themselves.
Some of these newbies think Mastodon is the network because they've never heard of the Fediverse. Others think the Fediverse is Mastodon and nothing else.
My estimation, and not only mine, is that more than 50% of all Mastodon users think the Fediverse consists of nothing else than Mastodon. A great deal of the rest thinks the Fediverse doesn't extend beyond Mastodon, Pixelfed and PeerTube. Not much anyway.
It doesn't help that Mastodon, unlike other Fediverse server applications such as Misskey, the Forkeys, Friendica, (streams) or Forte, does not tell its users which server app a message came from. It doesn't help either that Mastodon "sanitises" away quite a few things that'd make non-Mastodon messages a dead giveaway. So the huge majority of Mastodon users believe that if they see it on Mastodon, it came from Mastodon.
So these people are dropped into a network which they think is nothing but a purist, minimalist microblogging service with no more than 500 characters, and whose only differences from Twitter are the name, that it isn't just one website, that it isn't owned by Elon Musk, and that it isn't overrun by fascists.
They get used to it. They get used to only having a maximum of 500 characters. They get used to the CW field being the CW field. They get used to Mastodon's entire culture which they see as the be-all, end-all of online culture.
And then they come across a message with a whole lot over 500 characters for the first time. Something which, to their best knowledge, shouldn't exist in the Mastodon Fediverse. Something which mustn't exist in the Mastodon Fediverse.
Some don't have any idea how it could be possible to "toot" more than 500 characters "on Mastodon", and they ask how one can do that. Others believe that all these "long toots" come from hacked Mastodon servers. Either way, they often demand that these Mastodon users adhere to Mastodon's culture and Mastodon's unwritten rules and act like all good Mastodon users shall act. Including not "tooting" more than 500 characters "on Mastodon".
Both are being told that these "toots" aren't "toots" because they don't come from Mastodon. That the Fediverse is, in fact, not only Mastodon. That there's other server software in the Fediverse that has always been able to post way more than 500 characters.
That changes nothing for them. They still demand everyone in the Fediverse adhere to Mastodon's culture and Mastodon's unwritten rules and only to these, and that everyone in the Fediverse use whatever they use exactly like vanilla, unmodified Mastodon.
And they feel absolutely justified. According to their gospel, Gargron invented the Fediverse when he created Mastodon. And everything in the Fediverse that isn't Mastodon (once they discover that there is such stuff) has either been designed as an add-on glued onto Mastodon (Pixelfed, PeerTube), or it's an evil, savage intruder (everything that's capable of largely doing the same thing as Mastodon without being Mastodon).
The Fediverse is to Mastodon users what the ancient world was to the Romans. Mastodon is the Roman Empire. Literally the only place that has got something like culture. A few places have voluntarily joined the Roman Mastodon Empire. All the rest consists of primitive, savage, culture-less barbarians whose lands need to be conquered by force to bring them culture.The non-Mastodon side
The other side are the non-Mastodon users. This sounds harsh, but while Mastodon users act by faith and belief, non-Mastodon users act by knowledge. It's them who know what the Fediverse really is. That there has never been a point in history at which the Fediverse has only been Mastodon. And that culture does exist outside of Mastodon. Only that these cultures are different from Mastodon's culture, largely because they're geared towards the technical capabilities of the underlying software.
To non-Mastodon users, the Fediverse feels like the New World when the European conquerors and settlers arrived. They demanded the natives adopt European culture and convert to Catholic Christianty or face death. The natives actually already had cultures. Cultures that suited them and their surroundings much more than the culture lived in European cities. But the Europeans didn't acknowledge the natives' cultures as such, nor did they care.
From non-Mastodon users' point of view, Mastodon users act to them like the Europeans acted to the natives in their colonies-to-be.
A very good example, also because it's such an extreme example, has to be Friendica. In case you don't know, Friendica (https://friendi.ca; https://en.wikipedia.org/wiki/Friendica; https://joinfediverse.wiki/Friendica) is a free, open-source, decentralised, federated Facebook alternative that first came out as early as May, 2010. Friendica developed a wholly different culture from Mastodon's because it's vastly different from Mastodon.
Mastodon's culture was mostly coined in mid-2022 by those who escaped from Elon Musk's announcement to buy out Twitter in February/March, 2022.
Friendica's culture was coined by its early users in 2010 already.
Mastodon users are mostly used to living in a Mastodon-only network with no connection to anything that isn't Mastodon. They believe that Mastodon and the Fediverse were designed as such, and that Friendica is an illegitimate intruder.
Friendica users are used to being able to connect to everything that moves, including Mastodon, including the whole Fediverse, no matter which iteration of the Fediverse, including diaspora*, and the some. That's because Friendica was designed from the ground up to be able to connect to a whole lot of stuff. It's part of its concept.
Mastodon users believe that Mastodon was there before anything.
Friendica users know that Friendica was there long before Mastodon, even before diaspora*, and that Friendica still wasn't the first.
Mastodon users are used to only having 500 characters. They still consider that a lot in comparison with Twitter's 280 characters.
Friendica users are used to not having any character limit whatsoever. Friendica's actual technical character limit is imposed by the maximum size of the message text database field, and that's over 16.7 million characters.
Mastodon users are used to chopping long posts into threads. It's what they expect. Actual long posts irritate them.
Friendica users are used to posting long post in one piece. It's what they expect. One and the same post being chopped up into itty-bitty bits irritate them.
Mastodon users are used to putting CWs in a dedicated CW field.
Friendica users are used to the self-same text field actually being a summary field (Friendica calls it "abstract"). While Mastodon got that field in 2017 as a pull request from a user, Friendica had it from the get-go, i.e. since 2010. And Friendica actually adopted it from Evan Prodromou's decentralised Twitter alternative StatusNet from 2008 with which Friendica was able to federate with from the get-go as well.
Mastodon users "know" that Gargron invented the CW field.
Friendica users actually do know for a fact that they've had the same field as a summary field since long before Mastodon was even made. There are still enough Friendica veterans around from before 2016.
This also means that Mastodon users are used to poster-side CWs which all readers get just the same.
Friendica users are used to CWs being automatically generated on the reader's side, individually for each reader, by an optional text filter.
In fact, Mastodon can do the same. But nobody knows, it came way too late to become part of Mastodon's culture (Mastodon 4.0 in October, 2022), it's too tedious to use, it probably isn't supported by that many phone apps, and next to nobody uses Mastodon's Web interface. In the meantime, Friendica has had this feature for some twelve years longer, and it's only an on-off switch and one editable keyword list.
Mastodon users are used to only having up to four images and to images always only being file attachments dangling below a post.
Friendica users are used to being able to embed a virtually unlimited number of images to a post. And to actually embed them, as in, with text above the image and text below the image and another image below that text and more text below that image. Theoretically, they could insert tiny images into lines of text. By the way, Mastodon refuses to display embedded images. It also rejects any file attachments beyond the first four. And up to version 4.0 from October, 2022, it didn't support any kind of text formatting and "sanitised" all message texts down to plain text.
This also means that Mastodon users are used to only having plain text or mucking around with Unicode characters for bold type and italics.
Friendica users are used to being able to not only see, but also post all sorts of text formatting that HTML is capable of.
Mastodon users are often deadly afraid of quote-posts because they only know quote-posts as a means of harassment and dogpiling on Twitter.
Friendica users, their entire culture being entirely unfazed by whatever has ever happened on Twitter, are absolutely used to always having had quote-posts at hand and to using quote-posts as a means of forwarding content. They had what Mastodon calls "quotes" years before they had what Mastodon calls "boosts" (and what many Mastodon users refer to as "retoots").
Mastodon users are used to conversations being loosely tied together from toots and to having to visibly mention all those whom they want to receive a reply.
Friendica users are used to having enclosed threaded conversations with only one post and otherwise only comments. They're also used to everyone in the conversation, i.e. everyone who has received the original post, automatically receiving every single last comment. They're used to always seeing the entire thread immediately as opposed to single-message piecemeal.
Mastodon users are used to shouting into the void with hashtags attached if they want to talk about a certain topic. It's the only way for them to do so.
Friendica users are used to having groups. Oh, and full-text search.The conflict
It should be obvious that these two types have a very high chance of not getting along, especially if the Mastodon user is fairly new and not used to there being stuff in the Fediverse that's nothing like Mastodon.
Mastodon users keep demanding that everyone else in the Fediverse live by Mastodon's culture and Mastodon's rules and only by these.
Mastodon users who have joined in 2026 keep ordering Friendica veterans who have joined in the early 2010s (before there was any Mastodon) to act like they're on Mastodon.
They demand these Friendica veterans fully adopt Mastodon's culture (which isn't even geared towards Friendica's set of features).
They indirectly demand these Friendica veterans give up their own culture (because they cannot comprehend that there can be any other culture in the Fediverse than Mastodon's, as in, that what Friendica has is a culture, even though it's different from Mastodon's).
They directly demand these Friendica veterans give up some 40% of the features they've been using for a decade and a half and indirectly demand they give up another 40% of these features.
They demand these Friendica veterans stop posting more than 500 characters at once.
They demand these Friendica veterans put CWs into their abstract field. (Again, they think that Gargron has invented this field from scratch as a CW field,)
They demand these Friendica veterans use their abstract field only for CWs.
They demand these Friendica veterans stop "spamming" hashtags that clearly aren't there for content discovery. (They cannot comprehend that these hashtags are there to trigger automatic reader-side CWs because the entire concept is completely alien to them.)
And so forth.
These Friendica veterans have been in the Fediverse for about a decade and a half. And suddently, these Mastodon newbies appear and tell them how to use Friendica.
Of course, these Mastodon newbies don't know a thing about Friendica. They think the Friendica veterans are Mastodon users, and they're telling them how to use Mastodon.
So the Friendica users tell them, no, they aren't on Mastodon. They're on Friendica which has got absolutely nothing to do with Mastodon.
Then the Mastodon newbies will believe that someone has created this weird Friendica thing after Mastodon was made (it can't possibly be any other way, right?9 and illegally hacked this Friendica thing into the Mastodon Fediverse. And whoever made Friendica omitted to make Friendica just like Mastodon.
Okay, now the Friendica users tell them that Friendica was launched in 2010, how long before Mastodon that was, and that they themselves have been around for much longer than Mastodon, too.
Now, either the Mastodon newbies will fail to comprehend that there can be anything in the Fediverse made before Mastodon if Gargron has invented the very technology. Or they think that the Fediverse was still created with Mastodon, and that Friendica still illegally intruded into the Mastodon Fediverse.
Either way, the Friendica veterans will have to adapt and act entirely by Mastodon's standards. This is the Mastodon Fediverse, Mastodon is the biggest software (if only by monthly active users, by the way), Mastodon has defined "the Fediverse culture", and thus it's the Mastodon users and only the Mastodon users who get to say how people have to act and behave in the Fediverse.
And then the Mastodon users wonder how there's so much Mastodon hatred on Friendica (and there actually is). How Friendica users complain about Mastodon users trying to force them to use Friendica like Mastodon. How Friendica users complain about Mastodon users chopping long posts into small bits. As if they had a choice. How Friendica users complain about CWs in whatever that abstract field is supposed to be. And so forth.
How dare the Friendica users complain? The Mastodon users are the good guys! It's them and only them who have a culture, who have rules, who know how to use the Fediverse!
By the way: It gets even worse between Mastodon and Lemmy.
Mastodon's culture is an idealised version of pre-Musk Twitter's culture with bits of Tumblr's SFW culture mixed in. That's because just about everyone on Mastodon originally came from Twitter, and most of them escaped from Elon Musk. They want Mastodon (and the Fediverse) be a better Twitter. It helps that Mastodon is still trying hard to be a Twitter clone.
Lemmy's culture, on the other hand, is a carbon copy of Reddit's culture. Lemmy is a Reddit clone that shares next to no features at all with Mastodon except for ActivityPub support. Next to all Lemmy users are former Redditors who left Reddit when Reddit started charging $20,000,000 for its client API, effectively killing off all third-party Reddit apps. They saw no reason in changing their culture because it wasn't the culture that drove them away. Hardly any of them were on Twitter, and almost none of them have ever been on Mastodon. Many think the Fediverse is Lemmy. Of the rest, many think the Fediverse is Lemmy with a side of PieFed.
Mastodon lives on hashtags even more than Twitter. Lemmy has zero support for hashtags because Reddit doesn't have any either, and neither does Hacker News.
Mastodon requires mentions to get replies to their recipients. One visible mention per recipient. Lemmy doesn't need mentions for this at all. Mentions on Lemmy only serve to, well, mention someone. Just like on Reddit.
And so forth.
It's actually easy to spot threads on Lemmy that were started by Mastodon users: The title is in the post text, or there's no title at all because the Mastodon users did as they always do: mention in the first line, then a new line because that looks prettier. Of course, there's a mention in the post text. And there's a bunch of hashtags strewn across the post text even though they don't even work. If you're very lucky, the hashtags are at the bottom, but most Mastodon users don't waste any of their 500 characters on that.
I hope you get a rough idea how much headbutting there is between Mastodon users who think that the Mastodon users rule supreme over the whole Fediverse and Lemmy community owners who do rule over the Lemmy communities which these Mastodon users have just posted into.Countermeasures
Both sides are actually taking countermeasures. The non-Mastodon side is more effective at it, though.
On Mastodon's side, there are very few single users who block every single non-Mastodon server they come across.
Countermeasures on the non-Mastodon side vary. They start with single users who block each Mastodon user who doesn't behave like they want them to behave, e.g. they block everyone who chops a long post into a thread at first trike.
Then there's Hubzilla, reworked from a fork of a fork of Friendica by Friendica's own creator. Hubzilla has always been based on its own protocol, Zot6 (Friendica's creator calls it an older version of Nomad). ActivityPub support is optional, on by default on new servers and off by default on new channels. The current devs won't change anything about that. Not only doesn't Hubzilla's technology allow for moving it to ActivityPub as its base protocol, but ActivityPub being optional is seen as a last-resort "drawbridge" for those to whom Mastodon has become unbearable.
Nowadays, Friendica's creator is working on two other applications in the same family. (streams) is a fork of a fork of three forks of a fork (of a fork?) of Hubzilla, and Forte is a fork of (streams). Both have an admin-side user agent filter. It can block entire Fediverse applications without having to hassle around with a URL list. It was mainly created and advertised as a means to permanently lock Threads out, even if Threads should change URLs. But it's also being advertised as being capable of blocking all of Mastodon, all present and future servers. Mastodon being intentially made barely compatible with the rest of the Fediverse is only one reason for this.
(streams) and Forte also have another admin-side filter which, when turned on, locks everything out that doesn't support enclosed threaded conversations. That's because server applications like Mastodon mess with the way that (streams), Forte and their ancestors handle conversations. Granted, when this is activated only to get rid of Mastodon, it causes quite a bit of collateral damage.
Generally, (streams) and Forte are very similar. The main difference is that Forte is entirely based on ActivityPub whereas (streams) is based on the current version of Nomad with ActivityPub still being optional. The reason why (streams) is kept around is for there to still be one of these applications with the same protocol-level "drawbridge" as Hubzilla. And in fact, the most important (streams) group used to have ActivityPub off with the intention to keep Mastodon out.
I guess there are still Mastodon users who absolutely defend and support Mastodon's way being forced upon the non-Mastodon Fediverse, and who are irritated or upset about non-Mastodon users being very defensive of their own non-Mastodon ways and refusing to adopt Mastodon's (allegedly much superior) culture instead of embracing it.
And I guess there are Mastodon users who feel absolutely entitled to get to every last Hubzilla and (streams) and Forte user unhindered and force them to use Hubzilla/(streams)/Forte exactly like Mastodon in every way possible.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta #Fediverse #Mastodon #MastodonFediverse #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse #Friendica #Hubzilla #Streams #(streams) #Forte #Lemmy #MastodonCulture #FediverseCulture #MastodonCentricity #MastodonNormativity -
-
Re: https://sunny.garden/@ignova/116948343401616794,
Have you ever skipped reading a post or an article because of a #CW?
Boosts welcome.
-
RE: https://federate.social/@mattblaze/116938705958947037
Having perused this dialogue, I've come to the following opinion: no one should be obligated to write content warnings, however, they should probably *want* to write content warnings, given that it's an easy thing you can do to avoid causing harm to other people.
The issue is that I don't know what kinds of triggers people have. Some are quite obvious, but some are somewhat less so. I know of people who are sensitive to a particular song, for example. Obviously one has to draw a line somewhere, deciding which topics are obviously going to be triggering to a lot of people and which ones are far too unlikely to cause serious distress. But this method of guessing is liable to failure and it could still end up causing someone some harm.
My question is this: is there a big list of topics that people often find triggering which could be used as a guide for what ought to be given a content warning? I'm not talking about instance guidelines, but rather a sort of compendium of triggers with maybe some brief explanations for why the terms are triggering.
Obviously this doesn't ‘solve’ the problem either, but it could help people who are less clued‐in (like myself) to avoid making more obvious mistakes.
-
Foto of a dead body in my timeline yesterday, another one today.
I don't think I'm particularly sensitive when it comes to CWs, but can we please CW truly gory fotos like these?
And those looooooooong posts that feel like a whole book... for convenience.
-
I called CQ on #cw for the first time tonight.
When I heard someone answer I was so startled that I very nearly just switched off the radio instead of working them 😂
