R.L. Dane :Debian: :OpenBSD: 🍵<p><span class="h-card"><a href="https://polymaths.social/@clayton" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>clayton</span></a></span> <span class="h-card"><a href="https://polymaths.social/@amin" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>amin</span></a></span></p><p>XD</p><p>Well, you can do custom CSS for your <a href="https://polymaths.social/tags/gts" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GtS</span></a> profile, I think?</p>
#gts
2 posts2 participants0 posts today
Replied in thread
@electragician On my side the image is properly displayed, it has been downloaded and put in cache on my #gts server
It's a small image (1.64MB JPEG file)
Maybe you can take a look on your configuration file, if it has been modified, but default max-size to download media is 40MB so it should be downloaded
# Size. Max size in bytes of media to download from other instances.
#
# Lowering this limit may cause your instance not to fetch post media.
##
# Examples: [2097152, 10485760, 40MB, 40MiB]
# Default: 40MiB (41943040 bytes)
media-remote-max-size: 40MiB
Replied in thread
@crossgolf_rebel morgen aus den #gts netzwerk
Replied in thread
@jschwart : aan add-ons hebben we niks: die zullen door veel te weinig mensen worden gebruikt waardoor er niets verandert (bovendien bestaat het risico dat mensen nep-add-ons installeren).
Het gaat om een *combinatie* van wijzigingen die de EU zal moeten afdwingen.
Domeinnamen (inclusief het toenemende aantal TLD's) zijn namelijk het *probleem*. Je kunt ze vergelijken met telefoonnummers of woonadressen, potentieel iets- of nietszeggende strings die van een eigenaar *kunnen* zijn (en morgen van een ander). De enige voordelen ervan zijn dat ze uniek zijn en meestal kort.
De meeste internetters begrijpen echter niet hoe je ze moet interpreteren, zoals dat
www-example·com
iets heel anders is dan
www.example·com
(om het nog maar niet te hebben over IDN's zoals in
"https:⧸⧸lîdl·be/login").
Ik zie geen andere oplossing dan voor *mensen* begrijpelijke en traceerbare identificerende informatie opnemen in websitecertificaten, waaronder bijv. (indien beschikbaar) een KvK-nummer (in tegenstelling tot bij 'whois' kun je bij de KvK wel zinvolle identificerende info vinden). Alleen al betrouwbaar weten in welk land de websiteverantwoordelijke gevestigd is, zou al enorm kunnen helpen tegen oplichting.
In https://infosec.exchange/@ErikvanStraten/113990009126611573 zie je een screenshot van
https://play.google-ivi·com
waar Google Trust Services "gewoon" een ceetificaat voor uitgeeft (te zien in https://infosec.exchange/@ErikvanStraten/114061799937444243).
Infosec ExchangeErik van Straten (@ErikvanStraten@infosec.exchange)Attached: 1 image
@dianasusanti@mastodon.social : w.r.t. Indonesian speaking people, the image below that I just made shows another fake site - which will look familiar to Android users.
Note that it has a website certificate submitted by "Google Trust Services" while the site hides behind a Cloudflare IP-address.
It is not surprising that people fall for this, as (for example), to log in to Microsoft you have to go to:
https:⧸⧸login.microsoftonline.com
Instead of, any of, for example:
https:⧸⧸login.microsoft.com
https:⧸⧸login.365.microsoft.com
https:⧸⧸login.office.microsoft.com
Another scamwebsite:
https:⧸⧸lîdl·be/login
Note the î instead of the i.
P.S. I'm using
· instead of . and
⧸ instead of /
to prevent accidental opening.
#Phishing #Spoofing #AitM #Fraud #FakeWebsites #OnlineFraud #DVCerts #NobodyFeelsResponsible #Cybercrime #CyberCriminals #Russia #GoogleIsEvil #BigTechIsEvil #CloudflareIsEvil #MicrosoftIsEvil
Replied in thread
| 
2W/50Wh Oh fein ich hab mein Problem mit fedi.buzz gelöst, erst entmuten dann entfolgen dann klappt es auch scheint nen #GTS bug zu sein, ich werde nicht mehr von mastodon.social voll gespammt.
Dafür hab ich mir die Timeline von norden.social abonniert ;) ist deutlich weniger und ich hab wieder ne Möglichkeit Hashtags local zu Folgen *freu ;)
Anyone using #litestream for an #sqlite DB
I have a 3GB database, and Litestream is replicating it to another server. However, it seems to be running out of control with disk space. On the original server (where the live DB is) is a generations folder under the hidden litestream folder. It is full of WAL files. Currently over 37,000 files consuming 118GB of disk space.
My config includes retention: 24h and retention-check-interval: 1h with a snapshot-interval: 4h. I understood it would delete anything older than 24 hours. Am I doing something wrong? These wal files go back to the day I started using litestream
#GoToSocial #gts @gotosocial@thefedi.forum
I've just migrated my #gts instance to a new machine... hopefully I've copied all data properly 
Anyone using #litestream for an #sqlite DB
I have a 3GB database, and Litestream is replicating it to another server. However, it seems to be running out of control with disk space. On the original server (where the live DB is) is a generations folder under the hidden litestream folder. It is full of WAL files. Currently over 37,000 files consuming 118GB of disk space.
My config includes retention: 24h and retention-check-interval: 1h with a snapshot-interval: 4h. I understood it would delete anything older than 24 hours. Am I doing something wrong? These wal files go back to the day I started using litestream
Replied in thread
Replied in thread
So, few weeks ago I've installed a second instance of #GoToSocial for testing purpose.
The primary reason was to test #slurp but finally I didn't tested it yet, lack of time but also because the #mastodon instance from which I want to test the import does not let me export the history of messages & medias 
But ok, it's not a real problem for now, I'm not in a hurry to migrate the mastodon account.
For now what I'm trying to understand is how a #gts instance is federating and give me access to the #fediverse.
The documentation is not clear about this, or I'm dumb, it's possible too 
The thing is I feel a little bit alone here:
- My local timeline is almost empty even federated with ~7700 instances; in fact, there's only what I post myself so totally useless
- My federated timeline is filled with toot of people I'm following; that's totally useless too
It's like hem, in fact the fediverse let you follow stuff people on your instance are following and interacting with.
Currently to discover new accounts and follow topics on which I'm interested to:
- I'm following people, they often retoot stuff I can be interested about and then, I sometime discover new accounts to follow
- I'm following hashtags on third party instances -thanks to @phanpy for this functionality- but it's boring because I can't interact on toot without manual switch to instance...
I've been recommended by @erick (here: https://gts.erick.sh/@erick/statuses/01JN0ZCHN4M5BPWR0FFXJVQYNN) to create a dummy account and follow relay tags/instances (especially https://relay.fedi.buzz) to fill timeline of my instance.
It took me some time to understand how to do that because #GoToSocial doesn't allow like mastodon to use relays.
But basically it's pretty simple: to follow the hashtag, for example #GoToSocial, just follow @tag-gotosocial
To follow an entire timeline of an instance, for example mastodon.art, just follow @instance-mastodon.art
Then, federated timeline of my #gts instance start to be filled with a lot of stuff; starting to follow hashtags from my own instance now returns interesting content 
There's still some mystery: not all followed hashtags visible in federated timeline are available when I follow them to my instance (sometime yes, sometimes no...) and I still have tests to realize but I'm quite happy for now, it's a big step ahead about my #SelfHosting instance
Ich betreibe jetzt seit Juli 2023 einen
GoToSocial Server
von einem gängigen DSL100-Anschluss und einer gar nicht so mächtigen Hardware aus.
Ich habe darauf nur 2 aktive Accounts. Davon ist einer eigentlich nur für die unkomplizierte und schnelle Übermittlung von den Praxisablauf betreffenden Meldungen an unsere Webseite gedacht. Der zweite ist dieser Account hier 
Der Administrationsaufwand hält sich bei #gts sehr in Grenzen. Einen Moderationsaufwand hab ich logischerweise gar nicht. Ich liebe, dass ich meine Posts mit Markdown gestalten kann. Seit dem letzten Update kann ich wie bei Mastodon Beiträge nachträglich bearbeiten. Und auf der Roadmap für die nächsten Releases steht sogar die noch fehlende 2FA.
Ich kann allen, die gerne mal selbst mit einem Fediverse-Server experimentieren möchten, #GoToSocial nur wärmstens empfehlen. Ich erlebe es als eine ressourcensparsame Möglichkeit, sich selbst und einer Handvoll befreundeter Menschen eine Teilhabe im #Fediverse zu ermöglichen, die sonst vielleicht bei der Auswahl einer geeigneten Instanz bereits aufgeben würden.
Знаете, когда я искал софт для своего сервера чтобы погрузиться в #fediverse я хотел что-то вообще без вебморды, но таких не было и это меня очень расстраивало. В итоге я выбрал #gotosocial и мне дейсвительно нравится как выглядит #web страничка юзверя в #gts.
