#DailyBloggingChallenge (001/10)
In the past I have been quite fruitful with daily challenges. Successfully achieved the 50 day #StatisticsChallenge and slowly creeping up on 365 day mark of the #MappingChallenge (@barefootstache@en.osm.town) with less than a month to go. Thus, I will attempt the daily blogging challenge.
The requirements will be quite simple for the begining and might expand through time:
- It must use `hashtag (XX/YY)` format. This has two benefits:
1. One can follow the hashtag thereby potentialy creating its own atom/rss feed.
2. One can filter out these posts if unwanted.
- It must be post ready before slumber. This puts the focus on writing rather than publishing and gives a grace period if no internet connection.
- If written on mobile, it must be written with the #8pen keyboard.
- It must be at least one paragraph or three sentences long.
This challenge was sparked after reading the article
https://www.yieldcode.blog/post/why-engineers-should-write/
written by @skwee357.
#DailyBloggingChallenge (18/25)
This is where you can find the #RSS for an account on #mastodon (and probably the #fediverse):
```
https://<instance>/@<username>.rss
```
For my account it would be `https://qoto.org/@barefootstache.rss`
And for hashtags it's
```
https://<instance>/tags/<hashtag>.rss
```
For the #DailyBloggingChallenge it's `https://qoto.org/tags/DailyBloggingChallenge.rss`
One thing to keep in mind for choosing an `<instance>` for the hashtags, one should choose one that does not shadow ban keywords. In general, qoto.org is a good choice.
#Fdroid has a wide selection of apps to use as an RSS reader: https://search.f-droid.org/?q=rss+&lang=en
My preference is #Feeder (https://gitlab.com/spacecowboy/Feeder). Similar apps exist for various operating systems and as browser extensions.
#DailyBloggingChallenge (19/25)
Did you know that most newsletters have a #RSS or #atom option? The benefit of RSS over a #newsletter is that you are on the more private side, since lots of individuals use their private #email and lots of forms even ask for your name. This (if ever leaked) provides attackers a great data packet to put on their #spam lists and once on such a list, it is hard to get off it.
One could argue on the other side that RSS is also not safe, since one is prone towards #XSS attacks, though this can be said of anything that has internet access. So one wouldn't be better off if using email.
Thus when choosing a client, either for email or RSS feed, it is always better to opt for one that is not in the browser and sanitizes the message(s). Browser extensions are definitely a more lucrative attack option over operating system apps.
@skwee357 the Feeder app has the setting not to hide read posts
@barefootstache while generally I agree, I never was able to like RSS. Most readers treat is a chronological newspaper, which means if you “accidentally” read a post you did not intend to, you now need to fight and marking it as unread.
Email stays in your inbox, as long as you did not archived/deleted it. And since I practice zero inbox, I find this approach easier for my need.
As for #security and #privacy, one can always use masked email.
But it’s good to have options, so I agree.