microblog.at ist einer von vielen unabhängigen Mastodon-Servern, mit dem du dich im Fediverse beteiligen kannst.
Dies ist die private Mastodon Instanz von Robert Lender

Verwaltet von:

Serverstatistik:

1
aktive Profile

#gts

0 Beiträge0 Beteiligte0 Beiträge heute
Fortgeführter Thread
  1. advanced search operators prototype. status: not quite ready for prime time.
    • has a bunch of goofy operators nobody but me will ever use, such as is:article
    • still missing some classics like lang:, domain:, before:, and after:, and some oddballs like is:bot (would require extra join) and sort: (would break ID-based paging)
    • needs docs, although i know where Past Vyr basically already wrote them: https://github.com/VyrCossont/mastodon/pull/8 😇
  2. indexed full text search prototype. status: heretical.
    • only works on PostgreSQL: SQLite's full-text search is much fussier and requires using a "virtual table" and frankly i can't be bothered, at least tonight
    • direct port of https://github.com/VyrCossont/mastodon/pull/3 and has the same limitations: HTML isn't stripped, and media alt text and poll options aren't indexed
    • fixing that would start by adding a 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 column
    • ignores the whole issue of matching posts to language tags and language tags to PG text search configurations by assuming that everything is English
    • still massively faster than unindexed ILIKE that vanilla GTS uses

edit: fixed a backwards flag in has:media and related operators

GitHubAdvanced search operators · VyrCossont/gotosocial@a87e9d5Fast, fun, ActivityPub server, powered by Go. Contribute to VyrCossont/gotosocial development by creating an account on GitHub.
#GoToSocial#GTS#FullText
Antwortete im Thread

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.

docs.gotosocial.orgInstance - GoToSocial DocumentationNone

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 <github.com/superseriousbusines>, 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.

GitHub[bugfix] Reduce Web Push record size by VyrCossont · Pull Request #3762 · superseriousbusiness/gotosocialVon VyrCossont

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.

  1. improved hashtag search. status: upstreamable, mostly.
    • doesn't require # prefix to search hashtags
    • searches for matches anywhere in a hashtag: Mac now matches VintageMac as well as MacOS
    • includes hashtags when not specifically searching for accounts or statuses, like most Mastodon-compatibles
    • doesn't change existing tag sorting. popularity and/or recency might be more useful
  2. offset paging for searches. status: not upstreamable yet.
    • more compatible: many clients can't do ID paging
    • allows paging hashtag search results: Mastodon API has no concept of IDs for hashtags, so ID paging can't work for those anyway
    • possible performance issues: see comments on why main doesn't have it already. personally, i haven't noticed and i run this instance on a tiny VPS
  3. remove search restrictions. status: heretical.
    • searches any post on your instance (except other accounts' private/direct posts, and accounts that have you blocked)
    • includes public, unlisted, your own private and DM posts, and private and DM posts that are replies to you
    • expanded search is default: revert to standard GTS behavior by adding scope:classic or in:library operator to search query
    • definite performance issues: this means searching more posts! GTS does not use either PG full-text indexes/operators or SQLite full-text virtual tables, and this patch doesn't change that.
    • doesn't include alt text of media attachments, or polls, because main doesn't

i 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.

GitHubSearch for tags even when # prefix is omitted · VyrCossont/gotosocial@bef51e4Search for internal matches, not just prefix matches A full-text search should return tags as well as accounts and statuses.
#GoToSocial#GTS#FullText
Antwortete im Thread

@gotosocial users excited about Web Push notifications (my pet feature) should watch these issues for full support in their favorite clients:

GitHubPush notification type checkboxes incorrect for GotoSocial, possibly others · Issue #1032 · cheeaun/phanpyVon VyrCossont
#GoToSocial#GTS#Phanpy
Antwortete im Thread

@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 infosec.exchange/@ErikvanStrat.

@nazokiyoubinbou @evacide

Antwortete im Thread

@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) infosec.exchange/@ErikvanStrat.

Google also doesn't give a fsck about HSTS, see infosec.exchange/@ErikvanStrat.

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?

#Phishing#DV#GoogleIsEvil

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

GitHub[feature] Implement exclusive lists by VyrCossont · Pull Request #3280 · superseriousbusiness/gotosocialVon VyrCossont
#GotoSocial#GtS#GtSDev