I am about to make a simple automatic plant grow system, based on an ESP8266. Luckily I got a #Chirp from Catnip Electronics https://wemakethings.net/chirp/ at #37c3 which covers pretty much all of the parameters, I want to measure ^.^
Thanks again to @miceuz who gave it to me for free! :)
We're one week into 2024, do you know what that means? Time to clean up your #SNS “following” especially here in the #Fediverse.
Check the “dormant” accounts if you can unfollow them.
Check which accounts “moved”. Follow their new account, then unfollow their old account.
And maybe there are other accounts that you haven't interacted with in the past few months; and their content is no longer something that you are interested, you can unfollow them too.
If you still want to see their content, you can encourage them to use #hashtags and you follow those hashtags. Or, join a federated “group” like those powered by #Mbin#Kbin#Friendica#Chirp and #Lemmy.
Of course, depending on the fediverse platform your instance is using, there are probably better features to the content of users without seeing their content that is not of interest to you. A good example, #Firefish / #Catodon / #IceShrimp can do that through the “Antenna” feature.
Take some time to do this, and start your 2024 fediverse better than 2023.
@retrobeetism I have a similar experience. #Guppe groups (at least after it went offline for almost a month(?)) rarely works all other #Fediverse platforms (those I've tried). But #Chirp groups, #Friendica forums, #Kbin magazine, and #Lemmy communities, there are rarely any problems.
My brain tells me that the issue is with Guppe platform, since all other similar software works fine. They did something to break interoperability with the rest of the Fediverse, and created its own bubble with Mastodon.
#Guppe for us has been a problem for a long time. Users on our Firefish server just can't follow them. #Chirp too has issues. Especially inbound. The responses are malformed. Right now I have 11 in our Inbound queue which will eventually fail and disappear, so the subscribe user will never see the message.
From what others more knowledgeable that me have said, the implementation of ActivityPub for these services is poorly constructed and have been cobbled together for Mastodon servers
Hey #fediverse, does anyone know if a.gup.pe and chirp.social has some sort of #API which lists all groups in it? I've just thought of an idea to make this #GoToSocial instance I manage federate even more instances than just 600+ servers, which is to #massfollow them all with a #followbot. Yeah it's a really bad thing to use against normal instances (it's gonna annoy humans behind the accounts), but it shouldn't be a problem if I just follow group accounts, right? :sagume_think:
I'm gonna also try mass following every community in #Lemmy and #kbin as well.
Mit den vielen neuen #Gruppen im #Fediverse geht euch vielleicht ein wenig die Übersicht verloren. Zum Glück gibt es in #Friendica eine Möglichkeit direkt nach Gruppen zu suchen und diesen zu folgen. Damit entfällt die #Suche auf externen Seiten.
Die Suche wird statt eines "@" mit einen "!" eingeleitet. In der Treffervorschau werden euch alle Gruppen angezeigt, die zu diesen Namen gefunden wurden. Die Trefferliste liefert euch gleich noch die korrekte Adressierung zum Abonnieren einer Gruppe.
It depends on how you look at it. There are thousands of fediverse servers, and there are at least a million active users in total.
Based on the context of this discussion thread/branch, those Lemmy servers mentioned would not even fall near the “dominating the network”, they are very far from dominating the fediverse network.
But, if you are referring to “Reddit-like / Stackexchange-like / Quora-lack”, then sure, those servers mentioned are “dominating” the “answers UI/UX” space. However, the fediverse doesn't work like that, and you probably won't even notice it while using any fediverse software.
In the fediverse, #Lemmy and #Kbin servers acts like a group. If you have used #Chirp and #Guppe groups (chirp.social and a.gup.pe respectively), then Lemmy and Kbin servers works similarly.
If I post to a Lemmy “community” or to a Kbin “magazine”, that post will be re-shared/boosted/re-posted to everyone who subscribed/followed that community/magazine. Anyone who replies to that post, it will be re-shared/boosted/re-posted also.
In other fediverse software, it will just appear as a regular status update thread. In Lemmy and Kbin, it will appear as a comment to a certain post.
It's the same for, say, #BookWyrm. The flagship BookWyrm server is “dominating” the “bookshelf UI/UX” space, however, outside of that, it's just another software. The only difference is that with BookWyrm, you get a shelf, track your book reading, leave reviews to a specific book, and so on.
However, everything else are the same… if you leave a comment or posts an update about the book you are reading, it is no different from using #Calckey, #Hubzilla, #Friendica#Misskey, #Rebased, #Akkoma, #Mastodon, #Pleroma, to post a new update that “I am not at page 879 of the book ‘Shaka. When the Walls Fell’.”
And as far as the fediverse is concerned, BookWyrm is far from “dominating” the network.
II. Music industry
@-ppop@chirp.social
@-kpop@chirp.social
@-jpop@chirp.social
@-cpop@chirp.social
III. Asian dramas
@-pdrama@chirp.social
@-kdrama@chirp.social
@-jdrama@chirp.social
@-cdrama@chirp.social
Just remove the hyphen.
It is highly advisable that we always tag at least two similar groups (located on different servers) to ensure continuity of discussions in case one goes down. (If one goes down, then someone needs to create another duplicate located in another server for the exact same reason… continuity and redundancy.)
deleted_by_author