taquiones.net is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
@gumnos no, of course it won't. This is the beauty – and the downside – of open source and self-hosting communities: people eventually start with self-hosting, especially when it’s possible to do so with valid and lightweight tools like #snac. In a way, snac is one of the reasons for the loss of users from the BSD Cafe instance 😆
But, jokes aside, the BSD Cafe is not a server – it’s a community. Going self-hosted with solutions like snac (as @justine did too) means you’re still part of the BSD Cafe, and in fact, it's a success because the spirit of the BSD Cafe is exactly this.
In short, you can bring your own coffee ready, but the table and the welcome are always there. 🙂
CC: @grunfink
Relays in general are already available for a longer time and there’re also many ones available. My relay instance is new - it popped up of an idea when I saw many new #snac instances and someone showed relay links. I wouldn’t have thought that my relay instance would grow that quick, so I’m happy to see this gets appreciated by the community :)
#HowTo install & run #snac on #FreeBSD - run your own #ActivityPub instance in the #Fediverse!
In the last days I often got asked about #snac / #snac2 as an alternative to #Mastodon and I can highly recommend it! I few months ago, I already wrote a HowTo about setting snac up on a FreeBSD instance - might be worth to share again :) if you’re using snac, you might also want to use my relay service at https://fedi-relay.gyptazy.com to make your posts more visible in the Fediworld.
#opensource #fediverse #fediworld #alternatives #community #FreeBSD #RUNBSD #BoxyBSD #activitypub #mastodon #relay #community #federated
https://gyptazy.com/install-snac2-on-freebsd-an-activitypub-instance-for-the-fediverse/
Regarding your first point (saving a thread for later replying or reacting): I use bookmarks for that.
Regarding the page reloading after actions, I'm afraid it's not possible without the use of JavaScript, which is a no/no for this project. The action requires a trip to the server, and a response back with the same (or the most similar) content you were previously shown.
And with regard the mark of "below this line, you've already seen this": it has been on my mind for long time, but due to implementation details, it's trickier than it seems. I will implement it eventually, because it's something that I deeply need 😆
Thanks for taking a chance on #snac.
Publishing a photo of approximately 4MB from my snac instance (at home with 20 Mbit/sec uplink) meant overwhelming everything.
This happened because, for every remote instance, Nginx was requesting the multimedia file from snac. However, due to saturated connections, it took several seconds, leading to thread exhaustion in snac.
I resolved this issue by caching the multimedia files myself using Nginx, which significantly improved performance.
This matter will be covered in a subsequent (simple) blog post.
Learning en orienting myself into the code of snac
Snac is fascinating
https://codeberg.org/grunfink/snac2
🖋️ #bash #sh #zsh #ksh #csh #freeBSD #FediVerse #OpenRelay #openBSD #netBSD #ZFS #Filesystems #Linux #POSIX #Programming #snac
Using #snac makes making bots a breeze. It’s a great tool!
I hate that it uses emoji for ui (what is a lock? What is a hand shake?), but outside of that it makes me appreciate fediverse more.
GoToSocial, if I'm not wrong, doesn't support it (yet - it's in the roadmap): https://codeberg.org/superseriousbusiness/gotosocial/src/branch/main/ROADMAP.md
Thanks to the recent addition of relay support, it is now possible to follow hashtags and benefit from message exchange between all instances connected to the same relay.
This will slightly increase the traffic on our instance, but it will also boost its visibility.
#BSDCafe #BSDCafeAnnouncements #BSDCafeServices #BSDCafeUpdates #snac #snac2
The BSD Cafe's snac instance is now registered to the @gyptazy relay.
Thanks to the recent addition of relay support, it is now possible to follow hashtags and benefit from message exchange between all instances connected to the same relay.
This will slightly increase the traffic on our instance, but it will also boost its visibility.
#BSDCafe #BSDCafeAnnouncements #BSDCafeServices #BSDCafeUpdates #snac #snac2
Anyway, and because some users asked for it, you can share your own metrics to others. It's disabled by default; you can find a toggle in your user settings.
I hope you enjoy snac.
This issue that caused snacs notifications to crash has now been speedily resolved thanks to the amazing efforts of the developer @grunfink@comam.es
Update has been pushed to the #snac git repo.
Can someone like this toot please. I think I found a bug in #snac ? I saw in a thread of mine a comment that was abusive so I clicked delete. Now when I click on the notifications tab it gives me a 502 bad gateway. Everything else seems to work though. Very weird ! 🤔
anyone have a #snac instance and want to give me an account on for some good old fashion fediverse compatibility testing? excited to see how it now handles gancio and mobilizon events
https://comam.es/snac/grunfink/p/1737710445.095224
I'm glad you like it, thanks!
Entirely fair, but you've fallen in with the beige.party crew—likely run by someone geeky enough to do it for the love/fun, and share the experience with non-techno-geek users such as yourself.
(and agreed as well…I *am* a technogeek with my own domain/website/mailserver, and, while I have aspirations to eventually set up my own #snac or #gotosocial instance on my VPS, I haven't yet gone through the hassle. So I'm quite content to let @stefano play the benevolent overlord of this little corner of the fediverse where he lets us play for free)
Just a few days ago, I lunched my new relay service for the #Fediverse and I'm really happy to see that there're already many ones connected to - more than 50 instances in just a few days!
But what makes me even really happy is to see, that my service [2] also gets linked in the release notes of #snac [1] / #snac2 - and I can recommend the usage of relay services (it doesn't matter which one!) to everyone. It provides more content from connected instances to you, but also brings your posts - from your local instance - up to other ones within the federated network where it can get much easier distributed around other instances.
#snac is the perfect way to host an own fediverse instance. Using the #ActivityPub protocol allows you to connect to all other instances. With the integrated #Mastodon API, you can also use most of your usual clients or web clients. Snac is light, fast, does not require any database and follows the KISS way - which the most of us BSD people are living. With relay services, it's the perfect match for singe-user instances and @grunfink is always open for ideas and to help! It does not always need to be #Mastodon, #GoToSocial etc!
And if you're using any other software, you may still benefit by using relay services. And if you're still looking for a guide, howto setup snac2 on #FreeBSD, my howto [3] might help you out.
[1]: https://codeberg.org/grunfink/snac2
[2]: https://fedi-relay.gyptazy.com
[3]: https://gyptazy.com/install-snac2-on-freebsd-an-activitypub-instance-for-the-fediverse/
#community #opensource #development #coding #c #clang #homelab #hosting #BSD #RUNBSD #Howto
I've previously used #snacizens, but #snacsters also sounds great 🙂
#FediMeteo #FediMeteoStatus #FediMeteoAnnouncements #snac #snac2
#BSDCafe #BSDCafeAnnouncements #BSDCafeUpdates #BSDCafeServices #snac
The BSD Cafe snac instance has been upgraded to 2.69
#BSDCafe #BSDCafeAnnouncements #BSDCafeUpdates #BSDCafeServices #snac
Added support for subscribing to LitePub (Pleroma-style) Fediverse Relays like e.g. https://fedi-relay.gyptazy.com to improve federation. See snac(8)
(the Administrator Manual) for more information on how to use this feature.
Added support for following hashtags. This is only useful if your instance is subscribed to relays (see above).
Added support for a Mastodon-like /authorize_interaction
webpoint entry, that allows following, liking and boosting from another account's Mastodon public web interface. To be able to use it, you must reconfigure your https proxy to redirect /authorize_interaction
to snac (see snac(8)
).
Some fixes to accept Event
objects properly (like those coming from implementations like https://gancio.org/ or https://mobilizon.fr).
Added some caching for local Actor
objects.
Hashtags that are not explicitly linked in a post's content are shown below it.
Fixed broken NetBSD build (missing dependency in Makefile.NetBSD).
The user profile can now include longitude and latitude data for your current location.
Mastodon API: implemented limit= on notification fetches (contributed by nowster), implemented faster min_id handling (contributed by nowster), obey the quiet public visibility set for posts, other timeline improvements (contributed by nowster).
Reduced RSA key size for new users from 4096 to 2048. This will be friendlier to smaller machines, and everybody else out there is using 2048.
If the SNAC_BASEDIR
environment variable is defined and set to the base directory of your installation, you don't have to include the base directory in the command line.
Fixed a bug in the generation of the top page (contributed by an-im-dugud).
Added support for Markdown headers and underlining (contributed by an-im-dugud).
If you find #snac useful, please consider contributing via LiberaPay: https://liberapay.com/grunfink/
This release has been inspired by the song Nine Hundred Miles by #BarbaraDane.
On the other hand, the FediBuzz concept has the benefit that you only receive those posts you are interested in and not a firehose of data (most of it probably of no interest for you), which is a huge benefit if you have bandwidth restrictions.
OMG Following FediBuzz hashtags from your relay user account on a #snac instance actually works ! I think I'm going to be using FediBuzz a lot more now to follow hashtags and get more content.
Thank you for bringing this to my attention @nowster@fedi.nowster.me.uk
btw, if you're interested, how I post to fedi for my linkblog:
it all starts in my "bookmark" ruby script. It adds the bookmark to yaml file, which is then used to build the blog. This has not changed since last version.
I've added creation of a .txt file which will be the body of the toot. Then, my "deploy" script rsyncs the file to the server and removes local copy.
On the server, #snac is running in a FreeBSD jail. The folder where I upload the .txt file is mounted via nullfs.
Every minute a shell scipts iterates over the mounted folder, pipes contents into "snac note" and deletes all .txt file
I'm using Snac from #FreeBSD ports.
@mms that's one of the (many) reasons why I decided to use #snac for #FediMeteo - full usability
My new relay instance in the #Fediverse launched successfully :)
Just added a blog post: As I could see, not everyone was aware of the benefits of using such a service which is especially very important for smaller instances or even single-user instances. So, nothing new in the post - just a recap to summarize the things for newcomers :) #activitypub #mastodon #snac #pleroma #social #socialmedia #community
https://gyptazy.com/hosting-a-new-activitypub-relay-for-the-fediverse-including-mastodon-and-snac/
I've followed the #FreeBSD hashtag for now and will see what happens. One thing that does come to mind is that you now have a user called relay
that doesn't actually seem to do much other than follow the actors ????
Do I now have to follow my relay or is this something that the snac server takes care of ???
Also is it a good idea or can the relay
user follow multiple relay actors ??
wow, that was quick - more than 30 instances already connected to my relay in just such a short time :) Let's be federated and help even smaller #instances to distribute their content & posts!
You can find more information at:
https://fedi-relay.gyptazy.com
The instance is reachable on IPv4 and IPv6.
#fediverse #mastodon #snac #snac2 #activitypub #relay #activtypubrelay #Pleroma #BSD #RUNBSD #devops #opensource #ipv6 #gotosocial #community #akkoma #pixelfed #selfhosting #homelab
Hmmm was going to subscribe to https://fedi-
relay.gyptazy.com/ on my #snac server but there is one rule that even though I hardly post about might get my instance removed. It says "No political related content" but occasionally ( very rare ) I will boost a toot that I agree with to do with politics or make a random moan about our government but that too is rare. Mostly it's tech related and life. I totally agree with @gyptazy@gyptazy.com rules, it's just that politics that might catch me out ? So I guess I better go look for other relays like Intahnet.
Listing of other relay servers:
@eXOfasia @vamonosjuntas @lafurgo
Com a decisió política i per tal de fomentar la diversitat de software, fem servir snac
Ai que em desmaio! La eXO, quina ilu! 🎉
Sembla molt ecolobits aquest enginy federat. Ja sabeu que m’encanta que estigui a Codeberg 💚 I m’ha fet gràcia que snac sigui acrònim de Social Networks Are Crap. Molt FediPunk, jajaja.
Merci per muntar node, i visca la diversitat i el minimalisme fediversal!
greeting.html
page. Started thinking I'd messed up my nginx reverse proxy config somehow but couldn't see anything wrong. So decided to bypass the reverse proxy and use curl
on my snac instance to prove that it was snac that was the issue. Anyway reported and a fix has been found by another snac user @anzu@livellosegreto.it which I tested and @grunfink@comam.es pushed an update.snac2 - frontendin' alien toots
(Using snac2 and links2 to display mastodon toots from foreign instances.)
https://automa.triapul.cz/snac2-vol1/
Super special thanks to @grunfink , the author of snac, for returning sanity into web software.
CC: @mms@bsd.cafe
Thanks for providing this service and also this information. At this point, we can only say - thank you very much for your time, efforts and money you put into this service @stefano. At this point I also want to bring up the great work of @grunfink for his incredible work in the #snac / #snac2 project. Snac became the perfect solution for single user instances but also project related instances in the fediverse. Kudos, to both of you and thank you both very much! You both are doing a great job!
Some technical details for those interested:
The entire FediMeteo setup runs on a FreeBSD VM costing around 4 euros per month. It supports almost all major EU countries (plus the UK), with just a few left to complete. Currently, there are 25 separate jails, each running its own instance of snac, totaling 25 instances. The VM load typically stays around 10%, which increases to 30% when updates are published for countries with larger numbers of cities (currently Germany and Italy). The only time the load spikes is when new countries are announced; during that time, all remote instances connect to all cities to download their details.
As for RAM usage, excluding the ZFS cache, it's currently a total of 213 MB. Yes, MB.
I submitted a Pull Request to update MacPorts' snac to 2.68 here:
https://github.com/macports/macports-ports/pull/27332
GitHub Continuous Integration checks are running (two out of three completed successfully, which is a good sign, here's hoping the last one has no issues as well).
As usual, it's up to someone else with commit access to merge it.
#snac #MacPorts #OpenSource #ActivityPub #Mastodon #NoDatabaseNeeded
#NoJavaScript #NoCookiesEither #NotMuchBullShit #snacAnnounces
Ooh, I do like that #snac gives me a "delete" button for everyone *else's* toots! It hardly seems fair, but given I have impeccable taste it's probably correct to make me The Global Decider. Nice job 👍
Is #snac2 a suitable fedi server for a single-person, daily-driver instance, accessed via mastodon apps, interacting with the wider fediverse?
I /think/ I've mostly seen it deployed as a more write-centric service (for info bots/etc) ... but I could be mistaken.#snac #Fediverse #hosting #selfhosting
Fixed regression in link verification code (contributed by nowster).
Added ipv6 support for the https frontend connection (contributed by hb9hnt).
New "Like by URL" operation (contributed by dheadshot).
Added support for a Mastodon-like /share
link sharing URL, like the one provided by sites like https://mastodonshare.com/ and such. To be able to use it, you must reconfigure your https proxy to redirect /share
to snac (see snac(8)
).
New linux landlock (sandboxing) support for enhanced security (contributed by shtrophic). It's still a bit experimental, so you have to enable it explicitly by recompiling with the WITH_LINUX_SANDBOX directive (e.g. make CFLAGS=-DWITH_LINUX_SANDBOX
).
Some search fixes regarding repeated matches.
The export_csv
cmdline operation now exports the CSV files inside a user's export/
subdirectory instead of the current directory.
All CSV files to be imported must now be stored inside a user's import/
subdirectory instead of the current directory.
Mastodon API: more timeline paging tunings (contributed by nowster), post language selected in apps is properly set.
The command-line operation note
new reads the LANG
environment variable to set the post's language.
A new command-line operation, note_unlisted
, allows posting "unlisted" or "quiet public" posts.
The maximum number of entries in users' RSS feeds and in outboxes can now be set via the max_public_entries
variable in the server.json
file.
Fixed broken support for Audio
objects.
Made xmpp and mailto URLs clickable.
If you find #snac useful, please consider contributing via LiberaPay: https://liberapay.com/grunfink/
This release has been inspired by the painting Judith Slaying Holofernes by #ArtemisiaGentileschi.
En el caso de Mastodon al parecer hay una operación llamada "share" que hace lo mismo. En #snac lo están probando ahora y, o bien la página ya tiene incluido el mecanismo de compartir como pasa con "El salto", o bien te haces con una extensión o un bookmarlet. La extensión va como va, más bien regulinchi y el bookmarlet no termino de pillarlo.
La página del salto, correspondiente a una de sus noticias, es la siguiente:
Announcing FediMeteo – Weather in the Fediverse!
UPDATE: I have created an account for updates and other information on FediMeteo - follow the account @admin to stay updated!
UPDATE: Ireland, Poland, Portugal and Switzerland have just been added
Weather has always influenced our lives: from agriculture to outdoor activities, to extreme events that, thanks to modern technology, can now be predicted with greater reliability. Personally, weather plays a significant role in my daily decisions, which is why I decided to create a service tailored for the Fediverse.
FediMeteo uses Open-Meteo data to publish updates every 6 hours, including current weather conditions, forecasts for the next 12 hours, and predictions for the upcoming days. Each country is served by its own dedicated instance (e.g., it.fedimeteo.com for Italy), managed through snac to ensure simplicity and efficiency in publishing.
You can follow FediMeteo directly in the Fediverse (on Mastodon and compatible platforms), via RSS, or by visiting the dedicated page for your city (e.g., fr.fedimeteo.com/paris).
Currently supported countries include:
Austria, Germany, France, Ireland, Italy, Netherlands, Poland, Portugal, Spain, Switzerland and the United Kingdom, – with many more regions coming soon!
FediMeteo is hosted on a FreeBSD-based VPS, with each country isolated in its own jail to ensure security and scalability.
Visit the main site to explore the national instances and start following your local weather updates today:
https://fedimeteo.com
Happy weather monitoring to all! 🌦️
FediMeteo is dedicated to my grandfather, who every evening would give me the weather forecast based on TV, radio, and his personal experience. He would convince me that the weather would be bad, so he had an excuse to accompany me to school instead of me going alone.
#FediMeteo #Announcements #FreeBSD #FediMeteo #WeatherForecasts #Weather #Meteo #snac #Fediverse #Mastodon
Dear friends of the BSD Cafe,
As 2024 comes to an end, it’s time to reflect on what we’ve built together during the first full year of life for BSD Cafe. Launched on 20 July 2023, this project has grown far beyond what I could have imagined. While I haven’t tracked full uptime data, I can confidently say that the downtime was less than 30 minutes overall - even though the main VM hosting our services moved multiple times (including a switch from a Proxmox hypervisor to bhyve on FreeBSD, for the sake of alignment with our mission). In a world filled with over-engineered HA systems, we’ve outperformed many “big-name” cloud providers. Not bad for a community project, right?
For me, this has been an incredible journey. The users here are not just participants - they’re collaborators, and their positivity has been inspiring. The content shared and created at BSD Cafe has been valuable not only to the BSD community but beyond. What truly sets BSD Cafe apart is the openness for dialogue and exchange. Whether it’s social media posts, Matrix discussions, repositories in our brew, or RSS feeds, people seem to genuinely appreciate what we create and the conversations we foster.
BSD Cafe is a journey - one that grows, evolves, and continues. Our goal isn’t endless growth (we’re a community, not a business) but rather to maintain a welcoming, inclusive space where everyone feels a sense of positivity and belonging. For me, opening any service with “bsd.cafe” in the domain brings joy and pride. That’s the spirit I’ve tried to convey, and I hope it resonates with all of you, whether you’re active BSD Cafe users or friends of the community.
Promoting self-hosting and #OwnYourData has, as a side effect, inspired some users to “go solo” with their own setups. But even then, they remain part of BSD Cafe - in spirit, in purpose, and in connection.
Here’s a look at what we’ve achieved together this year:
- mastodon.bsd.cafe: 370 total users
Active in the past month: 207
Active in the past six months: 286
- snac.bsd.cafe: 14 total users
Active in the past month: 7
- blendit.bsd.cafe: 61 registered users
- matrix.bsd.cafe: 23 users
- brew.bsd.cafe: 29 users - 80 repositories
- freshrss.bsd.cafe: 25 users
- miniflux.bsd.cafe: 11 users
- press.bsd.cafe: 9 users
- myip.bsd.cafe: Constantly used by various users
- wiki.bsd.cafe: Could use a bit more love and content, but it fulfills its role as a functional homepage.
- tube.bsd.cafe: Still in testing - Peertube 7.0 update is on the way.
For detailed stats from our reverse proxy and general router (excluding media services, which generate most traffic but are handled via caching reverse proxies), you can check here - updated hourly: https://netstats.bsd.cafe
The journey of BSD Cafe continues, and I look forward to seeing where 2025 will take us. Together, we’ve built something special - something driven by passion, shared purpose, and a little bit of the BSD magic that makes all of this possible.
Here’s to a new year full of joy, serenity, and connection. Thank you for being part of this adventure.
Wishing you all a fantastic 2025 - and THANK YOU!
Stefano
#BSDCafe #BSDCafeServices #BSDCafeAnnouncements #BSDCafeUpdates #Fediverse #HappyNewYear #Mastodon #Snac #snac2 #lemmy #matrix #dokuwiki #forgejo #freshrss #miniflux #wallabag #peertube #FreeBSD #OpenBSD #NetBSD #RunBSD #BSD
Exactly one year ago, I launched the snac instance of BSD Cafe: https://snac.bsd.cafe
Some users gave it a try and decided to self-host. Others have kept it as a secondary account, while some use it regularly.
Happy anniversary, snac.bsd.cafe - and thanks to @grunfink for the ongoing development and improvement, always staying true to the principles of simplicity and integrity.
#BSDCafeServices #BSDCafe #snac #snac2 #Fediverse #SocialNetworks
Some users gave it a try and decided to self-host. Others have kept it as a secondary account, while some use it regularly.
Happy anniversary, snac.bsd.cafe - and thanks to @grunfink@comam.es for the ongoing development and improvement, always staying true to the principles of simplicity and integrity.
#BSDCafeServices #BSDCafe #snac #snac2 #Fediverse #SocialNetworks
El que se puedan ver ambas estando registrado en un único servidor o instancia es parte de la "magia" de la federación. Cuando necesito ver tu cuenta mi servidor pide datos al tuyo pero filtrándolos. Yo no veo cuántos sigues o a cuantos has seguido, ni tampoco tus publicaciones. Para eso, y es por diseño de #snac, el servidor activitypub que uso, filtra lo que pueda enviarle el tuyo respecto a tu cuenta y tengo que ir a tu servidor para averiguarlo.
Otra cosa, que es lo que hace el mendrugo este, es registrar una cuenta a tu nombre en su servidor puente. Si lo hiciese yo en el mío aparecería como @sunbeam_rider@taquiones.net, que tampoco es tu identificador porque el dominio cambia pero sirve para lo que quiere, sea lo que sea eso, que servicio público no creo.
CC: @pablo@mastodon.cl @fanta@mastodon.green @CorioPsicologia@mastodon.social
Y quitando ese detalle concuerdo con Fanta en que es muy buena explicación.
https://github.com/macports/macports-ports/pull/27188
Two of three GitHub Actions Continuous Integration checks passed, which is a good sign; hopefully the others will pass without issues.
As usual, it's up to others with commit access to merge it!
Thanks again for your and others' continued improvements to snac! Specifically I noticed shout outs to nowster and Shamar in the RELEASE_NOTES.md and I seem to recall watching the discourse about the PID locking suggested and discussed rather collaboratively too!
(My apologies for the delay. The Makefile was slightly modified, which in turn broke the $files/Makefile.patch applied by MacPorts so I needed to rework that which took me a bit longer than usual given other work obligations I have had today.
Though not a concern for upstream, for MacPorts users I also noticed the following warning when running % port test:
"Warning: violation by /opt/local/man
Warning: snac violates the layout of the ports-filesystems!
Warning: Please fix or indicate this misbehavior (if it is intended), it will be an error in future releases!"
Though, it appears as if the man pages are where I think they should be for MacPorts? I have never seen that Warning before, so my guess is something about MacPorts intended prescriptive behavior has been changed but I am not exactly certain what the expected behavior is supposed to be now? I will look into it further, but hopefully it isn't a concern for users at the moment; just thought I would mention it for the sake of being thorough!
However, it's entirely possible I messed something up too; so if others with greater wisdom than I see that Warning and know what to do to correct it, or if they encounter any other issues with MacPorts' snac, others are more than welcome to submit Pull Requests with improvements! Or feel free to open up an issue on MacPorts Trac instance at https://trac.macports.org and I'll look into it.)
#snac #MacPorts #OpenSource #ActivityPub #Mastodon #NoDatabaseNeeded
#NoJavaScript #NoCookiesEither#NotMuchBullShit #snacAnnounces
The search box also accepts post URLs; the post is requested and, if it's found, can be interacted with (liked, boosted, replied to, etc.).
IP addresses for failed logins are tracked and throttled to mitigate brute force attacks (see snac(8)
for more information).
Fixed a bug regarding repeated attachments when editing a post.
Mastodon API: Improved timeline pagination in some clients (details: an HTTP Link
header has been added), fixed missing audio attachments, fixed an incorrect value for the bot
field in newly created accounts, fixed a crash, implemented markers (contributed by nowster).
When running in server mode, the pidfile is locked to avoid concurrent running of the same server instance.
Added documentation and some tweaks to enable static compilation with musl (contributed by Shamar).
If you find #snac useful, please consider contributing via LiberaPay: https://liberapay.com/grunfink/
In the northern half we'll celebrate #SolInvictus by listening to the song One Perfect Sunrise by #Orbital.
Más tarde me he dado cuenta de que empleando el correo electrónico las discusiones no tienen sentido y que más allá del duelo al amanecer no merece la pena discutir con gente que se ha construido un personaje público y saca sus garbanzos de ahí. Entre eso y los palmeros, a los que el tuitstar SÍ responde por que necesita tenerles en cuenta, es difícil estar a gusto; de hecho el término "pocosfollower" es el indicativo de una época.
Pero sí que he pasado mucho tiempo allí obteniendo enlaces y enterándome de polémicas para pasar el rato y olvidar cómo estoy y quién soy así que tampoco es que lo haya dejado hasta el sábado. Una vez que tengo mi servidor en el fediverso (con #snac) tengo siempre un lugar que considero mío. Por esa parte estoy cubierto.
Ahora estoy intentando ver qué aparece en BlueSky y de momento están todos con una limpia tremenda de nazis y demás chusma que está funcionando al parecer. También cuentas estupendas que estaban permanentemente candadas en twitter ahora actúan en abierto y son una delicia de seguir. Pero el lugar sigue siendo extraño, como un barrio bajo asedio, y quiero ver dónde terminará cuando los dueños empiecen a monetizar.
max_id
nor since_id
fields to paginate, only a limit
field of 40.Regarding the other issue, snac do support Mastodon API pagination. Many apps do this correctly, like Tusky, Fedilab or semaphore.social, so you can travel the full timeline. Other ones only request the first page, I don't know why.
CC: @nowster@fedi.nowster.me.uk @justine@snac.smithies.me.uk
@nowster @justine Thanks for the test account.
There are at least two #snac bugs.
I've filed one of them at https://codeberg.org/grunfink/snac2/issues/241 (this also found a Pachli bug where errors during login weren't showing the underlying login error; I've fixed that now, thanks).
The other is the existing https://codeberg.org/grunfink/snac2/issues/164 -- snac doesn't implement https://docs.joinmastodon.org/api/guidelines/#pagination so Mastodon clients can't iterate through timelines to load them a page at a time.
I've discovered a thing, though; if I have the ntfy app and Tusky running at the same time, Tusky adds 3 or 4 additional notifications to Ntfy (don't know why), and then chaos insues (I get repeated notifications all the time).
https://github.com/macports/macports-ports/pull/27028/
2 out of 3 of GitHub Actions Continuous Integration checks have passed (and the third is running and hopefully will as well).
As in the past, I don't have commit access, so it's up to someone else to merge it.
Thank you for the continued improvements and bug fixes!
#snac #MacPorts #OpenSource #ActivityPub #Mastodon #NoDatabaseNeeded
#NoJavaScript #NoCookiesEither#NotMuchBullShit #snacAnnounces
But, always off by default. I swear.
But, I see great people using #snac and asking for this, and who am I to be that stubborn.
It will always be disabled by default, though.
As many users have asked for it, there is now an option to make the number of followed and following accounts public (still disabled by default). These are only the numbers; the lists themselves are never published.
Some fixes to blocked instances code (posts from them were sometimes shown).
Fixed non-appearing buttons Approve
and Discard
if the account requesting a follow were being followed.
If you find #snac useful, please consider contributing via LiberaPay: https://liberapay.com/grunfink/
This release has been inspired by the songs All Is Lost by #KatieGarfield and All Is Not Lost by #TonyAnderson.