Search results

@Julian Fietkau I'm surprised to read that (streams) allegedly has FEP-e232 implemented. As I happen to have two (streams) channels myself, and as (streams) allows me to have a look at the whole source code of any activity (whereas Hubzilla only shows me that of the content), I've checked a fairly recent post of mine that includes a link. And while it does define the hashtags just like Mastodon and Hubzilla, it does not define links in a way that conforms to FEP-e232. Either that, or (streams)' implementation of FEP-e232 is newer than the software was when I sent that post.




Next, I wanted to see if (streams) had its way of quote-posting changed in the last seven years or so of development and forking. I expected it to quote-post like Hubzilla, namely by turning a BBcode short code into a dumb copy of the original upon sending, but I wanted to see proof. As (streams) is a fork of a fork of three forks of a fork (of a fork) of Hubzilla that's still maintained by Hubzilla's own creator, I would have been surprised if he had changed the way (streams) quote-posts at some point on the way.

So I quote-posted my own post on (streams) just to see what happens. And (streams) acted exactly like Hubzilla and not at all like described in FEP-044f on the surface. It still inserts a dumb copy.

Good thing I have access to the full source code of any message on (streams). So here's what happened, namely what I expected to happen: (streams) quote-posts like Hubzilla.

First of all, when I clicked the "Share" button, this short code was inserted into the post editor:

[share⁠=1198713][/share]

The number, by the way, is the running number of the message to quote-post on the server.

Upon sending the post, (streams) automatically "expanded" the short code into the dumb copy I had expected.

[⁠share author='Jupiter+Rowland' profile='https://hub.netzgemeinde.eu/channel/jupiter_rowland' portable_id='_moYLN61-o3FbP3jyThygMDf-bjF2cApXgkrwlAE77iKy19xM1_6F06V4b71eTkqqNaTUjGiN0lfw2dyn5nXRw' avatar='https://streams.elsmussols.net/xp/6b50efa4bb804860f6128bba791b74fab4a0a5e09dbcbee8d8ca77cee00f0330-6' link='https://hub.netzgemeinde.eu/item/0a1cdda5-eb1c-4a33-9574-ddd896977b4f' auth='true' posted='2025-09-21 19:42:56' message_id='https://hub.netzgemeinde.eu/item/0a1cdda5-eb1c-4a33-9574-ddd896977b4f'] ...(the source code of the original message goes here)... [/share]

Both Hubzilla and (streams) render this the same way, namely with a header line above the copy that includes the profile picture of the original author, the name of the original author with a Zot/Nomad-type link to their channel/account and a Zot/Nomad-type link to the original of the post ("Zot/Nomad-type" means that [zrl][/zrl] is used rather than [url][/url] which means that the ID of an observer on Hubzilla/(streams)/Forte is attached to the link for OpenWebAuth identity recognition purposes.)

At the same time, curiously, (streams) includes the line "rel": "https://misskey-hub.net/ns#_misskey_quote" and a line that starts with "name": "RE: and continues with the URL of the original message into the code for the link to the original message. The latter is identical to what Misskey and all Forkeys have in quote-posting notes in plain sight, only that (streams) only reveals it in the source code rather than in the content as well.

So this part of FEP-044f is implemented, albeit concealed from most people and only happening in the code.




Now, looking at the quote policy part, that looks like it could be possible to add to the Fediverse's permission champions Hubzilla, (streams) and Forte. After all, they already have comment controls with no FEP backing it (and if GoToSocial's quote policy can be made into an FEP, maybe so can (streams)' and Forte's comment controls so that they actually do blank out reply buttons on the farther ends of the Fediverse if the software on the farther ends implement support for that FEP).

This could be done at three levels again. I'll illustrate this with (streams) and Forte because they're quite a bit less complex than older Hubzilla.

At channel level, quote-posting (and maybe quoting as well) could be set as usually, namely to semi-public (= everyone in the Fediverse = no quote policy), restricted (= only your contacts) and only yourself. (Seriously, you don't want random passersby with no accounts to quote-post you. Even though you can allow them to comment on your posts if you dare.)

"Only yourself" could be overridden at contact level by permitting certain contacts to quote-post (and maybe quote) your messages. This is actually standard behaviour on (streams) and Forte.

And then there is the per-post level which would be similar to (streams)' and Forte's comment controls. These allow you to limit who may comment on a post to only your contacts and those who have already participated in the same conversation, and they allow you to turn off comments altogether.

Quote authorisation would not be much different in handling from manually moderating comments from those who technically aren't permitted to comment (only that spammers don't quote-post, at least not yet, and they probably never will because that simply makes no sense). So that'd be nothing really new.

Of course, this would have some limitations which come from how Hubzilla, (streams) and Forte work and from their conversation architecture.

The first limitation is that you could only give certain contacts permission to quote-post your posts if you didn't give it to the whole Fediverse. Channel-wide permissions are always inherited by contact-specific permissions, and this cannot be overridden. So you couldn't generally allow everyone to quote-post your posts except for one certain contact of yours.

The second limitation is that you can only control the permissions of contacts, but not of non-contacts. So you can't disallow some stranger whom you aren't connected to to quote-post your posts while everyone else is allowed.

Then again, FEP-044f doesn't make either of these two possible either. It can only define who is permitted to quote-post a post, not who isn't.

The third limitation is that, on Hubzilla, (streams) and Forte, comments always have the same permissions as the post that they belong to because comments always have the same owner as the post that they belong to. Basically, if FEP-044f was to be defined for each comment individually, it would have a chance of clashing with conversation containers as per FEP-171b.

Here on Hubzilla, as well as from (streams)' point of view, everyone's comments in this thread are owned by me because I've started the thread. And the permissions on all these comments are defined by my post. I've seen my share of permission clashes whenever someone on Mastodon replied to a public post or a public comment with a DM, and Hubzilla overrode this by forcing the permissions of the post on that reply.

In practice, this means that the quote policies of all comments would be the same as that of the post. At least that's how Hubzilla, (streams) and Forte would understand them because the concept of comments having different permissions than the post is alien to them. So if you say that I'm not permitted to quote-post your comment, but I say that anyone can quote-post my post, Hubzilla and (streams) override the quote policy that you've given your comment on Mastodon with the quote policy that I've given my post on Hubzilla, and I can quote-post you.

So the actually difficult part would be to implement an exception in how Hubzilla, (streams) and Forte handle comment permissions for quote policies and make them individual for each comment rather than making comments inherit them from the post.

Well, and lastly, if you permitted all your contacts to quote-post a post of yours, and you had a few more contacts, the "canQuote" section would end up monstrous. (A bit less so if you could cherry-pick those who are allowed to quote-post you on a per-post base, just like you can cherry-pick those who are allowed to see the post in the first place.) Also, I'm wondering just how well policies as per FEP-044f (and their implementations in various server applications) will work with DIDs as per FEP-ef61 which (streams) and Forte use, and I guess, so does Mitra now.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Misskey #Forkey #Forkeys #GoToSocial #Hubzilla #Streams #(streams) #Forte #Mitra #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #Permission #Permissions #FEP_044f #FEP_171b #FEP_e232 #FEP_ef61
0

Lads lads lads lads!

Here's the first release candidate for v0.20.0 of #GoToSocial! If you're feeling bold, you can try this release candidate and help us find any lingering bugs before we release v0.20.0 proper!

https://codeberg.org/superseriousbusiness/gotosocial/releases/tag/v0.20.0-rc1

Please read the migration notes carefully for instructions on how to upgrade to this version.

The migrations in this release are quite long (can take several hours, even!), as we had to rethread the entire statuses table to handle the new way we cache status threads (and to improve timeline performance). Please plan downtime accordingly, and most importantly hang in there and don't be tempted to interrupt the migration process!

Please also pay particular attention to the metrics changes, as we've significantly changed the way that metrics exposure is configured, so you will likely have to adjust your setup if you use GtS Prometheus metrics. For more information on the new way of doing things, look through this document: https://docs.gotosocial.org/en/latest/advanced/metrics/

Release highlights

  • Big refactor of timeline code to use less memory and be (hopefully!) more responsive and less error prone.
  • Support for scheduled statuses!
  • Support for the focal point property on the frontend + over federation, so you can set focal point on your media and have it work properly!
  • Notifications when a status you've interacted with has been edited.
  • ListenBrainz widget on the frontend, so you can show off the music you've been listening to (https://docs.gotosocial.org/en/latest/user_guide/settings/#profile-fields)
  • Instance info panel in the settings, so that non-admins on the instance can see which domains are blocked and explicitly allowed, and the reason why.
  • Bunch of new themes for profile views!
  • Config option to expose emoji endpoints without authentication -- useful for compatibility with some clients. Default value still requires authentication.
  • Footnotes in markdown!
  • Configurable thumbnail dimensions.
  • Federation of avatar + header image descriptions is handled now, both in + out of GtS.
  • The new hidesToPublicFromUnauthedWeb and hidesCcPublicFromUnauthedWeb are federated in and out now, allowing your instance and other instances that support these properties to transmit + respect preferences for the visibility of posts to render on the unauthenticated (public) web view of threads.
  • Support for avif file format.
  • JSON logging format, for easier log ingestion.
  • Atom and JSON feed support for RSS (not just xml).
  • Reworked metrics format, more + better metrics, and an importable example grafana dashboard.
  • Domain permission subscription retractions are now handled properly.
  • Probably a lot more! See below!

Thanks for reading!

0
0

Me revoici dans le Fédivers sur ma propre instance, cette fois de #GoToSocial, mais toujours hébergée chez OVH à Beauharnois.

Je ne pourrai plus dire que je « pouet »...
Au fait, ça ressemble à quoi un cri de paresseux (la mascotte de GoToSocial)? 🤔

Logo de GoToSocial
0

Me revoici dans le Fédivers sur ma propre instance, cette fois de #GoToSocial, mais toujours hébergée chez OVH à Beauharnois.

Je ne pourrai plus dire que je « pouet »...
Au fait, ça ressemble à quoi un cri de paresseux (la mascotte de GoToSocial)? 🤔

Logo de GoToSocial
0

Hello, hello!
Maybe it's time for an #introduction / #newhere #neuhier:
My name is Jan and I'm not so new to the fediverse anymore. My main account is @radiyanjan Langhammer .
Some months ago I stumbled across #gotosocial and decided to set up my own instance - especially dedicated to #radio #audio (yes, birds, as well) and #radioart.
More info can be found in the profile-description and/ or on my main account.
Very glad for beeing here - in the #fediverse - among so many amazing people and projects.
So long and thanx for all the birds!

0
0
screenshot of fedialgo demo app
0

Does anyone know of a public set of ModSecurity exceptions for the fediverse/ActivityPub I can take a look at? I'm setting it up for GoToSocial and Mastodon now and manually doing this is pain.

Update, @cloudymax and I started a plugin here:
https://github.com/small-hack/argocd-apps/blob/2b7995c6fae5ecbb3944c6c6f4b139d98b76e67f/ingress-nginx/modsecurity_plugins_configmap.yaml#L177

Still happy to collaborate on it, but also wanted to note there was a mention a year ago about making an ActivityPub plugin over at the OWASP CRS repo, so maybe we could donate to that if its ever created:
https://github.com/coreruleset/coreruleset/issues/3497#issuecomment-1902181156

#WAF #modsecurity #nginx #apache #firewall #webApplicationFirewall #mastodon #gotosocial #activitypub

0

#AskFedi question to fellow #GoToSocial account holders who are on #YunoHost:

I've noticed that lately some posts I publish on here take in between 10-15 minutes to federate.

Are you experiencing the same thing?

And no, I haven't updated to the latest version of YunoHost, which was just released.

I also wonder if this is the right code to restart my GoToSocial instance?

sudo systemctl restart gotosocial.service

In case I wanted to restart that and not my whole VPS (which also hosts PeerTube, NextCloud and so many other things).

Any advice would be greatly appreciated!

0

Ω🪬Ω
New version (v1.1.0) of , the customizable timeline algorithm / filtering system for your Mastodon feed, has a toggle switch to allow or disallow the selection of more than one filter option for when you're checking out your favourite hashtags.

* Link: michelcrypt4d4mus.github.io/fe
* Code: github.com/michelcrypt4d4mus/f
* Video of FediAlgo in action (slightly out of date): universeodon.com/@cryptadamist

screenshot of fedialgo multiselect for hashtag filters
0
0
0
0

Dumb question that I was always too afraid to ask:

I know how the #Fediverse and its federation works. It's intuitive and familiar to me; I mean, I even host my own instance.

But I never understood how interaction cross-software is supposed to work. In theory, I can use whatever #ActivityPub software I want and still interact with everyone else. But in practice that just... isn't the case, right?

I mean, for text it's quite simple: I write a short post on #Mastodon and people on #GoToSocial or #Misskey or whatever can see and read that same post and interact with it. They can see my profile and it appears on their instance in their style and with their features.

Even outside of microblogging I still get it. A super-long post on #Friendica or #Diaspora appears on my timeline, too. Their profiles might have more fields than I can see here, but that's fine.

But what's up beyond that?

I can see #Pixelfed posts here, converted into image galleries. But what about the other way 'round? If someone on Pixelfed follows my Mastodon account, they can't see any of my non-image posts, right?

What about #PeerTube and such niche software? I guess I could follow a PeerTube account as a microblogger and see their videos and descriptions in my timeline. Video comments are replies.

But the other way 'round? How are they supposed to interact with Friendica or Pixelfed users? PeerTube doesn't even have a "timeline".

Doesn't that feature disparity undermine the whole idea of the #Fediverse or am I missing something?

#AskFedi #FediAdmin

0
0

🐛 GTS-HolMirDas v1.2.1 Released - Important Bugfixes

Fixed some critical issues that prevented the RSS-based content discovery from working properly. Thanks for sharing, @christianteqqy

🔧 What's Fixed:

  • Inline Comment Support: Fixed parsing of RSS feeds file when using inline comments
  • Control Character Error: Resolved "URL can't contain control characters" error caused by comments in same line as URLs
  • RSS File Parsing: Comments after # are now properly stripped from URLs
https://mastodon.social/tags/homelab.rss    # 20 posts default
https://fosstodon.org/tags/docker.rss?limit=50   # 50 posts

📦 Update Instructions:

# Download latest version
wget https://git.klein.ruhr/matthias/gts-holmirdas/raw/v1.2.1/gts_holmirdas.py

# Restart your container
docker compose restart gts-holmirdas

#GoToSocial #RSS #ContentDiscovery #SelfHosting #OpenSource #Federation #Homelab #Docker

0

@julian So all this is just an elaborate ploy to convince Mastodon devs to display summary? It might make sense, but then I don't understand why it is presented as a protocol problem.

The FEP won't make any difference. I've spent of lot of time tweaking my software in order to make rich content look good across the Fediverse (including Mastodon), and I can confidently say that Long form text FEP is not helpful at all. It is a mix of obvious requirements (which are already present in AP & AS), some arbitrary recommendations (like the set of allowed tags), and bad ideas (like the preview property). This is because it is not written by a developer: the author simply doesn't know what needs to be done in order to render an article across 10 different implementations.

When it comes to long form content, the best resource is @helge 's support tables. For example, there is an analysis of what HTML tags are supported in Article.content: https://funfedi.dev/support_tables/generated/html_tags_article/

No one talks about this project, but it is far more useful than anything done so far by the so called "longformers".

@developer @mikedevMike Macgirvin 🖥️ @jupiter_rowland @feb

@silverpill Who are the longformers anyway?

They're those who either are commercial or looking for professional/commercial users or both. Flipboard. Automattic (WordPress). Ghost. These kinds.

They know themselves. They know each other. And they know Mastodon. And that's it.

None of them has ever heard of Pleroma or Akkoma.

None of them has ever heard of Misskey or the Forkeys.

None of them has ever heard of Mitra.

None of them has ever heard of GoToSocial.

None of them has ever heard of Hollo.

None of them has ever heard of Friendica, Hubzilla, (streams) or Forte, even though Friendica and Hubzilla are both older than Mastodon. And apparently, neither has @Helge. But then again, Friendica and its nomadic, security-enhanced descendants are being overlooked by almost everyone. That's why there's always on-going work for features to be "introduced to the Fediverse" which Friendica has had for a decade and a half.

Granted, the HTML support on Friendica, Hubzilla, (streams) and Forte can be summarised with "yes". But elaborate tables that show what either of them supports how would be very useful.

Also, granted, everything I've mentioned above (normally) uses something else than HTML for formatting in the frontend. For example, Misskey and all Forkeys use MFM ("Misskey-Flavoured Markdown"). Friendica uses extended BBcode with the option to use Markdown instead. Hubzilla uses even more extended BBcode. (streams) and Forte can use the same even more extended BBcode and Markdown and HTML at the same time within the same post, although not all markup languages support all features.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Pleroma #Akkoma #Misskey #Forkey #Forkeys #Mitra #GoToSocial #Hollo #Friendica #Hubzilla #Streams #(streams) #Forte #LongFormContent #BBcode #Markdown #HTML #TextFormatting
0
screenshot of fedialgo demo app
0
0
0
0

🏕️ my adventures in self-hosting: day 220 (roller coaster edition) 🎢

A new blog post where I discuss how sanity prevailed and I will NOT install my own Lemmy instance. But! Now I'm tempted to set up something else. Thankfully reality for now is disrupting my fanciful plans.

🔗​: https://news.elenarossini.com/my-so-called-sudo-life/my-adventures-in-self-hosting-day-220-roller-coaster-edition/

#MySoCalledSudoLife #Sharkey #Friendica #GoToSocial #YunoHost #Docker

0
0

Question for #FediAdmin , especially the ones managing a single-user instance (or just with very few users):

How much RAM is currently using your fedi software, whether it is #Mastodon #Akkoma #GoToSocial or one of the fifty shades of #Misskey (and by RAM I'm meaning "in total", not just the software's main process, also the database and additionnai stuff)

It's really out of curiosity. For instance, soc(dot)breadcat(dot)run currently uses approx 4,5Gb (4Gb for Akkoma's main processes and ~500Mb for the DB, on Docker)

Repost appreciated :nice-three-hearts:
0

For today's , I'd like to thank everyone who supports the Fediverse. So, that means *you*. Yes, you, the one reading this.
Thank you!

The Fediverse truly is for everyone: if you don't have the skills or means to set up your own instance, you can join one of the public instances that aligns with your aspirations. If you can and want to, you can create your own instance, and thanks to lightweight (and interoperable) software, you can do it with spare hardware or very affordable VPS.
So thank you to all of you, friends of the Fediverse!

0
0
screenshot of fedialgo in action
0

🏕️ my adventures in #selfhosting - day 198 (summer project edition) 🏖️​

Hello Fedi friends,

I hope you've been having a nice week so far.

I've been in childcare mode, thus the silence. I've been thinking about something and I would love to get your advice.

#AskFedi: is there a way to export one's #GoToSocial archive of posts (but not replies to other users)? Like something with command lines that doesn't require tedious copy and paste operations?

I wanted to gather up all the posts about the first 6 months of my self-hosting journey, to neatly organize them on my website (either in multiple blog posts or pages) so that they could be more easily searchable. It's not really ideal to go on an infinite scroll quest in reverse chronological order to see the evolution of my self-hosting journey.

Like, I'm curious to see what I was up to in January but going back in time loading old posts takes forever. And I cannot really search for keywords.

I'd like to keep things organized and easily searchable. And implement a POSSE system going forward... publishing on my site first and then syndicating elsewhere.

It's my summer of POSSE inspired by @molly0xfffMolly White 🤗
https://www.citationneeded.news/posse/

If you have any ideas about how I can easily export all my #GtS posts, I'm all ears.

If not, I suppose I will start copying and pasting everything and do monthly installments of my self-hosting journey (aka "month 1" etc.). After all I have 1125 posts (sigh).

Anyways, I hope this finds you well and that you're keeping cool in this scorching heat (especially fellow Europeans).

have a lovely morning/afternoon/evening wherever you are ❤️​

#MySoCalledSudoLife

0

Ω🪬Ω
Latest release of , the customizable timeline algorithm / filtering system for your Mastodon feed, lets you blur / hide images marked as sensitive / , which solves the "unwanted dick pics in your feed" issue that can come up when users of one of the more "risque" fediverse servers manage to make one of their favourite hashtags trend.

* Link: michelcrypt4d4mus.github.io/fe
* Code: github.com/michelcrypt4d4mus/f
* Video of FediAlgo in action: universeodon.com/@cryptadamist
* Release notes: github.com/michelcrypt4d4mus/f

screenshot of fedialgo showing an image post from the mastobate.social server has been blurred out
0

Ok, I think I'm going to have to admit finally that @ryuslash@goto.ryuslash.orgTom is really my main account.

I've been using this account mainly to follow hashtags, but pretty much all of my posting has been happening on my other account.

When I first started I was worried about what it would mean to run my own server, but has been very good and hasn't been using up a lot of resources on my very small VPS.

I'll still check this account regularly, and I'll reply if you talk to me here.

0

🏕️ my adventures in #selfhosting - day 182 (new software edition!) ☁️​

Good morning Fedi friends!

This #GoToSocial account is officially back to posting about... self-hosting from the POV of a newbie / non-dev.

This morning I hit a new little milestone: I FINALLY installed #NextCloud on my VPS (thank you #YunoHost).

I'm getting ready to share short clips of my Fedi promo video (that anybody could use / upload on their own accounts - esp. Big Tech ones, if they're so inclined) and I needed a solution to let people download files. NextCloud is perfect for the task - and something I had looked forward to installing for a looooong time.

I'll share more details soon, but so far I'm excited to finally use it.

Wishing everyone a great day! 🌞​

#FOSS #MySoCalledSudoLife

0

🏕️ my adventures in #selfhosting - day 177 (VPS stress test edition) 📈

Dear Fedi friends,

You might have noticed I've been a little quiet on here since launching my Fedi promo video. What happened?

Well well well, the unexpected victim of my viral toot / video was... my beloved #GoToSocial account.

Approximately 12 hours after posting about my video - a toot that got 1200+ boosts - for some reason federation broke on this account. I was still posting messages and replying but getting zero interactions.

So yesterday evening, thanks to the amazing help of people on the GoToSocial Matrix help room, I was told to upgrade to the latest version of GoToSocial. And that fixed the problem, yay.

If you don't mind, I'll copy and paste parts of 2 messages I had tried to publish Tue & Wed:

((( message from Tue evening )))

Thank you for all the amazing feedback you shared today re: my Fediverse promo video. I’m really touched.

Extra thanks to everyone who helped spread the word on Big Tech platforms - to reach a wider audience. I don’t have any accounts there anymore (not even on LinkedIn) so I appreciate your help with fediverse advocacy 🙏

And special special thanks to all the superheroes who intentionally left the browser tab open on my video to take advantage of PeerTube’s P2P feature, helping offload bandwidth strain from my little server. You rock! 🥹

((( beginning of message from Wed Jun 11 )))

The past 24 hours have been incredible! Thank you for all the boosts to the post about my Fedi promo video (over a thousand!)

It looks like my self-hosted Ghost blog did well with the massive wave of traffic and didn't experience the "Mastodon hug of Death." THANK YOU Varnish cache for it! Total game changer. I could not recommend it more! (As someone who experienced the Mastodon hug of death TWICE before installing Varnish cache) 😅​

So: my #Ghost blog survived. Ditto for my self-hosted #PeerTube (which is on a separate VPS - installed/managed via #YunoHost). The video so far has almost 5000 views - which is pretty good for PeerTube.

✨​ The magic of the fediverse for you ✨​

((( end of pasted messages )))

Since yesterday, I changed the visibility of the video, making it public. And my VPS is surviving, thanks to PeerTube's P2P and various instances mirroring the video (thank you fellow admins, I owe you big time!)

I'm just so grateful for all your nice words and support.

Later today I'll travel to Amsterdam, as I will be speaking at #PubConf2025 about the Fediverse YAY. I'm super honored for this opportunity and I look forward to reconnecting with many other Fediverse advocates who have become friends.

Exciting times 🥹

Wishing you all a lovely day! ✨🚀

#MySoCalledSudoLife #TheFutureIsFederated

0

Dear Fedi friends,

By now you might have seen the post announcing the release of my promotional video for the Fediverse. But in case you have boosts turned off, here we go: news.elenarossini.com/fedivers

I posted about it this morning from my account because I have a 5000 character limit there. And I had so many people to thank for their help. It really takes a village.

Thank you for all the wonderful feedback so far ❤️

0
0
0

👋🏻 I thought I'd post this #introduction

I’m a #productivity enthusiast. I’m interested in #tech

I started this #GoToSocial instance as a mini-project; especially as my coding skills are very, very, limited, so a little bit of education for me. So far, so good.

In my spare time (not that there is much of it) I’m a #CubScout Leader #ScoutingUk

I have an amazing wife and between us we have 5 children - well, I say 'children' but they're all grown up now!

I follow #Formula1 My favourite team is #McLarenF1
I also support #AFCBournemouth 🍒

I find #lego to be extremely cathartic and enjoy building when I can.
I #read a lot; usually crime, mystery, thriller
I have also started listening to #audiobooks

I have a #pixelfed account too, where I post a lot of my photos - check it out here: @doonytime

As part of my foray into #selfhosting I also started a Friendica instance... but I'm not sure what I'm going to do with that.

#Nextcloud is where I now hold my documents etc - again self-hosted via a VPS.

It would be great if you would boost and follow so that I can start to build this instance out... 😉

#LoveSelfHostLife ❤️

#ScoutingUK #movies #F1 #reading #Fediverse

0

Hi all, I've just setup my own #GoToSocial instance, so it's time for an updated #introduction

I'm very much into #yoga and #meditation and everything related to that. I'm trying to learn #Sanskrit because its a beautiful language and also in order to be able to read text like the #BhagavadGita #Upanishads #YogaSutras which greatly inspire me.

I'm from the #Netherlands and work in #science in the field of outdoor #AirQuality I may occasionally share something about that, but this is not a work account (and any opinions are my own).

I love #photography , mostly related to #nature #weather #clouds #trees
I love the #forest, I'm grateful to live at the edge of the beautiful #Veluwe nature area.

I love growing food in my #garden using #organic #permaculture and #RegenerativeAgriculture inspired methods, I'm dreaming of tending my own #FoodForest some day.

Unfortunately I'm operating at half power thanks to #LongCovid since Feb. '22, so most of my hobbies are in "maintenance mode".

I'll post in English, my Dutch account is @kedara_nlRuben ~ Kedara.nl
I also have a personal website @ https://kedara.eu where I #blog, tend a #DigitalGarden / #wiki and try to contribute to the #Indieweb #smallweb communities.

I've done my fair share of instance hopping and had hoped to solve that by starting my own Akkoma instance, but found GoToSocial more suitable to my needs in the end. I hope to stay here now indefinitely.

Let me know if you have similar interests and I'll be happy to chat!

0
0

Hallo allemaal, ik heb net mijn eigen #GoToSocial server opgezet, dus het is tijd voor een bijgewerkte #introductie

Ik doe aan #yoga en #meditatie en alles wat daarmee te maken heeft. Ik probeer #Sanskriet te leren, omdat het een prachtige taal is en ook om teksten zoals de #BhagavadGita #Upanishads #YogaSutras te kunnen lezen, die mij erg inspireren.

Ik kom uit #Nederland en werk in de #wetenschap op het gebied van (buiten) #luchtkwaliteit. Het kan zijn dat ik daar af en toe iets over deel, maar dit is geen werkaccount (en toots zijn op persoonlijke titel).

Ik hou van #fotografie, meestal gerelateerd aan #natuur #weer #wolken #bomen
En speciaal ook van het #bos, ik ben dankbaar dat ik aan de rand van het prachtige natuurgebied de #Veluwe woon.

Verder hou ik van het verbouwen van voedsel in mijn #tuin met behulp van op #biologisch #permacultuur en #RegeneratieveLandbouw geïnspireerde methoden, ik droom ervan om ooit mijn eigen #voedselbos te onderhouden.

Helaas werk ik op halve kracht dankzij #LongCovid sinds februari '22, dus de meeste van mijn hobby's staan in de "onderhoudsmodus".

Ik post in het Nederlands, mijn Engelse account is @kedara_euRuben ~ Kedara.eu
Ik heb ook een persoonlijke website @ https://kedara.nl waar ik #blog, een #DigitaleTuin / #wiki onderhoud en probeer bij te dragen aan de #Indieweb #smallweb kringen.

Ik ben redelijk vaak van server gewisseld en had gehoopt dat op te lossen door mijn eigen Akkoma instance te starten, maar vond GoToSocial uiteindelijk meer geschikt. Ik hoop hier nu voor onbepaalde tijd te blijven.

Laat het me weten als je dezelfde interesses hebt, dan houden we contact!

0

Hi all, I've just setup my own #GoToSocial instance, so it's time for an updated #introduction

I'm very much into #yoga and #meditation and everything related to that. I'm trying to learn #Sanskrit because its a beautiful language and also in order to be able to read text like the #BhagavadGita #Upanishads #YogaSutras which greatly inspire me.

I'm from the #Netherlands and work in #science in the field of outdoor #AirQuality I may occasionally share something about that, but this is not a work account (and any opinions are my own).

I love #photography , mostly related to #nature #weather #clouds #trees
I love the #forest, I'm grateful to live at the edge of the beautiful #Veluwe nature area.

I love growing food in my #garden using #organic #permaculture and #RegenerativeAgriculture inspired methods, I'm dreaming of tending my own #FoodForest some day.

Unfortunately I'm operating at half power thanks to #LongCovid since Feb. '22, so most of my hobbies are in "maintenance mode".

I'll post in English, my Dutch account is @kedara_nlRuben ~ Kedara.nl
I also have a personal website @ https://kedara.eu where I #blog, tend a #DigitalGarden / #wiki and try to contribute to the #Indieweb #smallweb communities.

I've done my fair share of instance hopping and had hoped to solve that by starting my own Akkoma instance, but found GoToSocial more suitable to my needs in the end. I hope to stay here now indefinitely.

Let me know if you have similar interests and I'll be happy to chat!

0

GoToSocial is a lightweight safety-focused Fediverse server type popular among people who run their own servers.

It's now much easier to run your own GoToSocial server as it's available through managed hosting, where the hosting company does all the techy stuff for you:

➡️ fedihost.co/hosting/gotosocial

You can also transfer your Mastodon account to GoToSocial:

➡️ video.fedihost.co/w/i2AGvZc69g

(NOTE: Despite the similar name, FediHost is nothing to do with FediTips! 🙂 )

0
0
0
0

The cat is out of the bag, and we've officially talked about it. This year, health allow it, I'll be working on Anti-harassment and anti-absue related research for GoToSocial, the goal of this is to inform our development!

We mentioned it briefly in our recent newsletter.
https://opencollective.com/gotosocial/updates/gotosocial-newsletter-jan-apr-2023

As mentioned there, I'm hoping to organize a workgroup, so that anyone who's interested in this, and able to contribute time, can drop by to help. If you want to help out or have resources that might be interesting please don't hesistate to contact me here.

First step is to review existing work on the subject, to see if we need to adjust any of our other reserach questions.

#GoToSocial #AntiHarassment

0
0
0

I'm still considering setting up a single user instance. I'm trying to go with a low-power Raspberry Pi 2B, which is up to date with Debian.

One option is snac, I know nothing about C - it seems like a good option for that hardware, but am I in for a load of issues going in blind?

My other option is gotosocial, but I would need to do more work to get a database set up and deal with media storage.

0

After reviewing FEP-5624: Per-object reply control policies and GoToSocial's interaction policy spec, I find myself leaning toward the latter for long-term considerations, though both have merit.

FEP-5624 is admirably focused and simpler to implement, which I appreciate. However, 's approach seems to offer some architectural advantages:

  1. The three-tier permission model (allow/require approval/deny) feels more flexible than binary allow/deny
  2. Separating approval objects from interactions appears more secure against forgery
  3. The explicit handling of edge cases (mentioned users, post authors) provides clearer semantics
  4. The extensible framework allows for handling diverse interaction types, not just replies

I wonder if creating an that extracts GoToSocial's interaction policy design into a standalone standard might be worthwhile. It could potentially serve as a more comprehensive foundation for access control in .

This is merely my initial impression though. I'd be curious to hear other developers' perspectives on these approaches.

4
0

New blog post!

This time I talk about the two recent migrations I did with my data:

I migrated my main VPS from a US based VPS provider to @hetzner because I want to have my stuff in Europe.

The second one was the migration of this exact account from which I send this toot, I moved it from Fosstodon to my own GoToSocial instance which I am self-hosting on that Hetzner server.

I hope you will find it useful!

https://stfn.pl/blog/69-migrating-servers-migrating-instances/

#gotosocial #fosstodon #fediadmin #hetzner

0
0

My relay instance for the evolved in a great way - more than 120 instances are already connected to boost your posts across the Fediverse.

If you're running / , , or any other software on the protocol that supports relay instances - feel free to join the relay! Hopefully also supports relay services soon! Of course is supported (for IPV6 only instances).

fedi-relay.gyptazy.com

Screenshot of the overview page of fedi-relay.gyptazy.com showing more than 120 connected instances for a federated network within the Fediverse.
0
0
0
0

Если видите, что я на вас не подписался - без паники.

Я тут подписался на небольшую группу человек и тестирую свой личный инстанс. В теории может получиться так, что я найду тут какие-то недостатки и либо создам инстанс на другом поддомене или поеду на какой-то другой публичный.

Но если всё пройдёт удачно - я сделаю "миграцию" сюда, вас сюда автоматически подпишет (если вы были подписаны на @skobkinAlexey Skobkin), да и свои подписки оттуда я тоже перевезу.

#warning #announcement #log #GoToSocial #test

0