Replies: 11 comments 35 replies
-
Maybe a croncert bot in the Fediverse? |
Beta Was this translation helpful? Give feedback.
-
Meanwhile expect new Basel and Berlin venues ... ;) |
Beta Was this translation helpful? Give feedback.
-
@jakopako, do you have a Fediverse presence? Maybe there should be an official Croncert account in some Mastodon instance or the other. We have https://tooting.ch here in Switzerland to start with. |
Beta Was this translation helpful? Give feedback.
-
Is there some way to make a URL for a particular search setting? |
Beta Was this translation helpful? Give feedback.
-
So, since individual events in the API do not (yet) have a unique ID I think I'll do something like this: event JSON | cannonical representation | hash And then store the hashes somewhere, say in a hashes.txt file (to allow this to be deployed as a GitHub action). Then, to avoid reposting an event I can just grep the hashes.txt file. This will have the useful side effect of reposting an event which has changed. |
Beta Was this translation helpful? Give feedback.
-
Here's a first test of what these things are likely to look like: https://tooting.ch/@concertcloud/111291151031712649 and |
Beta Was this translation helpful? Give feedback.
-
@jakopako have you seen this? https://docs.joinmobilizon.org/contribute/graphql_api/ And this? https://mobilisons.ch/ |
Beta Was this translation helpful? Give feedback.
-
The admin of tooting.ch is encouraging me to dump events from the concertcloud.live API into Mobilisons, but I'm wondering if their API might actually be a reasonable target for the scrapers in the first place. ... |
Beta Was this translation helpful? Give feedback.
-
I wouldn't really call it solved.
What I decided to do was to take whatever open graph URL was offered as
canonical so long as it exists, and then to take the biggest image on the
sub-page for the event.
In short, it works most of the time. I'd rather have it in the Concert
Cloud data.
But anyway, it's coming along.
…On Thu, 23 Nov 2023 at 21:05, jakopako ***@***.***> wrote:
Very cool! Did you solve the image problem?
—
Reply to this email directly, view it on GitHub
<#254 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAATLBSEDYQBMLTWYOGO4DDYF6UA7AVCNFSM6AAAAAAX3J5V3KVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TMNJUHAZDO>
.
You are receiving this because you were mentioned.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
I should mention that I'm in Neuchatel today meeting with somebody from Fairsocial.net. We should organise a bigger meetup at some point. |
Beta Was this translation helpful? Give feedback.
-
This discussion is meant to collect a bunch of thoughts concerning the question in the title and on top of that figure out ways of assessing whether the entire project even makes sense in the sense of 'do people even need such a website?'
Actually, the most important question is probably whether people even need such a website. Or are there enough other websites that provide the information that people need? Does this website/project provide extra value that no other website provides? What are people's preferred ways of finding good concerts? I anyone even interested in finding new venues? Or does everyone rather go to known venues or follow suggestions received from friends etc.?
Let's say there is a need for such a website, then how do we find contributors? The group of people most likely to contribute is probably somewhere in the intersection between people that like music (and are especially curious to find new music / venues) and people that have sufficient IT skills to add events to the concert database by extending the configuration file in this repository. How does this group of people find out about this project?
Beta Was this translation helpful? Give feedback.
All reactions