@ivory @joe @gotosocial
Thanks for enabling #GtS support, I can confirm it works.
GtS also handles notifications more according to the standard than #Mastodon. Has this been taken into consideration as well?
@ivory @joe @gotosocial
Thanks for enabling #GtS support, I can confirm it works.
GtS also handles notifications more according to the standard than #Mastodon. Has this been taken into consideration as well?
is:article
lang:
, domain:
, before:
, and after:
, and some oddballs like is:bot
(would require extra join) and sort:
(would break ID-based paging)tsvector
column that concatenates (with record separators? as an array?) the contents of filterableFields
for a status, updates it every time the status or its attachments are edited, and GIN-indexes that columnILIKE
that vanilla GTS usesedit: fixed a backwards flag in has:media
and related operators
we now have some GoToSocial docs about importing your archived posts in general: https://docs.gotosocial.org/en/latest/user_guide/importing_posts/
most of the specifics are in the slurp
docs, but if you write your own importer and think it might be of general interest to GTS users, please let us know.
Hallo zusammen, ich habe eine kleine Zusammenfassung der GoToSocial Installation unter Docker bereitgestellt. Ihr findet Die zusammenfassung hier: https://info.jyrgi.de/services/gotosocial/index.html
i've documented how to use slurp
to import a Mastodon archive into GoToSocial 0.18 with status backdating: https://github.com/VyrCossont/slurp?tab=readme-ov-file#importing-a-mastodon-archive
one wrinkle i've hit so far is that Mastodon's media alt text limit is 1500 characters per attachment, but GTS's default was 500 characters before this change. if you have an old instance like mine, check your media-description-max-chars
setting before importing posts from Mastodon.
the status backdating API feature is included in today's GoToSocial 0.18.0rc2!
if you want to remind your users that your instance rules still apply to posts originally authored on other instances before turning it on (or just don't want it), you can switch the feature off in the config file: look for the instance-allow-backdating-statuses
variable.
Feditext + GTS users: updating to GTS 0.18.0-rc2 includes the patch that makes push notifications work for iOS clients like Feditext and is recommended for all GTS users. you don't need to update Feditext if you already have build 130.
ok, updates on importing posts:
slurp
to import and export emojislurp
to import postsslurp
patches that might help and i should tag a stable release after thatdon't let me forget those docs!
Feditext beta users: today's version 1.7.2 build 130 adds support for push notifications from GoToSocial instances.
you will need to be running a development version of GTS 0.18 with this patch applied <https://github.com/superseriousbusiness/gotosocial/pull/3762>, or wait for the *next* release candidate (0.18.0rc1 doesn't have it) or the 0.18.0 release proper.
users of other instance servers don't need to update.
ok, here you go, updated GTS search patches for 0.18.0rc1. notice how they're on my repo? these are completely unofficial. do not bug anyone but me about them.
Mac
now matches VintageMac
as well as MacOS
main
doesn't have it already. personally, i haven't noticed and i run this instance on a tiny VPSscope:classic
or in:library
operator to search querymain
doesn'ti may add more patches to this list in the medium future as i add more functionality to my own instance, for example, date range operators (before:date
, after:date
), post property operators (has:image
,has:poll
, has:cw
, is:sensitive
, visibility:public
), threading operators (to:user@instance.tld
, is:reply
, -is:reply
), sort operators (sort:oldest
, sort:newest
, sort:favs
) and maybe PG full-text indexing if i have a really good day (i really don't wanna figure out SQLite's weird shit! someone else do it!)
randos don't debate me about Fedi search. my clients can't set per-post interaction controls yet so i'll just block you.
@gotosocial users excited about Web Push notifications (my pet feature) should watch these issues for full support in their favorite clients:
@bob_zim : apart from the fact that online age verification can be easily bypassed, I expect online authentication (proving your identity as known by your government) to lead to massive numbers of identity fraud.
Reliable authentication necessitates that the VERIFIER is trustworthy. If not, they can impersonate you to a third party, using the digital proof that you provided.
Suppose you prefer watching sex with elderly women, and google "milf sex".
And suppose google comes up with rollatorbabes dot com. You go there and they demand that you prove you're old enough by sunmitting your electronic ID - and perhaps also a selfie "to prevent fraud". This may happen:
You <-> RollatorBabes <-> Visa
RollatorBabes forwards all auth details, except your home address (RollatorBabes changes that) to Visa - in order for them to obtain a creditcard - showing your name.
To prevent this, the first thing you need to know is WHO the verifier is. Not who they say they are, but reliably verified by a third party who deserves YOUR trust. So you can sue RollatorBabes if they fsck you.
Do you trust THEM, shown below?
See also https://infosec.exchange/@ErikvanStraten/113880125384919871.
@vwbusguy : non-ACME certs suck big time.
However, now the internet has turned into a malicious phishing mess.
People can no longer determine who is responsible for a website, and nobody cares.
Google hosted fake websites (using ACME certs from Let's Encrypt) on their cloud servers called:
• cancel-google[.]com
• adsupport-google[.]com
• helpdesk-google[.]com
See (Dutch) https://infosec.exchange/@ErikvanStraten/113837934294209517.
Google also doesn't give a fsck about HSTS, see https://infosec.exchange/@ErikvanStraten/113856108585517842.
Worse, last year a phishing site with a domain name containing "google" was proxied by Cloudflare - and had a "GOOGLE TRUST SERVICES" DV certificate.
Did I mention that browsers suck and that Big Tech, making Big Money, is knowingly complicit to cybercrime?
And did I mention that certificates were not invented to please admins?
Feditext beta users: today's version 1.7.2 build 126 now supports editing posts on GotoSocial 0.18 (already supported for most other Fedi servers).
since GtS 0.18 is still in development, this release is recommended for advanced GtS users only: you need to explicitly set a version like 0.18.0-dev while building GtS for Feditext to detect and enable 0.18 features.
users of current GtS or other servers don't need to update to today's Feditext release.
Hey GoToSocial users, can someone help?
How does a user access GTS-specific features if there's no web interface? If users are on Mastodon API apps, presumably that hides the GTS-specific features?
EDIT: I am specifically wondering how to access/create interaction settings for individual posts?
EDIT 2: Okay, thank you to all the people helping , now I understand a lot better. It seems the interaction settings apply to all public posts rather than individual ones, and these are set through the web interface.
Feditext beta users: version 1.7.2 build 124 now supports exclusive lists on GotoSocial 0.17 (previously supported only on Mastodon 4.2 and forks such as Hometown, where the feature originated).
since GtS 0.17 is still in development, this release is recommended for advanced GtS users only: you need to explicitly set a GtS version like 0.17.0-dev during build for Feditext to enable 0.17 features. users of current GtS or other servers don't need to update.
coming soon to GotoSocial: Hometown-style exclusive lists (upstreamed to Mastodon in 4.2). followers you've added to one of these lists will have their posts show up only in lists, but not on your home timeline. great for news and high-volume posters that you want to follow but not see all the time.
https://github.com/superseriousbusiness/gotosocial/pull/3280
Feditext beta users: version 1.7.2 build 119 comes with slightly improved support for following hashtags.
- highlights followed tags on posts that would not otherwise be in your home timeline, so that you know why you're seeing the posts
- enables the feature for GotoSocial 0.17: https://github.com/superseriousbusiness/gotosocial/pull/3141